I work for an ISP and recall, I think it was last year or maybe early this year, that one of our Atlanta data customers had 3 circuit down trouble tickets over the span of several months where the reason for outage ultimately turned out to be theft of telco cable. 3 times!!!
After the usual confusion it was finally determined that one of the ISP's staff had "noticed a cable not quite seated" while working on the data center floor. He had apparently followed a "standard procedure" to remove and clean the cable before plugging it back in. It was a fiber cable and he managed to plug it back in wrong (transposed connectors on a fiber cable). Not only was the notion of cleaning the cable end bizarre -- what, wipe it on his t-shirt? -- and never fully explained, but there was no followup check to find out what that cable was for and whether it still worked. It didn't, for nearly a week.
Actually there's nothing odd about cleaning a fiber connection at all and it is a very exacting process (see link below). Apparently exacting in this case just didn't include re-inserting the ends in the right holes.
Inspection and Cleaning Procedures for Fiber-Optic Connections
http://www.cisco.com/en/US/tech/tk482/tk876/technologies_white_paper09186a0080254eba.shtml
...if you were only the recipient of these robocalls. For several days a few months ago I was the recipient of massive blowback from these calls. My number was one that a robocaller was programmed to spoof and I received dozens upon dozens of calls, some of them extremely angry. I finally ended up recording an explanatory message on my voice mail.
Funny google never saw a website for this supposed company and its 'datacenter,' it only appears as a listing in a couple online business directories with no real information. Nearly 50 customers out of service? As another poster suggested, I suspect this is one small potatoes colo/hosting reseller who had their rack of servers confiscated from a larger colo facility.
This is so last year:
http://www.nytimes.com/2008/05/31/business/media/31billboard.html
"The problem with QOS flags is that the end-user can set them. There's nothing preventing me from marking every single packet I send as high-priority."
Not a problem at all. Routers generally can be configured to pass Class of Service bits as received or rewrite them appropriately to fit one of the ISP's standard QoS profiles.
What is research but a blind date with knowledge? -- Will Harvey
