17IPv4 routes
100.0% RPKI valid · 100.0% with a route object
7IPv6 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 AS51264, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS51264, 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.
| 91.202.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.202.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.228.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.164.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.164.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.164.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.200.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.200.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.200.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 159.200.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.117.68.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.108.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.143.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.14.123.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.93.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.0.206.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2001:678:cfc::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a10:eb80:a::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:eb80:c::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:eb80:d::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:eb80:e::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:eb80:f::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:eb80:b::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS51264'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 AS51264 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.