Traceroutes to sprintlink.net seem fine here... Tracing route to sprintlink.net [199.0.232.90] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms vlan2-lr1.stl1.dbn.net [209.251.166.1] 2 <10 ms * <10 ms lilublue.stl1.dbn.net [209.251.163.50] 3 <10 ms * <10 ms ge033-gr1.stl1.dbn.net [209.251.163.53] 4 <10 ms <10 ms <10 ms ga090-gr1.stl2.dbn.net [209.251.164.2] 5 <10 ms 10 ms 10 ms sl-gw5-kc-5-0-1-6M.sprintlink.net [144.232.132.5] 6 <10 ms 10 ms 10 ms sl-bb10-kc-1-3.sprintlink.net [144.232.2.61] 7 31 ms 30 ms 40 ms sl-bb10-chi-0-0.sprintlink.net [144.232.8.117] 8 30 ms 40 ms 30 ms 144.232.0.138 9 30 ms 40 ms 30 ms 144.228.252.13 10 60 ms 60 ms 70 ms 144.228.158.202 11 60 ms 60 ms 70 ms tiny.sprintlink.net [199.0.232.90] Trace complete. Dan Rabb digital broadcast network (314) 733-3127 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:34 PM To: nanog@merit.edu Subject: AT&T/Sprint problems AT&T seems to be completely gone, and Sprint connectivity is getting progressively worse. Anyone know what's going on? For instance: [ Mon Nov 30 12:24:21 ] [ root@pdx-s02 -> traceroute sprintlink.net traceroute to sprintlink.net (199.0.232.90), 30 hops max, 40 byte packets 1 pdx-pm01 (209.188.52.11) 1.055 ms 0.801 ms 0.774 ms 2 209.104.198.73 (209.104.198.73) 3.968 ms 4.637 ms 4.334 ms 3 a0-0-17.edge0.pao.priori.net (209.104.192.77) 111.857 ms 50.848 ms 40.709 ms 4 f0-0-0.plalic01.eli.net (207.173.115.249) 40.981 ms 40.323 ms 40.550 ms 5 a0-0--5.scrlic01.eli.net (207.173.113.141) 45.199 ms 48.857 ms 48.961 ms 6 sl-gw8-stk-12-0.sprintlink.net (144.228.107.17) 46.588 ms 276.005 ms 277. 638 ms 7 * * * etc. 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~