Centurylink having a bad morning?

Mailman List Mirror (Read Only)
1

One anomaly I’ve just notice: we can’t reach 209.244.0.1 (ns1.level3.com) from anywhere on the Internet, including our CL connections. Traceroute fails at 4.16.30.129 (lag-101.ear2.LosAngeles1.Level3.net) with 65% packet loss:

traceroute to 209.244.0.1 (209.244.0.1), 30 hops max, 56 byte packets
1 sent:79 loss:100% last:0 ms avg:0 ms
2 sent:79 loss:0% last:15.483 ms avg:28.071 ms
    172.102.107.166
3 sent:79 loss:2.5% last:140.81 ms avg:33.374 ms
    ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49)
4 sent:78 loss:0% last:11.695 ms avg:23.637 ms
    ae1---0.cbr01.lsan.ca.frontiernet.net (74.40.3.214)
5 sent:78 loss:65.4% last:13.844 ms avg:19.393 ms
    lag-101.ear2.LosAngeles1.Level3.net (4.16.30.129)
6 sent:78 loss:100% last:0 ms avg:0 ms
7 sent:78 loss:100% last:0 ms avg:0 ms
8 sent:78 loss:100% last:0 ms avg:0 ms
9 sent:78 loss:100% last:0 ms avg:0 ms
10 sent:78 loss:100% last:0 ms avg:0 ms

-mel beckman

2

Can't get to pretty much anything on the Internet from my Tmobile device... not really sure whats going on =)

3

One of my legacy L3 peers is only advertising 498174 prefixes. Very strange.

Ben Russell

4

Yikes, they really need to get their reflectors fixed so that we can dis-engage from them.

5

My systems dropped CL about 03 this morning. Appears that a correction has been applied as I am seeing more normal traffic from CL. Still no access to their portal and the phone is a mess.

LQ. Marshall | Sr. Network Engineer | RegEd