27IPv4 routes
100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
44Route objects not announced
registered with origin AS10101, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS10101, 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.
| 202.152.64.0/19 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 103.42.208.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.42.209.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 202.152.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.66.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.69.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.72.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.73.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.77.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.79.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.81.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.82.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 668 99% |
| 202.152.83.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 668 99% |
| 202.152.86.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.92.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.93.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.95.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.152.80.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 202.152.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 2 0%low visibility |
| 202.152.87.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
AS-SET
AS10101'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 44 are in fix.csv.
- Route object: not announced44
Route objects not announced
Route objects with origin AS10101 whose prefix no peer sees AS10101 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.42.208.0/22 | APNIC | Valid |
| 103.42.208.0/23 | APNIC | Valid |
| 103.42.210.0/23 | APNIC | Valid |
| 103.42.210.0/24 | APNIC | Valid |
| 103.42.211.0/24 | APNIC | Valid |
| 202.152.64.0/20 | APNIC | Invalid: maxLength |
| 202.152.64.0/21 | APNIC | Invalid: maxLength |
| 202.152.64.0/22 | APNIC | Invalid: maxLength |
| 202.152.64.0/23 | APNIC | Invalid: maxLength |
| 202.152.66.0/23 | APNIC | Invalid: maxLength |
| 202.152.68.0/22 | APNIC | Invalid: maxLength |
| 202.152.68.0/23 | APNIC | Invalid: maxLength |
| 202.152.70.0/23 | APNIC | Invalid: maxLength |
| 202.152.72.0/21 | APNIC | Invalid: maxLength |
| 202.152.72.0/22 | APNIC | Invalid: maxLength |
| 202.152.72.0/23 | APNIC | Invalid: maxLength |
| 202.152.74.0/23 | APNIC | Invalid: maxLength |
| 202.152.74.0/24 | APNIC | Invalid: maxLength |
| 202.152.75.0/24 | APNIC | Invalid: maxLength |
| 202.152.76.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.152.76.0/23 | APNIC | Invalid: maxLength |
| 202.152.76.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.152.78.0/23 | APNIC | Invalid: maxLength |
| 202.152.80.0/20 | APNIC | Invalid: maxLength |
| 202.152.80.0/21 | APNIC | Invalid: maxLength |
| 202.152.80.0/22 | APNIC | Invalid: maxLength |
| 202.152.80.0/23 | APNIC | Invalid: maxLength |
| 202.152.82.0/23 | APNIC | Invalid: maxLength |
| 202.152.84.0/22 | APNIC | Invalid: maxLength |
| 202.152.84.0/23 | APNIC | Invalid: maxLength |
| 202.152.86.0/23 | APNIC | Invalid: maxLength |
| 202.152.88.0/21 | APNIC | Invalid: maxLength |
| 202.152.88.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.152.88.0/23 | APNIC | Invalid: maxLength |
| 202.152.88.0/24 | APNIC | Invalid: maxLength |
| 202.152.89.0/24 | APNIC | Invalid: maxLength |
| 202.152.90.0/23 | APNIC | Invalid: maxLength |
| 202.152.90.0/24 | APNIC | Invalid: maxLength |
| 202.152.91.0/24 | APNIC | Invalid: maxLength |
| 202.152.92.0/22 | APNIC | Invalid: maxLength |
| 202.152.92.0/23 | APNIC | Invalid: maxLength |
| 202.152.94.0/23 | APNIC | Invalid: maxLength |
| 202.152.94.0/24 | APNIC, NTTCOM, RADB | Valid |
| 2406:7800::/32 | APNIC | 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.