Re: Centurylink having a bad morning?
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
On Aug 30, 2020, at 5:36 AM, Mel Beckman <mel@beckman.org> wrote:
Can't get to pretty much anything on the Internet from my Tmobile device... not really sure whats going on =) -----Original Message----- From: Mel Beckman <mel@beckman.org> Sent: Sunday, August 30, 2020 8:43 AM To: Drew Weaver <drew.weaver@thenap.com> Cc: nanog@nanog.org Subject: Re: Centurylink having a bad morning? 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
On Aug 30, 2020, at 5:36 AM, Mel Beckman <mel@beckman.org> wrote:
One of my legacy L3 peers is only advertising 498174 prefixes. Very strange. Ben Russell -----Original Message----- From: NANOG <nanog-bounces+brussell=stratusnet.com@nanog.org> On Behalf Of Drew Weaver Sent: Sunday, August 30, 2020 7:45 AM To: 'Mel Beckman' <mel@beckman.org> Cc: 'nanog@nanog.org' <nanog@nanog.org> Subject: RE: Centurylink having a bad morning? Can't get to pretty much anything on the Internet from my Tmobile device... not really sure whats going on =) -----Original Message----- From: Mel Beckman <mel@beckman.org> Sent: Sunday, August 30, 2020 8:43 AM To: Drew Weaver <drew.weaver@thenap.com> Cc: nanog@nanog.org Subject: Re: Centurylink having a bad morning? 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
On Aug 30, 2020, at 5:36 AM, Mel Beckman <mel@beckman.org> wrote:
Yikes, they really need to get their reflectors fixed so that we can dis-engage from them. -----Original Message----- From: NANOG <nanog-bounces+drew.weaver=thenap.com@nanog.org> On Behalf Of Ben Russell Sent: Sunday, August 30, 2020 9:14 AM To: 'nanog@nanog.org' <nanog@nanog.org> Subject: RE: Centurylink having a bad morning? One of my legacy L3 peers is only advertising 498174 prefixes. Very strange. Ben Russell -----Original Message----- From: NANOG <nanog-bounces+brussell=stratusnet.com@nanog.org> On Behalf Of Drew Weaver Sent: Sunday, August 30, 2020 7:45 AM To: 'Mel Beckman' <mel@beckman.org> Cc: 'nanog@nanog.org' <nanog@nanog.org> Subject: RE: Centurylink having a bad morning? Can't get to pretty much anything on the Internet from my Tmobile device... not really sure whats going on =) -----Original Message----- From: Mel Beckman <mel@beckman.org> Sent: Sunday, August 30, 2020 8:43 AM To: Drew Weaver <drew.weaver@thenap.com> Cc: nanog@nanog.org Subject: Re: Centurylink having a bad morning? 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
On Aug 30, 2020, at 5:36 AM, Mel Beckman <mel@beckman.org> wrote:
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 -----Original Message----- From: NANOG <nanog-bounces+quincy.marshall=reged.com@nanog.org> On Behalf Of Drew Weaver Sent: Sunday, August 30, 2020 10:07 AM To: 'Ben Russell' <brussell@stratusnet.com>; 'nanog@nanog.org' <nanog@nanog.org> Subject: RE: Centurylink having a bad morning? Yikes, they really need to get their reflectors fixed so that we can dis-engage from them. -----Original Message----- From: NANOG <nanog-bounces+drew.weaver=thenap.com@nanog.org> On Behalf Of Ben Russell Sent: Sunday, August 30, 2020 9:14 AM To: 'nanog@nanog.org' <nanog@nanog.org> Subject: RE: Centurylink having a bad morning? One of my legacy L3 peers is only advertising 498174 prefixes. Very strange. Ben Russell -----Original Message----- From: NANOG <nanog-bounces+brussell=stratusnet.com@nanog.org> On Behalf Of Drew Weaver Sent: Sunday, August 30, 2020 7:45 AM To: 'Mel Beckman' <mel@beckman.org> Cc: 'nanog@nanog.org' <nanog@nanog.org> Subject: RE: Centurylink having a bad morning? Can't get to pretty much anything on the Internet from my Tmobile device... not really sure whats going on =) -----Original Message----- From: Mel Beckman <mel@beckman.org> Sent: Sunday, August 30, 2020 8:43 AM To: Drew Weaver <drew.weaver@thenap.com> Cc: nanog@nanog.org Subject: Re: Centurylink having a bad morning? 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
On Aug 30, 2020, at 5:36 AM, Mel Beckman <mel@beckman.org> wrote:
--------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com ---------------------------------------------------------------------------------------
participants (4)
-
Ben Russell -
Drew Weaver -
Marshall, Quincy -
Mel Beckman