Announced routes
Every prefix a peer of the route collectors sees with origin AS265838, 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.224.118.0/24 | Valid | Nonecovered by 45.224.116.0/22 | 666 99% |
| 45.224.117.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.224.116.0/24 | Valid | Other IRR onlyRADB | 666 99% |
AS-SET
AS265838'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 7 are in fix.csv.
- Route object: none1
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.224.118.0/24 | No route object for it. A route object for 45.224.116.0/22 with origin AS265838 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265838 in the RIR database for the space. |
| Route object: RIR | 45.224.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.224.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265838 whose prefix no peer sees AS265838 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.224.116.0/22 | LACNIC | Valid |
| 45.224.116.0/23 | RADB | Valid |
| 45.224.119.0/24 | RADB | Valid |
| 2803:e220::/32 | RADB | 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.