Shared Hosting
Shared HostingKnowledgebase
Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > GNAX/Net Depot Dallas traceroute failures
GNAX/Net Depot Dallas traceroute failures
 |
 |
 |
Posted by sfchost, 02-20-2011, 07:37 PM Well it appears that GNAX/NetDepot data center in Dallas is having problems again. I did open a ticket (OWY-171821) and will be awaiting their response or the usual "close the ticket and maybe no one will notice" Quote:
Traceroute from Baltimore, MD -
1 ge-6-15-14.car1.Philadelphia1.Level3.net (4.69.135.117) 4 msec 0 msec 0 msec
2 ae-7-7.ebr2.Washington1.Level3.net (4.69.133.162) 8 msec 8 msec 4 msec
3 ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 8 msec 8 msec
ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 4 msec
4 ae-1-60.edge1.Washington4.Level3.net (4.69.149.15) 8 msec
ae-2-70.edge1.Washington4.Level3.net (4.69.149.79) 8 msec
ae-1-60.edge1.Washington4.Level3.net (4.69.149.15) 8 msec
5 xe-1-2-0.er1.iad10.us.above.net (64.125.13.233) [AS6461 {ABOVENET}] 4 msec 8 msec 8 msec
6 xe-2-0-0.cr2.dca2.us.above.net (64.125.31.209) [AS6461 {ABOVENET}] 8 msec 8 msec 40 msec
7 xe-2-2-0.cr2.iah1.us.above.net (64.125.30.53) [AS6461 {ABOVENET}] 60 msec 60 msec 60 msec
8 xe-1-2-0.cr2.dfw2.us.above.net (64.125.26.133) [AS6461 {ABOVENET}] 40 msec 40 msec 56 msec
9 xe-0-2-0.mpr1.dfw1.us.above.net (64.125.27.213) [AS6461 {ABOVENET}] 40 msec 40 msec 40 msec
10 64.125.193.186.t00805-01.above.net (64.125.193.186) [AS6461 {ABOVENET}] 40 msec 40 msec 40 msec
11 * * *
Traceroute from Boston, MA -
1 ae-2-7.bar1.Boston1.Level3.net (4.69.132.242) 12 msec 0 msec 0 msec
2 ae-0-11.bar2.Boston1.Level3.net (4.69.140.90) 0 msec 0 msec 4 msec
3 ae-8-8.ebr1.NewYork1.Level3.net (4.69.140.98) 4 msec 4 msec 8 msec
4 ae-4-4.ebr1.NewYork2.Level3.net (4.69.141.18) 4 msec 4 msec 4 msec
5 ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 8 msec 8 msec 12 msec
6 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 8 msec *
ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 1024 msec
7 ae-1-60.edge1.Washington4.Level3.net (4.69.149.15) 76 msec
ae-3-80.edge1.Washington4.Level3.net (4.69.149.143) 16 msec 12 msec
8 xe-1-2-0.er1.iad10.us.above.net (64.125.13.233) [AS6461 {ABOVENET}] 8 msec 12 msec 8 msec
9 xe-2-0-0.cr2.dca2.us.above.net (64.125.31.209) [AS6461 {ABOVENET}] 12 msec 12 msec 12 msec
10 xe-2-2-0.cr2.iah1.us.above.net (64.125.30.53) [AS6461 {ABOVENET}] 48 msec 44 msec 44 msec
11 xe-1-2-0.cr2.dfw2.us.above.net (64.125.26.133) [AS6461 {ABOVENET}] 44 msec 40 msec 44 msec
12 xe-0-2-0.mpr1.dfw1.us.above.net (64.125.27.213) [AS6461 {ABOVENET}] 44 msec 44 msec 44 msec
13 64.125.193.186.t00805-01.above.net (64.125.193.186) [AS6461 {ABOVENET}] 228 msec 156 msec 240 msec
14 * * *
Traceroute from Baton Rouge, LA -
1 ge-6-17-16.car1.Houston1.Level3.net (4.69.135.197) 8 msec 8 msec 8 msec
2 ae-2-5.bar1.Houston1.Level3.net (4.69.132.230) 4 msec 8 msec 8 msec
3 ae-13-13.ebr1.Dallas1.Level3.net (4.69.137.138) 24 msec 20 msec 16 msec
4 ae-1-60.edge2.Dallas3.Level3.net (4.69.145.12) 16 msec
ae-4-90.edge2.Dallas3.Level3.net (4.69.145.204) 12 msec 12 msec
5 ex-3-1-0.er1.dfw2.us.above.net (64.125.12.73) [AS6461 {ABOVENET}] 16 msec 88 msec 12 msec
6 xe-1-1-0.cr1.dfw2.us.above.net (64.125.26.209) [AS6461 {ABOVENET}] 36 msec 28 msec 12 msec
7 xe-0-1-0.mpr1.dfw1.us.above.net (64.125.27.209) [AS6461 {ABOVENET}] 12 msec 12 msec 12 msec
8 64.125.193.186.t00805-01.above.net (64.125.193.186) [AS6461 {ABOVENET}] 12 msec 16 msec 12 msec
9 * * *
Traceroute from Burlington, VT -
1 ge-6-22-12.car1.Philadelphia1.Level3.net (4.69.135.61) 20 msec 20 msec 16 msec
2 ae-7-7.ebr2.Washington1.Level3.net (4.69.133.162) 20 msec 24 msec 20 msec
3 ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 24 msec 20 msec 24 msec
4 ae-4-90.edge1.Washington4.Level3.net (4.69.149.207) 20 msec
ae-2-70.edge1.Washington4.Level3.net (4.69.149.79) 20 msec
ae-3-80.edge1.Washington4.Level3.net (4.69.149.143) 24 msec
5 xe-1-2-0.er1.iad10.us.above.net (64.125.13.233) [AS6461 {ABOVENET}] 76 msec 24 msec 20 msec
6 xe-2-0-0.cr2.dca2.us.above.net (64.125.31.209) [AS6461 {ABOVENET}] 156 msec 20 msec 24 msec
7 xe-2-2-0.cr2.iah1.us.above.net (64.125.30.53) [AS6461 {ABOVENET}] 76 msec 80 msec 88 msec
8 xe-1-2-0.cr2.dfw2.us.above.net (64.125.26.133) [AS6461 {ABOVENET}] 72 msec 76 msec 56 msec
9 xe-0-2-0.mpr1.dfw1.us.above.net (64.125.27.213) [AS6461 {ABOVENET}] 104 msec 56 msec 56 msec
10 64.125.193.186.t00805-01.above.net (64.125.193.186) [AS6461 {ABOVENET}] 56 msec 72 msec 56 msec
11 * * *
Traceroute from Buffalo, NY -
1 ge-6-18-22.car2.Pittsburgh3.Level3.net (4.69.136.5) 8 msec 8 msec 12 msec
2 ae-3-3.ebr1.Chicago1.Level3.net (4.69.135.250) 28 msec 20 msec 36 msec
3 ae-1-51.edge3.Chicago3.Level3.net (4.69.138.10) 20 msec 24 msec 20 msec
4 xe-1-2-0.er1.ord7.us.above.net (64.125.13.237) [AS6461 {ABOVENET}] 24 msec 20 msec 24 msec
5 xe-2-2-0.cr1.ord2.us.above.net (64.125.26.249) [AS6461 {ABOVENET}] 20 msec 24 msec 24 msec
6 xe-0-2-0.cr1.dfw2.us.above.net (64.125.30.61) [AS6461 {ABOVENET}] 48 msec 48 msec 80 msec
7 xe-0-1-0.mpr1.dfw1.us.above.net (64.125.27.209) [AS6461 {ABOVENET}] 48 msec 144 msec 48 msec
8 64.125.193.186.t00805-01.above.net (64.125.193.186) [AS6461 {ABOVENET}] 68 msec 68 msec 68 msec
9 * * *
Traceroute from Columbia, SC -
1 ge-7-16-22.car2.Atlanta1.Level3.net (4.69.151.81) 8 msec
ge-7-16-21.car1.Atlanta1.Level3.net (4.69.151.53) 16 msec
ge-7-16-22.car2.Atlanta1.Level3.net (4.69.151.81) 8 msec
2 vlan51.csw1.Atlanta2.Level3.net (4.69.150.62) 16 msec
vlan52.csw2.Atlanta2.Level3.net (4.69.150.126) 12 msec
vlan51.csw1.Atlanta2.Level3.net (4.69.150.62) 16 msec
3 ae-73-73.ebr3.Atlanta2.Level3.net (4.69.148.253) 8 msec
ae-63-63.ebr3.Atlanta2.Level3.net (4.69.148.241) 12 msec
ae-73-73.ebr3.Atlanta2.Level3.net (4.69.148.253) 8 msec
4 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 28 msec 24 msec 28 msec
5 ae-71-71.csw2.Washington1.Level3.net (4.69.134.134) 20 msec
ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 28 msec *
6 ae-4-90.edge1.Washington4.Level3.net (4.69.149.207) 24 msec
ae-3-80.edge1.Washington4.Level3.net (4.69.149.143) 28 msec
ae-1-60.edge1.Washington4.Level3.net (4.69.149.15) 32 msec
7 xe-1-2-0.er1.iad10.us.above.net (64.125.13.233) [AS6461 {ABOVENET}] 24 msec 28 msec 28 msec
8 xe-2-0-0.cr2.dca2.us.above.net (64.125.31.209) [AS6461 {ABOVENET}] 28 msec 24 msec 32 msec
9 xe-2-2-0.cr2.iah1.us.above.net (64.125.30.53) [AS6461 {ABOVENET}] 40 msec 44 msec 40 msec
10 xe-1-2-0.cr2.dfw2.us.above.net (64.125.26.133) [AS6461 {ABOVENET}] 48 msec 52 msec 48 msec
11 xe-0-2-0.mpr1.dfw1.us.above.net (64.125.27.213) [AS6461 {ABOVENET}] 48 msec 52 msec 44 msec
12 64.125.193.186.t00805-01.above.net (64.125.193.186) [AS6461 {ABOVENET}] 44 msec 40 msec 44 msec
13 * * *
Traceroute from Chicago, IL -
1 ae-2-52.edge3.Chicago3.Level3.net (4.69.138.42) 0 msec
ae-1-51.edge3.Chicago3.Level3.net (4.69.138.10) 0 msec
ae-2-52.edge3.Chicago3.Level3.net (4.69.138.42) 0 msec
2 xe-1-2-0.er1.ord7.us.above.net (64.125.13.237) [AS6461 {ABOVENET}] 0 msec 0 msec 0 msec
3 xe-2-2-0.cr1.ord2.us.above.net (64.125.26.249) [AS6461 {ABOVENET}] 0 msec 4 msec 0 msec
4 xe-0-2-0.cr1.dfw2.us.above.net (64.125.30.61) [AS6461 {ABOVENET}] 32 msec 32 msec 36 msec
5 xe-0-1-0.mpr1.dfw1.us.above.net (64.125.27.209) [AS6461 {ABOVENET}] 32 msec 32 msec 36 msec
6 64.125.193.186.t00805-01.above.net (64.125.193.186) [AS6461 {ABOVENET}] 32 msec 36 msec 32 msec
7 * * *
Posted by NetDepot - Terrence, 02-20-2011, 07:48 PM Will look into this for you.
Posted by NetDepot - Terrence, 02-20-2011, 07:55 PM Hello,
Our team is investigating the issues at the moment as posted on the ticket. feel free to send me an email tyhap[@]gnax.net if you have any questions.
Posted by Dustin Cisneros, 02-20-2011, 07:57 PM Do they really just close tickets without reviewing them?
I was considering them and spoke with Jason a few times doesnt sound like they would do this...
Posted by NetDepot - Terrence, 02-20-2011, 08:01 PM
I was considering them and spoke with Jason a few times doesnt sound like they would do this...
Posted by sfchost, 02-20-2011, 09:58 PM We 've have 12 documented incidents of connectivity issues since the beginning of October 2010. I guess I should clarify that we had tickets closed with NO response, but in ALL cases the issue (whatever it was) was actually resolved.
Posted by Dustin Cisneros, 02-21-2011, 04:15 AM
Posted by rd1234, 02-21-2011, 06:02 AM You might want to check that your server accepts icmp requests.
Posted by sfchost, 02-21-2011, 07:56 AM Yes, the server accepts ICMP requests...
Here is our Pingdom report for the last 24 hours....We were just informed that:Quote:
Date/Time - Status - Response Time - Error - Location
02/21/2011 05:59:26AM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Washington, DC
02/21/2011 05:58:26AM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Madrid, Spain
02/21/2011 05:58:06AM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Dallas 5, TX
02/21/2011 01:14:03AM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Herndon, VA
02/21/2011 01:12:26AM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Houston 3, TX
02/21/2011 01:12:04AM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Dallas 5, TX
02/20/2011 06:20:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Dallas 6, TX
02/20/2011 06:19:09PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Houston 3, TX
02/20/2011 06:16:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - New York, NY
02/20/2011 06:15:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Chicago, IL
02/20/2011 06:14:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Copenhagen, Denmark
02/20/2011 06:13:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Seattle, WA
02/20/2011 06:12:27PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Washington, DC
02/20/2011 06:11:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Madrid, Spain
02/20/2011 06:10:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Las Vegas, NV
02/20/2011 06:09:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Denver, CO
02/20/2011 06:08:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - San Francisco, CA
02/20/2011 06:07:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Paris, France
02/20/2011 06:07:05PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Los Angeles, CA
02/20/2011 06:06:26PM - DOWN - Timeout (> 30s) - Socket timeout, unable to connect to server - Manchester, UKMy best guess is that the Dallas network does not have any form of IPS to help thwart, or at least detect, these types of attacks.Quote:
There was a very large scale DDOS attack directed towards another server located on the same switch
Posted by rd1234, 02-21-2011, 09:10 AM If the DDOS attack would choke the network you should probably see at least some of the pings getting through. It's more probable that a provider upstream detected the attack and started filtering traffic until the situation cools down. You might be just a collateral victim of this.
Add to Favourites 
Print this Article
Also Read
