Level3 funkiness

Blake Pfankuch bpfankuch at cpgreeley.com
Wed Apr 15 15:11:34 CDT 2009


 2  dvr-edge-05.inet.qwest.net (72.165.27.181)  27.696 ms  27.688 ms  28.022 ms
 3  dvr-core-01.inet.qwest.net (205.171.10.89)  28.010 ms  28.001 ms  27.990 ms
 4  * * 67.14.2.89 (67.14.2.89)  50.773 ms
 5  xe-8-2-0.edge2.dallas3.level3.net (4.68.63.53)  51.120 ms xe-8-1-0.edge2.dallas3.level3.net (4.68.63.49)  51.107 ms  51.099 ms
 6  vlan79.csw2.Dallas1.Level3.net (4.68.19.126)  56.763 ms  37.806 ms vlan89.csw3.Dallas1.Level3.net (4.68.19.190)  33.368 ms
 7  ae-82-82.ebr2.Dallas1.Level3.net (4.69.136.145)  35.514 ms ae-72-72.ebr2.Dallas1.Level3.net (4.69.136.141)  44.125 ms ae-62-62.ebr2.Dallas1.Level3.net (4.69.136.137)  44.120 ms
 8  ae-2.ebr1.Denver1.Level3.net (4.69.132.105)  50.913 ms  50.895 ms  50.522 ms
 9  ge-6-0.hsa1.Denver1.Level3.net (4.68.107.3)  45.675 ms !H ge-6-1.hsa1.Denver1.Level3.net (4.68.107.67)  46.875 ms !H *



-----Original Message-----
From: J. Oquendo [mailto:sil at infiltrated.net]
Sent: Wednesday, April 15, 2009 1:36 PM
To: nanog at nanog.org
Subject: Level3 funkiness


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






More information about the NANOG mailing list