Announced routes
Every prefix a peer of the route collectors sees with origin AS27678, 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.
| 200.1.120.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.1.122.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 200.7.6.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.7.7.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 190.124.24.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 190.124.25.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2001:1398:5::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 200.16.113.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 200.27.115.0/24 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 668 99% |
| 2001:1398:1::/48 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 634 100% |
| 2001:1398:2::/48 | Valid | RIR databaseLACNIC | 634 100% |
| 2001:1398:3::/48 | Valid | RIR databaseLACNIC, NTTCOM, RADB | 634 100% |
AS-SET
AS27678'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 28 are in fix.csv.
- Route object: RIR7
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 200.1.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.1.122.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.7.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.124.24.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.124.25.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:1398:5::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27678 whose prefix no peer sees AS27678 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.124.24.0/23 | LACNIC, RADB | Valid |
| 190.124.26.0/24 | LACNIC, RADB | Valid |
| 199.7.82.0/23 | RADB | No ROA |
| 199.7.83.0/24 | RADB | No ROA |
| 200.1.120.0/22 | LACNIC, NTTCOM, RADB | Valid |
| 200.1.121.0/24 | RADB | Valid |
| 200.1.122.0/24 | RADB | Valid |
| 200.1.123.0/24 | RADB | Valid |
| 200.1.131.0/24 | RADB | No ROA |
| 200.7.6.0/23 | LACNIC, RADB | Valid |
| 200.16.114.0/23 | LACNIC, RADB | Valid |
| 200.16.114.0/24 | RADB | Valid |
| 200.16.115.0/24 | RADB | Valid |
| 2001:500:3::/48 | RADB | No ROA |
| 2001:500:9e::/47 | RADB | No ROA |
| 2001:500:9f::/48 | RADB | No ROA |
| 2001:1398::/32 | NTTCOM | No ROA |
| 2001:1398:4::/47 | LACNIC | Valid |
| 2001:1398:4::/48 | NTTCOM, RADB | Valid |
| 2001:1398:14::/48 | LACNIC | Valid |
| 2001:1398:16::/48 | LACNIC, NTTCOM, RADB | 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.