EVENT / POSSIBLE ROUTE LEAK / 10 NOV 2026, 01:16 UTC

Yes, ASPA would have stopped this

7,282 prefixes newly invalidpeak 7,282/min, usually 56.5/min1 min · 7 collectors

7,282 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
AS20764AS32577,210
AS1299AS32577,207
AS20764AS835942
AS1299AS835938
AS174AS32579
02

Whose prefixes

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

OriginPrefixes
AS111721,434
AS26611415
AS45271324
AS12252299
AS13335253
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/20261110T0116Z · 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 ↗