AT&T Outage?

Update:

4 785 ms 245 ms 781 ms gbr5.n54ny.ip.att.net [12.123.202.130]

5 756 ms 759 ms 787 ms tbr1.n54ny.ip.att.net [12.122.11.9]

6 * * * Request timed out.

7 729 ms 737 ms 699 ms 64.212.107.97

8 * * * Request timed out.

9 682 ms 688 ms 331 ms
COMCAST-IP-SERVICES-LLC-New-York.TenGigabitEther

et9-2.ar4.NYC1.gblx.net [64.213.77.218]

10 667 ms 673 ms 674 ms
te-0-1-0-0-crs01.plainfield.nj.panjde.comcast.ne

[68.85.192.37]

11 * * * Request timed out.

12 710 ms 696 ms 709 ms
te-1-1-ur02.mtlaurel.nj.panjde.comcast.net [68.8

.192.42]

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

Same coming out of the mid-west also.

  4 12.122.96.5 584 msec 788 msec 784 msec
  5 192.205.34.62 816 msec 632 msec 616 msec
  6 ae-15-51.car1.Atlanta2.Level3.net (4.68.103.10) 712 msec 808 msec
860 msec
  7 COMCAST-IP.car1.Atlanta2.Level3.net (4.71.252.6) 784 msec 840 msec
784 msec
  8 pos-0-8-0-0-cr01.mclean.va.ibone.comcast.net (68.86.85.70) 736 msec
820 msec
784 msec
  9 pos-0-0-0-0-cr01.philadelphia.pa.ibone.comcast.net (68.86.85.6) 796
msec 844
msec 852 msec
10 be-40-crs01.401nbroadst.pa.panjde.comcast.net (68.86.208.33) 872
msec 804 ms
ec 696 msec
11 pos-0-7-0-0-crs01.ivyland.pa.panjde.comcast.net (68.85.192.202) 748
msec 824
msec *
12 te-0-1-0-0-crs01.plainfield.nj.panjde.comcast.net (68.85.192.37) 700
msec 74
0 msec 784 msec
13 te-1-1-ur01.mtlaurel.nj.panjde.comcast.net (68.85.192.38) 824 msec
848 msec
864 msec
14 te-1-1-ur02.mtlaurel.nj.panjde.comcast.net (68.85.192.42) 800 msec
768 msec
716 msec
15 te-1-1-ur01.arneysmount.nj.panjde.comcast.net (68.85.192.46) 680
msec 692 ms
ec 828 msec
16 GE-0-1-ubr01.arneysmount.nj.panjde.comcast.net (68.86.223.118) 824
msec 800
msec 816 msec
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Same coming out of the mid-west also.

Not seeing anything unusual here in S.E CT (att adsl going to Comcast
business cable acct.).

1 2 ms 10 ms 2 ms 172.16.34.250
2 1 ms <1 ms <1 ms 69.183.133.206
3 8 ms 8 ms 8 ms se1-l0.mrdnct.sbcglobal.net [204.60.4.38]
4 8 ms 9 ms 8 ms dist1-vlan60.mrdnct.sbcglobal.net
[66.159.184.226]
5 45 ms 24 ms 15 ms bb1-10g2-0.mrdnct.sbcglobal.net
[151.164.92.147]
6 88 ms 98 ms 147 ms 151.164.94.255
7 100 ms 52 ms 13 ms asn3356-level3.eqnwnj.sbcglobal.net
[151.164.89.250]
8 16 ms 18 ms 17 ms ae-31-53.ebr1.newark1.level3.net
[4.68.99.94]
9 14 ms 17 ms 17 ms ae-2.ebr1.newyork1.level3.net [4.69.132.97]
10 24 ms 19 ms 16 ms ae-71-71.csw2.newyork1.level3.net
[4.69.134.70]
11 13 ms 13 ms 13 ms ae-2-79.edge1.newyork2.level3.net
[4.68.16.75]
12 14 ms 28 ms 13 ms comcast-ip.edge1.newyork2.level3.net
[4.71.184.2]
13 16 ms 17 ms 17 ms
te-3-3-ar01.chartford.ct.hartford.comcast.net [68.86.90.66]
14 17 ms 17 ms 17 ms po-10-ar01.berlin.ct.hartford.comcast.net
[68.87.146.30]
15 17 ms 17 ms 17 ms
te-9-1-ur01.middletown.ct.hartford.comcast.net [68.87.182.50]
16 18 ms 17 ms 18 ms
te-9-1-ur01.killingworth.ct.hartford.comcast.net [68.87.182.46]
17 18 ms 18 ms 28 ms te-9-1-ur01.clinton.ct.hartford.comcast.net
[68.87.182.42]
18 19 ms 20 ms 20 ms te-8-1-ur01.groton.ct.hartford.comcast.net
[68.87.182.21]
19 19 ms 19 ms 26 ms
te-9-1-ur01.nstonington.ct.hartford.comcast.net [68.87.182.25]
20 19 ms 19 ms 20 ms te-9-1-ur01.norwich.ct.hartford.comcast.net
[68.86.231.166]
21 * 1533 ms 2871 ms
75-144-196-61-connecticut.hfc.comcastbusiness.net [75.144.196.61]

ya, our end point is a tad saturated but not my problem yet. :wink:

~JasonG