- Previous message: Jay R. Ashworth: "Re: amazonaws.com?"
- Maybe in reply to: Loveless, Phillip S.: "AT&T Outage?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Jason Gurtz (no email)
Date: Wed Jun 04 2008 - 14:29:08 EDT
> 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. ;)
~JasonG
--
|
|
|