Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Waveform.net outage?
Waveform.net outage?
Posted by natecarlson, 11-27-2009, 04:40 PM |
Howdy,
I'm having issues reaching my server at Waveform.. anyone else having issues?
I can't reach my server, the IPMI interface on it, or the router IP on Waveform's side.. get a nice loop between two of their routers when tracerouting (see below). I've had packet loss issues on their network before (apparently 1U customers get put on a network segment that is more vulnerable to DDoS?), but don't recall having a complete down.
I filled out the contact form on their site a few hours ago, and tried calling the only phone number I have from them.. haven't heard back, and still down.
traceroute to admin.det.technicality.org (208.92.219.73), 30 hops max, 40 byte packets
<snip>
8 p15-0.chr1.southfield-mi.us.xo.net (207.88.84.110) 7.049 ms 7.038 ms 7.058 ms
9 66.237.110.54.ptr.us.xo.net (66.237.110.54) 7.113 ms 7.060 ms 7.029 ms
10 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 8.115 ms 8.104 ms 7.654 ms
11 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 7.700 ms 7.889 ms 7.967 ms
12 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 9.232 ms 9.217 ms 9.117 ms
13 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 8.758 ms 8.730 ms 8.713 ms
14 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 9.148 ms 8.798 ms 8.783 ms
15 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 8.659 ms 8.850 ms 8.837 ms
16 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 9.466 ms 9.491 ms 9.518 ms
17 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 9.402 ms 9.429 ms 9.466 ms
18 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 10.191 ms 10.178 ms 10.303 ms
19 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 10.031 ms 10.160 ms 10.147 ms
20 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 11.230 ms 11.218 ms 12.026 ms
21 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 11.255 ms 10.500 ms 10.485 ms
22 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 10.947 ms 10.978 ms 10.966 ms
23 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 10.788 ms 10.721 ms 10.756 ms
24 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 11.526 ms 11.660 ms 11.642 ms
25 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 11.645 ms 11.633 ms 11.611 ms
26 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 14.093 ms 14.792 ms 14.759 ms
27 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 13.995 ms 12.636 ms 12.793 ms
28 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 13.820 ms 13.838 ms 13.474 ms
29 pos-3-0.core2.sfld.waveform.net (216.29.182.93) 13.313 ms 13.338 ms 13.371 ms
30 pos-3-0.core1.troy2.waveform.net (216.29.182.94) 14.054 ms 13.584 ms 14.012 ms |
Posted by natecarlson, 11-27-2009, 04:41 PM |
I should note that their web site is working - this is the same behavior I've had before when I'm having packet loss.. again, it's apparently due to the segment I'm on within their network. |
Posted by natecarlson, 11-27-2009, 04:55 PM |
Heard back..
"Some customer service is currently interrupted by an issue with one of our routers. Our engineers are working right now to solve this problem. We will continue to update our customers with more information as it becomes available."
Bummer. Now to decide if I should fire up a server with last night's backups or wait it out... |
Posted by jts_01, 11-27-2009, 05:01 PM |
Spoke to support and no ETA as of yet |
Posted by natecarlson, 11-27-2009, 05:17 PM |
Do you have a NOC contact that actually works outside of business hours? If so, could you PM it to me?
Thanks! |
Posted by jts_01, 11-27-2009, 06:14 PM |
Back up for me |
Posted by natecarlson, 11-27-2009, 06:23 PM |
Yup - just lit up a few minutes ago for me too. |
Posted by AlternativeHost, 11-27-2009, 06:27 PM |
A few people have contacted me stating the routing issue had happened for about an hour and affected all of their colocated servers. As of about 10 minutes ago the servers started responding and everything looks to be in working order. Your best bet to contact them is email as I am sure their phones are swamped at the moment. |
Posted by AlternativeHost, 11-27-2009, 10:53 PM |
I was not informed form one of their clients until 2:26pm EST, but that does appear to be case. Can anyone confirm if this affected just colocation customers? I do not have equipment there, so I am unable to check the status. |
Add to Favourites Print this Article
Also Read