20IPv4 routes
15.0% RPKI valid · 100.0% with a route object
1IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
17No ROA
1 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
54Route objects not announced
registered with origin AS5091, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS5091, 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.
| 139.45.177.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 139.45.181.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 139.45.183.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 139.45.184.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 139.45.178.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 139.45.182.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 139.45.180.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 139.45.160.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.161.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.162.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.165.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.168.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.170.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.171.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.175.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 673 100% |
| 139.45.173.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 669 99% |
| 139.45.174.0/24 | No ROA | RIR databaseNTTCOM, RADB, RIPE | 2 0%low visibility |
| 2a0c:ecc0::/48 | Valid | Nonecovered by 2a0c:ecc0::/29 | 331 52% |
| 65.87.144.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 194.34.153.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 671 100% |
| 194.34.152.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 669 99% |
AS-SET
AS5091'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 80 are in fix.csv.
- ROA: none17
- Route object: none1
- Route object: RIR8
- Route object: not announced54
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 139.45.177.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: RIR | 139.45.177.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 139.45.181.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: RIR | 139.45.181.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 139.45.183.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: RIR | 139.45.183.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 139.45.184.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: RIR | 139.45.184.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 139.45.178.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: RIR | 139.45.178.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 139.45.182.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: RIR | 139.45.182.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 139.45.180.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: RIR | 139.45.180.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 139.45.160.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.161.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.162.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.165.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.168.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.170.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.171.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.175.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.173.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| ROA: none | 139.45.174.0/24 | No ROA covers it. Add a ROA for AS5091, maxLength 24. |
| Route object: none | 2a0c:ecc0::/48 | No route object for it. A route object for 2a0c:ecc0::/29 with origin AS5091 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5091 in the RIR database for the space. |
| Route object: RIR | 65.87.144.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS5091 whose prefix no peer sees AS5091 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.21.168.0/24 | ARIN, RADB | No ROA |
| 139.45.160.0/19 | RADB | No ROA |
| 139.45.160.0/20 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.160.0/21 | NTTCOM, RADB | No ROA |
| 139.45.160.0/22 | NTTCOM, RADB | No ROA |
| 139.45.160.0/23 | NTTCOM, RADB | No ROA |
| 139.45.162.0/23 | NTTCOM, RADB | No ROA |
| 139.45.163.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.164.0/22 | NTTCOM, RADB | No ROA |
| 139.45.164.0/23 | NTTCOM, RADB | No ROA |
| 139.45.164.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.166.0/23 | NTTCOM, RADB | No ROA |
| 139.45.166.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.167.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.168.0/21 | NTTCOM, RADB | No ROA |
| 139.45.168.0/22 | NTTCOM, RADB | No ROA |
| 139.45.168.0/23 | NTTCOM, RADB | No ROA |
| 139.45.169.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.170.0/23 | NTTCOM, RADB | No ROA |
| 139.45.172.0/22 | NTTCOM, RADB | No ROA |
| 139.45.172.0/23 | NTTCOM, RADB | No ROA |
| 139.45.172.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.174.0/23 | NTTCOM, RADB | No ROA |
| 139.45.176.0/20 | NTTCOM, RADB, RIPE | No ROA |
| 139.45.176.0/21 | NTTCOM, RADB | No ROA |
| 139.45.176.0/22 | NTTCOM, RADB | No ROA |
| 139.45.176.0/23 | NTTCOM, RADB | No ROA |
| 139.45.176.0/24 | NTTCOM, RADB | No ROA |
| 139.45.178.0/23 | NTTCOM, RADB | No ROA |
| 139.45.179.0/24 | NTTCOM, RADB | No ROA |
| 139.45.180.0/22 | NTTCOM, RADB | No ROA |
| 139.45.180.0/23 | NTTCOM, RADB | No ROA |
| 139.45.182.0/23 | NTTCOM, RADB | No ROA |
| 139.45.184.0/21 | NTTCOM, RADB | No ROA |
| 139.45.184.0/22 | NTTCOM, RADB | No ROA |
| 139.45.184.0/23 | NTTCOM, RADB | No ROA |
| 139.45.185.0/24 | NTTCOM, RADB | No ROA |
| 139.45.186.0/23 | NTTCOM, RADB | No ROA |
| 139.45.186.0/24 | NTTCOM, RADB | No ROA |
| 139.45.187.0/24 | NTTCOM, RADB | No ROA |
| 139.45.188.0/22 | NTTCOM, RADB | No ROA |
| 139.45.188.0/23 | NTTCOM, RADB | No ROA |
| 139.45.188.0/24 | NTTCOM, RADB | No ROA |
| 139.45.189.0/24 | NTTCOM, RADB | No ROA |
| 139.45.190.0/23 | NTTCOM, RADB | No ROA |
| 139.45.190.0/24 | NTTCOM, RADB | No ROA |
| 139.45.191.0/24 | NTTCOM, RADB | No ROA |
| 194.34.152.0/22 | NTTCOM, RADB | No ROA |
| 194.34.152.0/23 | NTTCOM, RADB | No ROA |
| 194.34.154.0/23 | NTTCOM, RADB | No ROA |
| 194.34.154.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 194.34.155.0/24 | NTTCOM, RADB, RIPE | No ROA |
| 2620:cc:4000::/48 | ARIN, RADB | No ROA |
| 2a0c:ecc0::/29 | RADB, RIPE | 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.