EVENT / POSSIBLE ROUTE LEAK / 8 NOV 2026, 20:19 UTC

Yes, ASPA would have stopped this

15,850 prefixes newly invalidpeak 8,005/min, usually 26.5/min8 min · 10 collectors

15,850 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
AS20764AS325714,371
AS1299AS32577,436
AS174AS32576,170
AS6830AS3257751
AS20764AS3491704
02

Whose prefixes

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

OriginPrefixes
AS111721,502
AS178531,208
AS16509789
AS38266551
AS45271432
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/20261108T2019Z · 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 ↗