Announced routes
Every prefix a peer of the route collectors sees with origin AS188, 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.
| 149.64.200.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 198.22.15.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 198.151.10.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS188'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: RIR3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 149.64.200.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.22.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.151.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS188 whose prefix no peer sees AS188 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 139.121.0.0/16 | ARIN | Valid |
| 149.64.0.0/16 | ARIN | Valid |
| 198.22.12.0/22 | ARIN | Valid |
| 198.151.8.0/21 | 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.