Announced routes
Every prefix a peer of the route collectors sees with origin AS62998, 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.
| 107.173.39.0/24 | No ROA | None | 646 96% |
| 107.174.106.0/24 | Valid | RIR databaseARIN | 672 100% |
| 155.94.138.0/24 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS62998'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: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 107.173.39.0/24 | No ROA covers it. Add a ROA for AS62998, maxLength 24. |
| Route object: none | 107.173.39.0/24 | No route object for it. Add a route object with origin AS62998 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62998 whose prefix no peer sees AS62998 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 155.94.130.0/24 | ARIN | Valid |
| 155.94.165.0/24 | ARIN | Valid |
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.