Verizon Routing issue

Mon Jun 24 14:44:41 UTC 2019

(Updating subject line to be accurate)

> On Jun 24, 2019, at 10:28 AM, Max Tulyev <maxtul at netassist.ua> wrote:
> 
> Hi All,
> 
> here in Ukraine we got an impact as well!
> 
> Have two questions:
> 
> 1. Why Cloudflare did not immediately announced all their address space by /24s? This can put the service up instantly for almost all places.

They may not want to pollute the global routing table with these entries.  It has a cost for everyone.  If we all did this, the table would be a mess.

> 2. Why almost all carriers did not filter the leak on their side, but waited for "a better weather on Mars" for several hours?

There’s several major issues here

- Verizon accepted garbage from their customer
- Other networks accepted the garbage from Verizon (eg: Cogent)
- known best practices from over a decade ago are not applied

I’m sure reporters will be reaching out to Verizon about this and their response time should be noted.

It was impacting to many networks.  You should filter your transits to prevent impact from these more specifics.

- Jared

https://twitter.com/jaredmauch/status/1143163212822720513
https://twitter.com/JobSnijders/status/1143163271693963266
https://puck.nether.net/~jared/blog/?p=208