maybe host problem? I can reach to www.level3.com, but not www.level3.net. It seems both are belonging to same subnet.
Brandon Galbraith wrote: > In Chicago, traceroutes are dying in the same place (Denver). Peered out of > 350 Cermak. > > -brandon > > On Wed, Apr 15, 2009 at 2:45 PM, Charles Mills <w3y...@gmail.com> wrote: > > >> Can't get to level3.net 63.211.236.36 or www.level3.net 4.68.95.28 from >> Pittsburgh either and I peer directly with level3 with a full BGP feed. >> >> >> >> On Wed, Apr 15, 2009 at 3:35 PM, J. Oquendo <s...@infiltrated.net> wrote: >> >> >>> Anyone else experience sporadic funkiness via >>> Level3? I can't even reach the main website from who >>> knows how many networks I've tried. Also friends >>> and former colleagues have tried to reach the site >>> to no avail. >>> >>> One of my machines on AT&T: >>> # traceroute level3.net >>> traceroute to level3.net (63.211.236.36), 30 hops max, 40 byte packets >>> >>> 4 cr1.n54ny.ip.att.net (12.122.105.58) 11.285 ms 21.702 ms 21.477 >>> >> ms >> >>> 5 ggr2.n54ny.ip.att.net (12.122.131.141) 12.712 ms 10.194 ms 16.393 >>> ms >>> 6 so-8-0-0.car3.NewYork1.Level3.net (4.68.127.149) 9.975 ms 10.019 >>> >> ms >> >>> 10.833 ms >>> 7 vlan79.csw2.NewYork1.Level3.net (4.68.16.126) 10.162 ms 10.189 ms >>> 14.474 ms >>> 8 ae-71-71.ebr1.NewYork1.Level3.net (4.69.134.69) 15.763 ms 11.166 >>> >> ms >> >>> 9.725 ms >>> 9 ae-3-3.ebr4.Washington1.Level3.net (4.69.132.93) 16.139 ms 30.616 >>> >> ms >> >>> 16.275 ms >>> 10 ae-64-64.csw1.Washington1.Level3.net (4.69.134.178) 15.684 ms >>> ae-74-74.csw2.Washington1.Level3.net (4.69.134.182) 21.870 ms >>> ae-84-84.csw3.Washington1.Level3.net (4.69.134.186) 28.729 ms >>> 11 ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 17.035 ms >>> ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 17.041 ms >>> ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 21.940 ms >>> 12 ae-2-2.ebr2.Chicago2.Level3.net (4.69.132.69) 31.671 ms 42.407 ms >>> 45.774 ms >>> 13 ae-1-100.ebr1.Chicago2.Level3.net (4.69.132.113) 31.922 ms 32.115 >>> >> ms >> >>> 38.135 ms >>> 14 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 75.265 ms 67.528 ms >>> 67.937 ms >>> 15 ge-9-0.hsa1.Denver1.Level3.net (4.68.107.35) 62.587 ms !H >>> ge-9-1.hsa1.Denver1.Level3.net (4.68.107.99) 62.543 ms !H >>> ge-9-2.hsa1.Denver1.Level3.net (4.68.107.163) 75.797 ms !H >>> >>> >>> (From Texas through Above.net) >>> $ traceroute level3.net|tail -n 1 >>> traceroute to level3.net (63.211.236.36), 64 hops max, 40 byte packets >>> 11 ge-6-2.hsa1.Denver1.Level3.net (4.68.107.131) 21.473 ms !H * >>> ge-6-0.hsa1.Denver1.Level3.net (4.68.107.3) 21.547 ms !H >>> >>> Confirmed it can't be reached from Travelers Ins, The >>> Hartford, none of my connections. Anyone else seeing >>> issues? I'm seeing drop off from clients going through >>> their Atlanta interconnects with Charter and two other >>> providers, which I can't make sense of. I DO KNOW they >>> experienced some sort of issue with a TDM switch or so >>> they said... Very broad statements: "We know teh >>> interwebs are down please stand by" >>> >>> I know websites are one thing, but the chances of the >>> website going down, a TDM switch being wacky and now >>> clients traversing their networks complaining all at >>> once seems a little out of the ordinary. >>> >>> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ >>> J. Oquendo >>> SGFA, SGFE, C|EH, CNDA, CHFI, OSCP >>> >>> "It takes 20 years to build a reputation and five minutes to >>> ruin it. If you think about that, you'll do things >>> differently." - Warren Buffett >>> >>> 227C 5D35 7DCB 0893 95AA 4771 1DCE 1FD1 5CCD 6B5E >>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5CCD6B5E >>> >>> >>> >>> >> -- >> >> > > > >
