Wireshark-users: [Wireshark-users] AT&T backbone issues 08/04/2011 1230pm - 5pm CDT?
From: Ben Bartsch <uwcableguy@xxxxxxxxx>
Date: Fri, 5 Aug 2011 08:38:16 -0500
Did anyone else notice any problems on the ATT backbone yesterday?  We had one VPN tunnel go down (out of 8) and found the problem was within the ATT internet infrastructure.  After being transferred around ATT for about 2 hours, the problem seemed to resolve itself.

We are in Baton Rouge. LA and our VPN connect from here to Connecticut.  We found that packets from Connecticut were reaching us here, but were not gettting back to Connecticut.  Our tracert failed at 12.81.24.97.  After the problem resolved itself, we were able to continue on to 74.175.192.22.

I am curious if anyone else had similar problems yesterday.  Also, does anyone know a decent web site that shows (in real time) outages and delays on the internet backbone?  I found one - http://www.internetpulse.net/ that was interesting.  And what about a map showing where these IPs physically reside (as opposed to where they are registered)?

The site rocks, Stretch!  Keep up the good work.

Ben



Failed tracert:
1  65.x.x.x 0 msec 0 msec 0 msec
2  65.x.x.x 10 msec 0 msec 0 msec
3  12.81.38.6 10 msec 10 msec 10 msec
4  12.83.24.126 30 msec 10 msec 0 msec
5  12.81.24.97 10 msec 10 msec 10 msec
6   *  *  *

Successful tracert:
1  65.x.x.x 0 msec 0 msec 0 msec
2  65.x.x.x 60 msec 0 msec 0 msec
3  12.81.38.6 40 msec 20 msec 10 msec
4  12.83.24.126 20 msec 10 msec 20 msec
5  12.81.24.97 10 msec 20 msec 20 msec
6  74.175.192.22 20 msec 40 msec 10 msec
7  12.123.153.18 40 msec 50 msec 60 msec
8  12.122.18.1 50 msec 50 msec 40 msec
9  12.122.2.133 50 msec 40 msec 100 msec
10 12.122.1.174 40 msec 170 msec 40 msec
11 12.122.3.37 50 msec 90 msec 40 msec
12 12.122.115.94 50 msec 60 msec 60 msec
13 12.122.130.137 40 msec 50 msec 60 msec
14 12.86.158.250 50 msec 40 msec 50 msec
15-19 removed