<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.css-901oao
{mso-style-name:css-901oao;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">It gets better …<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="https://twitter.com/g_bonfiglio/status/1300086336121176064">https://twitter.com/g_bonfiglio/status/1300086336121176064</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN">The day Telia (and NTT, and others) de-peered Level3.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">“</span><span class="css-901oao">AS1299 have temporarily disabled all IPv4 peering with CenturyLink AS3356 on their request.”<o:p></o:p></span></p>
<p class="MsoNormal"><span class="css-901oao"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Regards,<br>
<br>
Stephen Flynn<br>
Atlantic.Net<br>
Direct: (321) 206-1390<br>
<a href="mailto:sflynn@staff.atlantic.net">sflynn@staff.atlantic.net</a><br>
<a href="http://www.atlantic.net/">www.atlantic.net</a></span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Outages <outages-bounces@outages.org>
<b>On Behalf Of </b>Tino Montemor via Outages<br>
<b>Sent:</b> Sunday, August 30, 2020 11:06 AM<br>
<b>To:</b> outages@outages.org<br>
<b>Subject:</b> Re: [outages] Outages Digest, Vol 147, Issue 10<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="background:#B04800;padding:5.25pt 1.5pt 5.25pt 1.5pt">
<p class="MsoNormal" style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<o:p></o:p></p>
</td>
<td width="100%" style="width:100.0%;background:#FFE878;padding:5.25pt 3.75pt 5.25pt 11.25pt;word-wrap: break-word">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<strong><span style="color:#B04800">CAUTION:</span></strong><span style="color:#B04800"> This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.</span><o:p></o:p></p>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Just want to reflect (pun?) what others are saying, Centurylink wasn’t letting go of our routes.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As of about 2 minutes ago it seems out AS Prepend has finally began to propagate
<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">_____<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Tino Montemor | Skechers USA, Inc. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">O: 310-406-0132 M: 909-721-6673<o:p></o:p></p>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> Outages <<a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a>>
on behalf of <a href="mailto:outages-request@outages.org">outages-request@outages.org</a> <<a href="mailto:outages-request@outages.org">outages-request@outages.org</a>><br>
<b>Sent:</b> Sunday, August 30, 2020 6:32:35 AM<br>
<b>To:</b> <a href="mailto:outages@outages.org">outages@outages.org</a> <<a href="mailto:outages@outages.org">outages@outages.org</a>><br>
<b>Subject:</b> Outages Digest, Vol 147, Issue 10</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Send Outages mailing list submissions to<br>
<a href="mailto:outages@outages.org">outages@outages.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:outages-request@outages.org">outages-request@outages.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:outages-owner@outages.org">outages-owner@outages.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Outages digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: CenturyLink peering issues? (David Hubbard)<br>
2. Re: 3356 does not WITHDRAW bgp routes (randal k)<br>
3. Re: 3356 does not WITHDRAW bgp routes (David Hubbard)<br>
4. Re: CenturyLink peering issues? (Chris Adams)<br>
5. Re: 3356 does not WITHDRAW bgp routes (randal k)<br>
6. Re: CenturyLink peering issues? (Stephen Flynn)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 30 Aug 2020 12:22:27 +0000<br>
From: David Hubbard <<a href="mailto:dhubbard@dino.hostasaurus.com">dhubbard@dino.hostasaurus.com</a>><br>
To: "<a href="mailto:outages@outages.org">outages@outages.org</a>" <<a href="mailto:outages@outages.org">outages@outages.org</a>><br>
Subject: Re: [outages] CenturyLink peering issues?<br>
Message-ID:<br>
<<a href="mailto:D5BED54B-45C3-4EC8-9DBA-EF1276D52C73@dino.hostasaurus.com">D5BED54B-45C3-4EC8-9DBA-EF1276D52C73@dino.hostasaurus.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Ugh; seeing same thing. Have had sessions turned down for over two hours and looking glasses are still showing 3356 propagating the advertisements.<br>
<br>
?On 8/30/20, 8:11 AM, "Outages on behalf of Chris Adams via Outages" <<a href="mailto:outages-bounces@outages.org%20on%20behalf%20of%20outages@outages.org">outages-bounces@outages.org on behalf of outages@outages.org</a>> wrote:<br>
<br>
Once upon a time, Stephen Flynn via Outages <<a href="mailto:outages@outages.org">outages@outages.org</a>> said:<br>
> Odd part --- I disconnected my Level3 circuit at the ORL-FL facility so that I could fully failover to my other carrier link.<br>
> Level3 is still advertising my routes, even though my link and BGP session is down.<br>
<br>
I can confirm this - I shut down IPv4 BGP with Level3 in Chicago, but<br>
checking route-views and such, they're still advertising our routes (but<br>
don't know how to get to us once packets hit their network)..<br>
<br>
AS7007 all over again?<br>
-- <br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 30 Aug 2020 06:33:41 -0600<br>
From: randal k <<a href="mailto:rkohutek+outages@gmail.com">rkohutek+outages@gmail.com</a>><br>
To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
Subject: Re: [outages] 3356 does not WITHDRAW bgp routes<br>
Message-ID:<br>
<<a href="mailto:CANeLk7RmHnXa=EieXpahpmM966bL8==7qsywR89Yrd0fuZ9tHA@mail.gmail.com">CANeLk7RmHnXa=EieXpahpmM966bL8==7qsywR89Yrd0fuZ9tHA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Seeing the same thing - shut a peer, still seeing those routes via<br>
3356 across multiple route-servers & looking glasses.<br>
<br>
So, do we disconnect 3356 and suffer the blackhole in hopes that it<br>
will eventually withdraw those routes, or leave it on to prevent<br>
blackholing but suffer massive packet loss to other carriers? Wow.<br>
<br>
On Sun, Aug 30, 2020 at 6:28 AM Lukas Tribus via Outages<br>
<<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br>
><br>
> As previously mentioned by Stephen Flynn, 3356 does not WITHDRAW stale<br>
> bgp routes, can be confirmed with AT&T's route server at (telnet<br>
> route-server.ip.att.net).<br>
><br>
> Stale routes from 1 hour + are still announced by 3356.<br>
><br>
><br>
> This is causing blackholing.<br>
> _______________________________________________<br>
> Outages mailing list<br>
> <a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 30 Aug 2020 12:47:57 +0000<br>
From: David Hubbard <<a href="mailto:dhubbard@dino.hostasaurus.com">dhubbard@dino.hostasaurus.com</a>><br>
To: "<a href="mailto:outages@outages.org">outages@outages.org</a>" <<a href="mailto:outages@outages.org">outages@outages.org</a>><br>
Subject: Re: [outages] 3356 does not WITHDRAW bgp routes<br>
Message-ID:<br>
<<a href="mailto:4BA8D9E3-9A4F-45FB-AFE4-8BBB2E3C6902@dino.hostasaurus.com">4BA8D9E3-9A4F-45FB-AFE4-8BBB2E3C6902@dino.hostasaurus.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I tried bringing two circuits back up hoping to not have blackholing, one never left idle, the other received <2000 routes, which I know from prior outages to mean that the entire region (Tampa Bay) has been BGP isolated from the rest of their network. Good
times...<br>
<br>
?On 8/30/20, 8:43 AM, "Outages on behalf of randal k via Outages" <<a href="mailto:outages-bounces@outages.org%20on%20behalf%20of%20outages@outages.org">outages-bounces@outages.org on behalf of outages@outages.org</a>> wrote:<br>
<br>
Seeing the same thing - shut a peer, still seeing those routes via<br>
3356 across multiple route-servers & looking glasses.<br>
<br>
So, do we disconnect 3356 and suffer the blackhole in hopes that it<br>
will eventually withdraw those routes, or leave it on to prevent<br>
blackholing but suffer massive packet loss to other carriers? Wow.<br>
<br>
On Sun, Aug 30, 2020 at 6:28 AM Lukas Tribus via Outages<br>
<<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br>
><br>
> As previously mentioned by Stephen Flynn, 3356 does not WITHDRAW stale<br>
> bgp routes, can be confirmed with AT&T's route server at (telnet<br>
> route-server.ip.att.net).<br>
><br>
> Stale routes from 1 hour + are still announced by 3356.<br>
><br>
><br>
> This is causing blackholing.<br>
> _______________________________________________<br>
> Outages mailing list<br>
> <a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sun, 30 Aug 2020 07:48:14 -0500<br>
From: Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
Subject: Re: [outages] CenturyLink peering issues?<br>
Message-ID: <<a href="mailto:20200830124814.GB29578@cmadams.net">20200830124814.GB29578@cmadams.net</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Once upon a time, randal k <<a href="mailto:rkohutek+outages@gmail.com">rkohutek+outages@gmail.com</a>> said:<br>
> It's weird you say that - I have been attempting to use Level3's well<br>
> known communities to attempt to prepend, no-export etc and have been<br>
> having limited luck ... and those communities even appear in<br>
> route-views, so I know they're being sent!<br>
<br>
I brought my session back up, not accepting any routes, and prepending<br>
ours (just in case the change propagated)... it took a while, but<br>
eventually I do see the prepended routes.<br>
<br>
But for a provider that said they shut down their link to Level3, I<br>
still see their routes... possibly (slowly) propagating changes but not<br>
actual withdraws?<br>
-- <br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sun, 30 Aug 2020 06:52:16 -0600<br>
From: randal k <<a href="mailto:rkohutek+outages@gmail.com">rkohutek+outages@gmail.com</a>><br>
To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
Subject: Re: [outages] 3356 does not WITHDRAW bgp routes<br>
Message-ID:<br>
<<a href="mailto:CANeLk7RcTGWkQp4SYJQO=j=c04dTpYSGrXTxfK9ovi_QkgyxZQ@mail.gmail.com">CANeLk7RcTGWkQp4SYJQO=j=c04dTpYSGrXTxfK9ovi_QkgyxZQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Watching closely, after applying ^3356$ on our inbound routes, I can<br>
see that they are bouncing sessions and slowly adding in prefixes -- I<br>
have 17x 3356-originated routes in PA, and 893x in CO. And they have<br>
reset the PA BGP session numerous times.<br>
<br>
On Sun, Aug 30, 2020 at 6:33 AM randal k <<a href="mailto:rkohutek+outages@gmail.com">rkohutek+outages@gmail.com</a>> wrote:<br>
><br>
> Seeing the same thing - shut a peer, still seeing those routes via<br>
> 3356 across multiple route-servers & looking glasses.<br>
><br>
> So, do we disconnect 3356 and suffer the blackhole in hopes that it<br>
> will eventually withdraw those routes, or leave it on to prevent<br>
> blackholing but suffer massive packet loss to other carriers? Wow.<br>
><br>
> On Sun, Aug 30, 2020 at 6:28 AM Lukas Tribus via Outages<br>
> <<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br>
> ><br>
> > As previously mentioned by Stephen Flynn, 3356 does not WITHDRAW stale<br>
> > bgp routes, can be confirmed with AT&T's route server at (telnet<br>
> > route-server.ip.att.net).<br>
> ><br>
> > Stale routes from 1 hour + are still announced by 3356.<br>
> ><br>
> ><br>
> > This is causing blackholing.<br>
> > _______________________________________________<br>
> > Outages mailing list<br>
> > <a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
> > <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Sun, 30 Aug 2020 13:32:31 +0000<br>
From: Stephen Flynn <<a href="mailto:sflynn@staff.atlantic.net">sflynn@staff.atlantic.net</a>><br>
To: "<a href="mailto:outages@outages.org">outages@outages.org</a>" <<a href="mailto:outages@outages.org">outages@outages.org</a>><br>
Subject: Re: [outages] CenturyLink peering issues?<br>
Message-ID:<br>
<<a href="mailto:BN6PR19MB10269D437047598C160A6724EB500@BN6PR19MB1026.namprd19.prod.outlook.com">BN6PR19MB10269D437047598C160A6724EB500@BN6PR19MB1026.namprd19.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Just attempted a prepend (x4) on my Level3 advertisements --- only noticed a change within the NTT network tables.<br>
Other large carriers received no advertisement changes (Telia, Hurricane Electric, AT&T)<br>
<br>
I then noticed that my BGP session was constantly flapping. I've now shutdown my circuit again. Level3 is still announcing my address space.<br>
Thank you Level3!<br>
<br>
<br>
Regards,<br>
<br>
Stephen Flynn<br>
Atlantic.Net<br>
Direct: (321) 206-1390<br>
<a href="mailto:sflynn@staff.atlantic.net">sflynn@staff.atlantic.net</a><br>
<a href="http://www.atlantic.net">www.atlantic.net</a><br>
<br>
<br>
-----Original Message-----<br>
From: Outages <<a href="mailto:outages-bounces@outages.org">outages-bounces@outages.org</a>> On Behalf Of Chris Adams via Outages<br>
Sent: Sunday, August 30, 2020 8:48 AM<br>
To: <a href="mailto:outages@outages.org">outages@outages.org</a><br>
Subject: Re: [outages] CenturyLink peering issues?<br>
<br>
<br>
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.<br>
<br>
<br>
Once upon a time, randal k <<a href="mailto:rkohutek+outages@gmail.com">rkohutek+outages@gmail.com</a>> said:<br>
> It's weird you say that - I have been attempting to use Level3's well <br>
> known communities to attempt to prepend, no-export etc and have been <br>
> having limited luck ... and those communities even appear in <br>
> route-views, so I know they're being sent!<br>
<br>
I brought my session back up, not accepting any routes, and prepending ours (just in case the change propagated)... it took a while, but eventually I do see the prepended routes.<br>
<br>
But for a provider that said they shut down their link to Level3, I still see their routes... possibly (slowly) propagating changes but not actual withdraws?<br>
--<br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=bFAhm8rB5vXbGyJn-mWQSZrkEgY9uWkKpuo-JUqRuG4&r=Z3AiGMt06fETQSnc5l2T7vSIOF-bixsu4CbUYvAlOxM&m=Lr0Sp0x0UoGt1nlwfLsZu9_oFAIXiSqjH50CkdMWtVc&s=JPfcY3xr11kFtDNgRuUxEfMQsBNdk3iRqqwiw04UU60&e=</a>
<br>
<br>
<br>
------------------------------<br>
<br>
End of Outages Digest, Vol 147, Issue 10<br>
****************************************<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>