EVENT / POSSIBLE ROUTE LEAK / 18 NOV 2026, 07:21 UTC
Yes, ASPA would have stopped this
9,627 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. The paths point at AS6939 as the network that passed them on.
Who passed it on
On these paths one network sits between the two blocking attestations: it received the route from a network that does not list it as a provider, and handed it to another network that does not list it either. That is the shape of a route leak. It can also mean one of those two ASPA objects is incomplete.
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.
Whose prefixes
The origin networks with the most prefixes caught in this event.
Example paths
Read from observer to origin. Highlighted hops are the blocking attestations; the leak sits between them.
| Prefix | AS path |
|---|---|
| 2a06:de05:61b6::/48 | AS20764→AS8359→AS1299→AS174→AS53667→AS199340 |
| 2001:4288:a102::/48 | AS20764→AS8359→AS1299→AS5511→AS6713 |
| 2602:ff03:960::/48 | AS20764→AS8359→AS1299→AS3257→AS20473 |
| 41.89.217.0/24 | AS20764→AS3257→AS174→AS36914 |
| 41.89.199.0/24 | AS20764→AS6762→AS174→AS36914 |
| 193.200.249.0/24 | AS49434→AS5511→AS174→AS57043→AS59965 |
| 187.55.51.0/24 | AS49434→AS6453→AS174→AS60068→AS154132 |
| 2a0d:3dc1:b4bc::/48 | AS20912→AS6939→AS8298→AS4601→AS210312 |
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/20261118T0721Z · JSON · all events
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 ↗