EVENT / POSSIBLE ROUTE LEAK / 10 NOV 2026, 08:19 UTC

Yes, ASPA would have stopped this

3,265 prefixes newly invalidpeak 2,329/min, usually 63.5/min3 min · 10 collectors

3,265 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
AS6881AS574632,113
AS12735AS574631,133
AS7018AS13979888
AS20057AS13979887
AS41327AS57463748
02

Whose prefixes

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

OriginPrefixes
AS20057883
AS12735517
AS34619113
AS4339188
AS19720784
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/20261110T0819Z · 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 ↗