nanog mailing list archives

Re: 1.1.1.1


From: Saku Ytti via NANOG <nanog () lists nanog org>
Date: Wed, 16 Jul 2025 18:24:55 +0300

Any amount of redundancy can be fixed by automation.

On Wed, 16 Jul 2025 at 17:15, Tom Beecher via NANOG
<nanog () lists nanog org> wrote:

Now that everyone has gotten the RPKI rage out of their system, Cloudflare
is taking responsibility for this event. Explicitly stated it wasn't a
hijack, but their own mistake.

https://blog.cloudflare.com/cloudflare-1-1-1-1-incident-on-july-14-2025/

On Tue, Jul 15, 2025 at 3:56 PM Noah van der Aa via NANOG <
nanog () lists nanog org> wrote:

On 15/07/2025 21:18, Marco Moock via NANOG wrote:
Didn't RPKI and IR avoid any damage?

Yes - these route leaks didn't actually propagate very far.

The only reason they even appeared is because the actual route announced
by CF disappeared.
All 1.1.1.1 related prefixes (v6 included) were withdrawn around the
same time. RIPE's BGPlay tool [0] shows the massive withdrawal spike
quite nicely.

[0] https://stat.ripe.net/bgplay

_______________________________________________
NANOG mailing list

https://lists.nanog.org/archives/list/nanog () lists nanog org/message/FP2NP3F4A422JXTPBMVOUSNR6FYVYPUH/

_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/7NDDV33O26BWTWD2IBUJBNOGJWJQI3KB/



-- 
  ++ytti
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/DGUVO74MWNNPMIJZEYANSP235OAMNHMH/

Current thread: