73IPv4 routes
94.5% RPKI valid · 84.9% with a route object
3IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
4No ROA
11 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS42003, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS42003, 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.
| 94.187.14.0/24 | No ROA | Nonecovered by 94.187.8.0/21 | 673 100% |
| 94.187.15.0/24 | No ROA | Nonecovered by 94.187.8.0/21 | 673 100% |
| 94.187.8.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 178.135.0.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 94.187.8.0/24 | Valid | Nonecovered by 94.187.8.0/21 | 673 100% |
| 94.187.9.0/24 | Valid | Nonecovered by 94.187.8.0/21 | 673 100% |
| 94.187.10.0/24 | Valid | Nonecovered by 94.187.8.0/21 | 673 100% |
| 94.187.11.0/24 | Valid | Nonecovered by 94.187.8.0/21 | 673 100% |
| 94.187.95.0/24 | Valid | Nonecovered by 94.187.88.0/21 | 673 100% |
| 178.135.8.0/24 | Valid | Nonecovered by 178.135.8.0/21 | 673 100% |
| 178.135.9.0/24 | Valid | Nonecovered by 178.135.8.0/21 | 673 100% |
| 178.135.10.0/24 | Valid | Nonecovered by 178.135.8.0/21 | 673 100% |
| 178.135.95.0/24 | Valid | Nonecovered by 178.135.88.0/21 | 673 100% |
| 77.42.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 77.42.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 77.42.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 77.42.224.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 77.42.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 77.42.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.0.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.6.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.16.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.24.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.32.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.64.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.72.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.88.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.96.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.187.120.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.6.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.8.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.16.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.24.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.32.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.64.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.72.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.96.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.128.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.136.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.144.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.160.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.168.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.176.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.216.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.224.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.135.120.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 2a00:6920:d000::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a00:6920:e000::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a00:6920:f000::/40 | Valid | RIR databaseRIPE | 636 100% |
| 178.135.200.0/21 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS42003'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 22 are in fix.csv.
- ROA: none4
- Route object: none11
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.187.14.0/24 | No ROA covers it. Add a ROA for AS42003, maxLength 24. |
| Route object: none | 94.187.14.0/24 | No route object for it. A route object for 94.187.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| ROA: none | 94.187.15.0/24 | No ROA covers it. Add a ROA for AS42003, maxLength 24. |
| Route object: none | 94.187.15.0/24 | No route object for it. A route object for 94.187.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| ROA: none | 94.187.8.0/21 | No ROA covers it. Add a ROA for AS42003, maxLength 21. |
| ROA: none | 178.135.0.0/21 | No ROA covers it. Add a ROA for AS42003, maxLength 21. |
| Route object: none | 94.187.8.0/24 | No route object for it. A route object for 94.187.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 94.187.9.0/24 | No route object for it. A route object for 94.187.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 94.187.10.0/24 | No route object for it. A route object for 94.187.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 94.187.11.0/24 | No route object for it. A route object for 94.187.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 94.187.95.0/24 | No route object for it. A route object for 94.187.88.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 178.135.8.0/24 | No route object for it. A route object for 178.135.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 178.135.9.0/24 | No route object for it. A route object for 178.135.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 178.135.10.0/24 | No route object for it. A route object for 178.135.8.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
| Route object: none | 178.135.95.0/24 | No route object for it. A route object for 178.135.88.0/21 with origin AS42003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42003 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42003 whose prefix no peer sees AS42003 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.42.208.0/20 | RIPE | Invalid: maxLength |
| 77.42.251.0/24 | RIPE | Invalid: origin |
| 94.187.104.0/21 | RIPE | Valid |
| 94.187.112.0/21 | RIPE | Valid |
| 178.135.88.0/21 | RIPE | Valid |
| 178.135.112.0/21 | RIPE | Valid |
| 2a00:6920:e100::/40 | RIPE | 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.