20IPv4 routes
0.0% RPKI valid · 70.0% with a route object
1IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
21No ROA
6 with no route object for this origin
8Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS1880, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS1880, 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.
| 192.36.147.0/24 | No ROA | Other origin only | 41 6%low visibility |
| 192.108.198.0/23 | No ROA | None | 41 6%low visibility |
| 192.108.209.0/24 | No ROA | Nonecovered by 192.108.208.0/22 | 41 6%low visibility |
| 192.108.212.0/23 | No ROA | None | 41 6%low visibility |
| 204.29.132.0/23 | No ROA | None | 41 6%low visibility |
| 204.29.132.0/24 | No ROA | None | 41 6%low visibility |
| 2001:440:1880::/48 | No ROA | Other IRR onlyNTTCOM | 1 0%low visibility |
| 192.36.143.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.195.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.196.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.198.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.199.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.200.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.202.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 672 100% |
| 192.108.203.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.204.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.208.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.211.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.213.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.214.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.108.197.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 2 0%low visibility |
AS-SET
AS1880'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 35 are in fix.csv.
- ROA: none21
- Route object: none6
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.36.147.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| Route object: none | 192.36.147.0/24 | Route objects for it name AS1257. Add a route object with origin AS1880 in the RIR database for the space. |
| ROA: none | 192.108.198.0/23 | No ROA covers it. Add a ROA for AS1880, maxLength 23. |
| Route object: none | 192.108.198.0/23 | No route object for it. Add a route object with origin AS1880 in the RIR database for the space. |
| ROA: none | 192.108.209.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| Route object: none | 192.108.209.0/24 | No route object for it. A route object for 192.108.208.0/22 with origin AS1880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1880 in the RIR database for the space. |
| ROA: none | 192.108.212.0/23 | No ROA covers it. Add a ROA for AS1880, maxLength 23. |
| Route object: none | 192.108.212.0/23 | No route object for it. Add a route object with origin AS1880 in the RIR database for the space. |
| ROA: none | 204.29.132.0/23 | No ROA covers it. Add a ROA for AS1880, maxLength 23. |
| Route object: none | 204.29.132.0/23 | No route object for it. Add a route object with origin AS1880 in the RIR database for the space. |
| ROA: none | 204.29.132.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| Route object: none | 204.29.132.0/24 | No route object for it. Add a route object with origin AS1880 in the RIR database for the space. |
| ROA: none | 2001:440:1880::/48 | No ROA covers it. Add a ROA for AS1880, maxLength 48. |
| Route object: RIR | 2001:440:1880::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 192.36.143.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.195.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.196.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.198.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.199.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.200.0/21 | No ROA covers it. Add a ROA for AS1880, maxLength 21. |
| ROA: none | 192.108.202.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.203.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.204.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.208.0/22 | No ROA covers it. Add a ROA for AS1880, maxLength 22. |
| ROA: none | 192.108.211.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.213.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.214.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
| ROA: none | 192.108.197.0/24 | No ROA covers it. Add a ROA for AS1880, maxLength 24. |
Route objects not announced
Route objects with origin AS1880 whose prefix no peer sees AS1880 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.36.150.0/24 | RIPE | No ROA |
| 192.108.200.0/24 | RIPE | No ROA |
| 192.108.201.0/24 | RIPE | No ROA |
| 192.108.206.0/24 | RIPE | No ROA |
| 192.108.207.0/24 | RIPE | No ROA |
| 192.108.212.0/24 | RIPE | No ROA |
| 2001:440:1878::/48 | NTTCOM | 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.