Here's another one to sprintlink... this one looks good too. traceroute to 199.0.232.90 (199.0.232.90), 30 hops max, 40 byte packets 1 sl-gw5-nyc-5-1-1-6M.sprintlink.net (144.232.171.93) 1.435 ms 1.245 ms 1.18 ms 2 sl-bb10-nyc-2-2.sprintlink.net (144.232.7.53) 1.229 ms 1.254 ms 1.143 ms 3 sl-bb10-chi-3-0.sprintlink.net (144.232.8.202) 23.64 ms 23.673 ms 23.656 ms 4 sl-bb4-chi-4-0-0.sprintlink.net (144.232.0.166) 24.333 ms 24.155 ms 24.177 ms 5 144.228.252.13 (144.228.252.13) 25.052 ms 26.468 ms 25.29 ms 6 144.228.158.202 (144.228.158.202) 67.511 ms 73.599 ms 80.131 ms 7 tiny.sprintlink.net (199.0.232.90) 87.195 ms * 63.64 ms Dan Rabb digital broadcast network dan@dbn.net -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Jim Dawson Sent: Monday, November 30, 1998 2:56 PM To: Chris Cappuccio Cc: nanog@merit.edu Subject: Re: AT&T/Sprint problems On Mon, 30 Nov 1998, Chris Cappuccio wrote:
I'm on AT&T, and I haven't noticed any unreachable sites... ELI maybe?
Nope -- here's another out our other pipe: [ Mon Nov 30 12:40:50 ] [ root@pdx-s01 -> traceroute postoffice.worldnet.att.net traceroute to postoffice.worldnet.att.net (204.127.5.20), 30 hops max, 40 bytes 1 ns.bytes.net (205.147.64.1) 54.959 ms 18.982 ms 19.484 ms 2 cisco1.bytes.net (205.147.64.2) 19.213 ms 18.972 ms 29.649 ms 3 border1-serial3-1.Seattle.cw.net (204.70.52.49) 58.715 ms 29.107 ms 74.8s 4 border1-serial3-1.Seattle.cw.net (204.70.52.49) 33.812 ms !H * 39.391 ms H Jim __________________________________________________________________ Jim Dawson jdawson@navi.net GCN Communications, Inc. http://www.navi.net 618 NW Glisan St. Ste. 407 voice: +1.503.641.1449 Portland, Or 97209 USA fax: +1.503.641.3634 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~