PROJECT 02 / ASPA PREVIEW

What ASPA
would drop today

RIPE RIS Liverpki-clientUpdated every minute

ASPA lets a network publish who its upstream providers are. Routers that enforce it reject paths that could only exist through a route leak. This page checks the public BGP stream against every published ASPA object and shows what enforcement would remove right now.

Live state

Loading Waiting for the first summary…
Prefixes seen—last 60 minutes
With an invalid path— 
With a valid path—every hop attested
Invalid routes—distinct prefix + path
ASPA objects— 
RIS collectors— 
01

Check your network

Before publishing an ASPA, or to audit one: see which networks carry your routes, which of them behave like transit providers, and whether your attestation would make any observed path invalid.

02

ASPA lint

Published ASPA objects that keep making real routes invalid. Each row is a network whose ASPA leaves out a neighbour, while that neighbour has carried its routes for hours. When the neighbour also passes those routes on to Tier-1 networks, it behaves like a provider that is missing from the ASPA: networks that enforce ASPA would drop those paths.

 

Network (its ASPA)Leaves outPrefixesOwnCollectorsSeen forReading
No data yet.

Evidence, not a verdict. This view only sees routes that changed in the last 24 hours on RIPE RIS, and a long-running route leak looks the same as a missing provider. Click a network for its full report and feed. Is a row about your network wrong? peering@wd6.net

03

Events

Prefixes that turn invalid for the first time in an hour, per minute. A burst far above the recent norm is recorded as an event, usually a route leak. Bursts right after an RPKI refresh are labelled as ASPA updates. Every event keeps a permanent page. All events · Atom feed

−60 min now

No data yet.

04

Blocking attestations

Every invalid path has a gap: the climb from the origin and the descent from the observer cannot meet. Each side of that gap ends at an AS whose ASPA excludes the next hop. Either the route leaked in between, or that ASPA is incomplete. Ranked by distinct prefixes affected.

AS (attests)ExcludesPrefixesRoutesOriginsObservers
No data yet.
05

Recent invalid paths

Paths read from observer to origin. Highlighted hops are the two blocking attestations; the leak, or the missing provider, sits between them. Most recent first, at most 200.

PrefixAS pathCollectorsLast seen
No data yet.
06

Method

A / SOURCE

RIS Live

Every BGP announcement from all RIPE RIS route collectors, as it happens. Prepends are collapsed; paths with AS_SETs are counted separately.

B / VALIDATION

rpki-client

All five RIR trust anchors, refreshed every fifteen minutes over RRDP. Repositories that only offer rsync are not included.

C / ALGORITHM

Downstream check

RIS peers send full tables, so each collector is treated as a customer of its peer and paths are checked with the downstream procedure of draft-ietf-sidrops-aspa-verification.

Provider hints in the network check use valley-free routing: a neighbour that passes your routes on to a Tier-1 network is treated as a likely provider. It only sees routes that changed in the last 24 hours, since RIS Live streams updates rather than full tables. Route leaks and incomplete visibility can mislead it, so check suggestions against your transit contracts.

An invalid path is evidence, not a verdict. It shows where a published attestation and observed routing disagree. Counts are distinct prefixes and routes over the last hour, so a single busy session cannot inflate them.

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 ↗ · peering@wd6.net