amuck-landowner

NY CC blowed away

Francisco

Company Lube
Verified Provider
Confirmed CC buffalo is back up.
Yep. Nodeping has a monitoring node there and it blasted off alerts for Jersey for us.

I don't expect much of an 'excuse', most likely just a hardware failure or possibly a screwup on an upstreams prefix lists/ACL's.

Francisco
 
Last edited by a moderator:

bzImage

New Member
Now I know why I keep getting false alarm SMS messages from node ping.

23.94.101.96 - - [09/Mar/2014:09:06:09 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"
23.94.101.96 - - [09/Mar/2014:09:07:10 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"
23.94.101.96 - - [09/Mar/2014:09:08:09 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"
23.94.101.96 - - [09/Mar/2014:09:09:10 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"
 

ColoCrossing CC-16 (NET-23-94-0-0-1) 23.94.0.0 - 23.95.255.255
 
 

ocitysolutions

New Member
Verified Provider
Our network up there was offline for over an hour. This will be added to the list of reasons we are moving next weekend.
 

Francisco

Company Lube
Verified Provider
I though LET was running host on vanillaforums.com
No that's what "the cluster" thing that we poke at. They were hosted there but ate some fairly large floods.

On top of that, vanillaforums.com got hacked due to LET being hosted there.

Francisco
 

NodePing

New Member
Yep. Nodeping has a monitoring node there and it blasted off alerts for Jersey for us.


I don't expect much of an 'excuse', most likely just a hardware failure or possibly a screwup on an upstreams prefix lists/ACL's.


Francisco
We don't have a production probe server in New York.
 

NodePing

New Member
Now I know why I keep getting false alarm SMS messages from node ping.

23.94.101.96 - - [09/Mar/2014:09:06:09 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"


23.94.101.96 - - [09/Mar/2014:09:07:10 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"


23.94.101.96 - - [09/Mar/2014:09:08:09 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"


23.94.101.96 - - [09/Mar/2014:09:09:10 -0700] "GET / HTTP/1.1" 302 2352 "-" "NodePing"

ColoCrossing CC-16 (NET-23-94-0-0-1) 23.94.0.0 - 23.95.255.255
We don't have a probe in New York.  Those logs are from March 9.  Are they related to this outage?

We work hard to not send false alerts. If you're getting some, please let us know via a support ticket and we'll look into it.
 

Awmusic12635

Active Member
Verified Provider
Tonight, while a technician was in the building meet me room completing the installation of additional fiber connections to service our Buffalo datacenter, an error which impacted a master patch panel occurred which caused an interruption of service to all segments of our network. ColoCrossing understands that you rely on our services and that any outage, for any reason, including human error is absolutely unacceptable. Immediately upon receiving notice of the network-down alert ColoCrossing's facilities team began investigating and took action to resolve the outage. In the coming days we will be conducting a full review and will institute changes to our policies to ensure that a similar event cannot impact our network in the future. We appreciate your business and regret any frustration caused.
 

Nett

Article Submitter
Verified Provider
Nah, Biloh forgot to pay the tech salary and the tech decided to cut the network.
 
Last edited by a moderator:
Top
amuck-landowner