EVENT / POSSIBLE ROUTE LEAK / 10 NOV 2026, 00:04 UTC

Yes, ASPA would have stopped this

22,208 prefixes newly invalidpeak 9,540/min, usually 80.5/min6 min · 12 collectors

22,208 prefixes took a path that contradicts a published ASPA. A network that enforces ASPA rejects every one of them, so the leak ends at its border instead of spreading.

01

Blocking attestations

The published ASPA objects these paths contradict. Each row reads: this network's ASPA does not list that neighbour, yet the route passed between them.

Network (its ASPA)Leaves outPrefixes
AS12735AS693921,913
AS1299AS693912,700
AS6762AS69394,655
AS3257AS69391,669
AS7018AS6939704
02

Whose prefixes

The origin networks with the most prefixes caught in this event.

OriginPrefixes
AS111721,538
AS116641,409
AS45271779
AS27947727
AS26611619
03

How to read this

An event is a minute in which far more prefixes turned ASPA-invalid than in the hour before, as seen on the public RIPE RIS Live stream and checked against every validated ASPA object. It is evidence, not a verdict: an incomplete ASPA produces the same picture as a leak, and this view only sees what RIS collectors see. Permanent address: aspa.wd6.net/event/20261110T0004Z · JSON · all events

WD6

Who's behind this

The ASPA Preview is a WD6 Labs project, run by WD6.NET, an Amsterdam network since 1999 (AS20495). Running your own network? We do IP transit and peering for hosters: IP transit ↗