EVENT / POSSIBLE ROUTE LEAK / 9 NOV 2026, 15:03 UTC

Yes, ASPA would have stopped this

70,618 prefixes newly invalidpeak 9,887/min, usually 37.5/min25 min · 12 collectors

70,618 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
AS2027AS6013269,291
AS3257AS6013267,252
AS3320AS6461532
AS6730AS8218304
AS20764AS8359243
02

Whose prefixes

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

OriginPrefixes
AS123892,681
AS70292,624
AS60792,329
AS32571,802
AS114041,694
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/20261109T1503Z · 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 ↗