See how selected public BGP collectors know about an address or network—and what materially changed during the last 72 hours.
Try , , or .
A separate, on-demand view from RouteViews—shown for comparison, never mixed into the local RIPE RIS mirror.
RouteViews did not return a current matching route for this query.
This address or network is not present in the currently loaded collector views. Check the data-health details before interpreting absence as a withdrawal.
Common observed paths, grouped by reporting peers. The full evidence remains in AS Paths.
| Peers | Observed AS path | Collectors | Last observed |
|---|---|---|---|
| Collector | Source | Seeing route | Active peers | Origins | Freshness |
|---|---|---|---|---|---|
Everything on the other tabs is live and complete: the current origin, RPKI validity, holder and AS names are resolved on demand. What is missing is the timeline — how this prefix changed over the last 72 hours — which requires a collector holding a continuous feed open, since that history cannot be backfilled after the fact.
RouteViews answers the current lookup, but it does not populate this timeline. Import one matching RIPE RIS RIB snapshot, then keep that same collector’s RIS Live process running. History starts at initialization; it is not retroactively backfilled, so a complete window takes 72 continuous hours.
backend/.venv/bin/python collector/snapshot.py <bview URL> --collector rrc00backend/.venv/bin/python collector/stream.py --collector rrc00This is only a stability statement for the coverage period shown above.