Announced routes
Every prefix a peer of the route collectors sees with origin AS205397, 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.
| 45.74.61.0/24 | No ROA | Other origin only | 3 0%low visibility |
| 102.135.10.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 101.1.16.0/24 | Valid | RIR databaseAPNIC | 669 99% |
AS-SET
AS205397'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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.74.61.0/24 | No ROA covers it. Add a ROA for AS205397, maxLength 24. |
| Route object: none | 45.74.61.0/24 | Route objects for it name AS36351. Add a route object with origin AS205397 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205397 whose prefix no peer sees AS205397 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 101.1.16.0/23 | APNIC | Valid |
| 101.1.17.0/24 | APNIC | Invalid: maxLength |
| 2a03:5840:130::/48 | RIPE | 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.