Announced routes
Every prefix a peer of the route collectors sees with origin AS48629, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 185.170.131.0/24 | Invalid: origin | None | 2 0%low visibility |
| 185.86.160.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.86.161.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.86.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.86.163.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 38.56.95.0/24 | Valid | RIR databaseARIN | 672 100% |
| 143.20.45.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS48629's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.170.131.0/24 | ROAs covering it name AS210539, not AS48629. If AS48629 should announce it, add a ROA for AS48629. |
| Route object: none | 185.170.131.0/24 | No route object for it. Add a route object with origin AS48629 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48629 whose prefix no peer sees AS48629 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.159.187.0/24 | RIPE | Valid |
| 185.86.160.0/22 | RIPE | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.