Announced routes
Every prefix a peer of the route collectors sees with origin AS271541, 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.
| 181.232.250.0/23 | Valid | Other IRR onlyALTDB, RADB | 672 100% |
| 181.232.250.0/24 | Valid | Other IRR onlyALTDB | 672 100% |
| 181.232.251.0/24 | Valid | Other IRR onlyALTDB | 672 100% |
| 2801:80:3e70::/47 | Valid | Other IRR onlyALTDB, RADB | 634 100% |
AS-SET
AS271541'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 6 are in fix.csv.
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 181.232.250.0/23 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.250.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.251.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2801:80:3e70::/47 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271541 whose prefix no peer sees AS271541 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2801:80:3e70::/48 | ALTDB | Invalid: maxLength |
| 2801:80:3e71::/48 | ALTDB | Invalid: maxLength |
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.