On 08/30/2020 around 5:30AM CDT, one of our upstream providers,
(and one of the largest internet Tier-1 backbone providers) had
a global routing meltdown, and all traffic that was supposed to be
handled by them was dropped to the floor.
We had shutdown our peer with them, but even though our peer was
shutdown, they were still announcing our route prefixes (even though
this should not work this way), still causing major network disruptions.
Around 8:30AM with consultation with other providers, we implemented a
different workaround to still keep our peer session up with
Centurylink/Level3 but not take any route prefixes from them.
In other providers tests, this was working much better to combat
against Centurylink's routing problems.
The problems with CenturyLink are far reaching, they handle a
significant amount of traffic on the Internet, and this disrupted
traffic for many services around the Internet.
We'll continue monitoring Centurylink's issues as the day goes on.
Thank you.
--
Doug McIntyre <[log in to unmask]>
-- ipHouse/Green Cloud Technologies --
Network Engineer/Provisioning/Jack of all Trades
