22IPv4 routes
100.0% RPKI valid · 81.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
4 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
11Route objects not announced
registered with origin AS55034, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS55034, 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.
| 204.141.176.0/24 | Valid | Nonecovered by 204.141.176.0/22 | 673 100% |
| 204.141.177.0/24 | Valid | Nonecovered by 204.141.176.0/22 | 673 100% |
| 204.141.178.0/24 | Valid | Nonecovered by 204.141.176.0/22 | 673 100% |
| 204.141.179.0/24 | Valid | Nonecovered by 204.141.176.0/22 | 673 100% |
| 192.243.40.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.243.42.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.243.43.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.243.45.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.243.46.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.243.47.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 204.141.172.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 204.141.173.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.243.41.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.243.44.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 63.217.235.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 205.252.124.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 205.252.125.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 205.252.126.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 205.252.127.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 209.8.50.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 209.8.51.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 63.217.234.0/24 | Valid | RIR databaseAPNIC | 670 100% |
AS-SET
AS55034'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 25 are in fix.csv.
- Route object: none4
- Route object: RIR10
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 204.141.176.0/24 | No route object for it. A route object for 204.141.176.0/22 with origin AS55034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55034 in the RIR database for the space. |
| Route object: none | 204.141.177.0/24 | No route object for it. A route object for 204.141.176.0/22 with origin AS55034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55034 in the RIR database for the space. |
| Route object: none | 204.141.178.0/24 | No route object for it. A route object for 204.141.176.0/22 with origin AS55034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55034 in the RIR database for the space. |
| Route object: none | 204.141.179.0/24 | No route object for it. A route object for 204.141.176.0/22 with origin AS55034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55034 in the RIR database for the space. |
| Route object: RIR | 192.243.40.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.243.42.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.243.43.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.243.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.243.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.243.47.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.141.172.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.141.173.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.243.41.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.243.44.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55034 whose prefix no peer sees AS55034 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.251.49.0/24 | RADB | No ROA |
| 63.251.251.0/24 | RADB | No ROA |
| 66.171.200.0/24 | RADB | No ROA |
| 69.25.100.0/24 | RADB | No ROA |
| 70.42.236.0/24 | RADB | No ROA |
| 192.243.40.0/21 | RADB | Valid |
| 204.141.172.0/23 | NTTCOM | Valid |
| 204.141.176.0/22 | NTTCOM, RADB | Valid |
| 205.252.124.0/22 | APNIC | Valid |
| 205.252.124.0/23 | APNIC | Valid |
| 205.252.126.0/23 | APNIC | 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.