19IPv4 routes
100.0% RPKI valid · 100.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS39603, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS39603, 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.
| 5.173.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 5.173.128.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 5.173.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 46.112.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 46.113.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 89.108.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 89.108.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.108.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.254.128.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 94.254.128.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 94.254.144.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 94.254.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 94.254.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 94.254.224.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 109.243.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 109.243.128.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 109.243.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 164.126.0.0/15 | Valid | RIR databaseRIPE | 673 100% |
| 31.174.0.0/15 | Valid | RIR databaseRIPE | 671 100% |
| 2a00:1981::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS39603's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS39603 is announced.
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.