Is it just me or is Sprint having issues tonight? I noticed some routing problems getting to C&W hosted sites via Sprint. When I tried to go to www.sprint.net, I couldn't resolve it. According to F, sprint.net's NS's are: NS1-AUTH.SPRINTLINK.net. 2D IN A 206.228.179.10 NS2-AUTH.SPRINTLINK.net. 2D IN A 144.228.254.10 NS3-AUTH.SPRINTLINK.net. 2D IN A 144.228.255.10 These are all currently unreachable from our site (directly connected to Sprint and UUNet) and multiple offsite locations on other backbones. If I traceroute from atlantic.net (goes out via Sprint) to my own site (www.lewis.org) hosted off a C&W T1, I get 2 hops into C&W, and then nothing. If I trace from www.lewis.org to atlantic.net, I get 2 hops into Sprint, and then nothing. Before anyone asks...yes, I did call Sprint and run this all by them...and they opened a ticket...but the fact that seemed more interested in doing intrusive testing on our T3 than looking at their own network didn't instill much confidence. ---------------------------------------------------------------------- Jon Lewis *jlewis@lewis.org*| Spammers will be winnuked or System Administrator | nestea'd...whatever it takes Atlantic Net | to get the job done. _________http://www.lewis.org/~jlewis/pgp for PGP public key__________
Is it just me or is Sprint having issues tonight? I noticed some routing problems getting to C&W hosted sites via Sprint. When I tried to go to www.sprint.net, I couldn't resolve it. According to F, sprint.net's NS's are:
I'm having problems getting to them from any of Bell Atlantic, Qwest, ATT, and FNSI. This is what I get: traceroute to 205.161.150.10 (205.161.150.10), 30 hops max, 40 byte packets 1 mlbg-cisco1.valkyrie.net (216.28.208.1) 0.560 ms 0.516 ms 0.498 ms 2 10.0.0.254 (10.0.0.254) 3.854 ms 2.320 ms 15.090 ms 3 core1-hssi194-VALKYRIE.Columbus.fnsi.net (216.28.124.237) 27.433 ms 15.166 ms 10.864 ms 4 s2-1-0.ar1.CLE1.globalcenter.net (204.246.200.161) 13.401 ms 57.557 ms 28.739 ms 5 pos2-0-155M.cr2.CLE1.gblx.net (206.132.111.129) 20.358 ms 13.445 ms 13.506 ms 6 pos0-0-622M.cr2.NYC2.gblx.net (206.132.249.158) 76.148 ms 57.577 ms 50.716 ms 7 208.51.66.22 (208.51.66.22) 56.659 ms 86.165 ms 70.022 ms 8 144.232.171.129 (144.232.171.129) 49.299 ms 174.081 ms 210.255 ms 9 144.232.7.5 (144.232.7.5) 190.847 ms 31.009 ms 40.972 ms 10 144.232.9.226 (144.232.9.226) 101.685 ms 178.979 ms 176.402 ms 11 144.232.7.209 (144.232.7.209) 156.856 ms 107.443 ms 32.757 ms 12 144.232.0.30 (144.232.0.30) 36.669 ms 61.025 ms 103.171 ms 13 144.232.0.66 (144.232.0.66) 83.153 ms 31.524 ms 59.179 ms 14 * * * 15 * * * (and so on...to 30) and traceroute to 205.161.150.10 (205.161.150.10), 30 hops max, 38 byte packets 1 10.1.3.1 (10.1.3.1) 122.842 ms 37.881 ms 26.726 ms 2 151.200.4.66 (151.200.4.66) 23.846 ms 27.925 ms 23.968 ms 3 205.171.59.29 (205.171.59.29) 27.332 ms 25.078 ms 25.368 ms 4 wdc-core-01.inet.qwest.net (205.171.24.13) 27.326 ms 27.583 ms 25.364 ms 5 wdc-brdr-03.inet.qwest.net (205.171.24.38) 25.956 ms 27.674 ms 29.492 ms 6 205.171.4.238 (205.171.4.238) 28.739 ms 29.176 ms 30.189 ms 7 sl-bb10-rly-0-2.sprintlink.net (144.232.0.37) 27.328 ms 31.116 ms 28.813 ms 8 144.232.0.30 (144.232.0.30) 28.038 ms 27.348 ms 30.113 ms 9 144.232.0.66 (144.232.0.66) 28.017 ms 29.313 ms 28.111 ms 10 * * * 11 * * * 12 * * * 13 * * * (and so on...to 30) I just talked to sprint and they tell me that they know about the problem, but they don't know what it is. Sprint is in the process of opening a master ticket at the moment, but they didn't have the number to give to me right away, and I didn't feel like holding. They obviously have no ETR. -- Nick Bastin Software Developer OPNET Technologies
participants (2)
-
jlewis＠lewis.org -
Nick Bastin