@WaveConnects Current call recording says 4:30am. Looking at a fusion splicing benchmarking, says that an average 2 person team takes 4 hours to prep and 8 hours to splice and coil. With the 4 person team, hopefully they will get it done faster. Was told they started the splicing at ~10:30pm.
@WaveConnects I just talked to the CNOC and they say that they have just finished pulling the new cables and started doing the fiber splicing an hour ago using 4 people. Won't give an ETA but did confirm that it is a 144 fiber line aka 288 splices need to be made.
@WaveConnects On my calls today, I have been told 3pm, 6pm and now 8:30pm. Your techs should know how long it takes to fix a fiber cable. So give us the real number so we don't get frustrated with the increasing time. Also say if you are waiting for others first, aka power co., etc to finish.
@NewGooseShoes@WaveConnects My last call in a few minutes ago said 10pm, which is over 10 hours of outage. Lets say it is the largest fiber cable at 144 strands, this would mean 288 splices. (10 hours ร 60 minutes) / 288 splices = ~2 minutes per splice.
@bruceonthe@WaveConnects They don't have an SLA. Read sections 10 Performance & Force Majeure and 12 Limitation of Liability for more info. https://t.co/GcY6xqJzMr
@wanamaker_alex@WaveConnects In fact you could have a script that pings your equipment every x minutes. If it can't pint it, it flags it as an outage. Then you could be proactive to an outage vers reactive to unhappy clients. Your techs all have cell phone and can log what the outage is and est time, etc.
@wanamaker_alex@WaveConnects Also if this is fiber, why are they not doing a fiber ring, which can be reversed at a break. This means that only a few people near the break would be affected and not the thousands right now.
@wanamaker_alex@WaveConnects I have topld them this also as it would actually save them money. I call them once an hour and chat with them for at least 15m. Add up all those calls from all of us customers and it is a large expense, which could be reduced by having an outage map with what is going on,
@fuzzychef Fred Hutch also has some good maps tracking the genome samples.
https://t.co/Q3TOLrGPS0 (Real-time tracking of pathogen evolution)
https://t.co/xvwgsHWvIN (Real-time tracking of nCoV)
psqlODBC is finally fixed for 32/64bit interoperability. You can now move files between your 32-bit application and your 64-bit application without having to change the name of the driver that you are using.
https://t.co/1EfzchwgTZ
Two unsuspecting users can cause a Denial of Service Attack against the server they are connecting to. This affects traditional web hosing companies the most who have many user databases on the same server. https://t.co/6Z8THJIUKO