Announced routes
Every prefix a peer of the route collectors sees with origin AS37738, 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.
| 102.222.212.0/24 | No ROA | Other IRR onlyALTDB | 264 39% |
| 2c0f:5f40::/48 | Valid | Nonecovered by 2c0f:5f40::/32 | 635 100% |
| 102.210.212.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 102.210.213.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 102.210.214.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 102.210.215.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.200.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.201.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.202.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.203.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.204.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.205.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.206.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 154.70.207.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 2c0f:5400:2::/48 | Valid | RIR databaseAFRINIC | 635 100% |
| 2c0f:5400:3::/48 | Valid | RIR databaseAFRINIC | 635 100% |
| 2c0f:5400:4::/48 | Valid | RIR databaseAFRINIC | 635 100% |
| 2c0f:5400:5::/48 | Valid | RIR databaseAFRINIC | 635 100% |
AS-SET
AS37738'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 9 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.222.212.0/24 | No ROA covers it. Add a ROA for AS37738, maxLength 24. |
| Route object: RIR | 102.222.212.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: none | 2c0f:5f40::/48 | No route object for it. A route object for 2c0f:5f40::/32 with origin AS37738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37738 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS37738 whose prefix no peer sees AS37738 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.210.212.0/22 | AFRINIC | Valid |
| 154.70.200.0/21 | AFRINIC | Valid |
| 2c0f:5400::/32 | AFRINIC | Valid |
| 2c0f:5400::/48 | AFRINIC | Valid |
| 2c0f:5400:6::/48 | AFRINIC | Valid |
| 2c0f:5f40::/32 | AFRINIC | 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.