89IPv4 routes
93.3% RPKI valid · 95.5% with a route object
23IPv6 routes
100.0% RPKI valid · 91.3% with a route object
4RPKI invalid
4 origin · 0 maxLength
2No ROA
6 with no route object for this origin
4Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS62005, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS62005, 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.
| 85.239.53.0/24 | Invalid: origin | None | 37 5%low visibility |
| 85.239.55.0/24 | Invalid: origin | None | 23 3%low visibility |
| 85.239.52.0/24 | Invalid: origin | None | 10 1%low visibility |
| 85.239.54.0/24 | Invalid: origin | None | 10 1%low visibility |
| 91.227.77.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.28.119.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 2a10:1fc0:15::/48 | Valid | None | 603 95% |
| 2a10:1fc0:16::/48 | Valid | None | 603 95% |
| 45.86.228.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 45.143.166.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 62.106.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.97.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.210.108.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.221.190.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 92.118.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 140.225.199.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.19.254.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 155.212.242.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 171.22.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 171.22.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.39.18.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.35.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.61.120.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.54.160.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.46.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.109.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.109.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.109.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2.59.216.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.59.217.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.59.218.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.145.171.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.150.109.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.21.222.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.21.229.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.22.236.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.23.219.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.24.226.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.25.224.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.26.216.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.26.222.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.27.212.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.27.236.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.29.216.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.29.227.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 91.211.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.242.228.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.118.124.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.118.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 130.49.155.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 132.243.169.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 132.243.170.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 132.243.171.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 155.212.243.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 176.124.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.119.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.200.16.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.200.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.61.121.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.20.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.86.229.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.86.231.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.129.0.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.150.108.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 62.204.35.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.236.230.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 136.0.20.0/24 | Valid | RIR databaseARIN | 671 100% |
| 146.19.49.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 171.22.181.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.66.248.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.66.249.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 92.118.126.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.42.221.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 45.83.180.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 91.235.234.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 91.242.241.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 93.89.211.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 132.243.64.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 132.243.168.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 146.19.143.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 146.19.185.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 176.124.32.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 185.123.53.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 193.104.75.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 193.109.120.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 194.26.141.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 45.83.182.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 45.129.199.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 193.43.104.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 194.59.183.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 77.72.85.0/24 | Valid | RIR databaseRIPE | 665 99% |
| 2a10:1fc0:1::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:1fc0:3::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:1fc0:4::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:1fc0:5::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:1fc0:d::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a12:c740::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:1fc0:8::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:1fc0:b::/48 | Valid | RIR databaseRADB, RIPE | 633 100% |
| 2a10:1fc0:c::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:1fc0:e::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:1fc0:f::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:1fc0:10::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:1fc0:12::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a12:c740:1::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:1fc0:9::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:1fc0:11::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:1fc0:13::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:1fc0:14::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a12:c740:2::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:1fc0:2::/48 | Valid | RIR databaseRIPE | 629 99% |
| 2a10:1fc0:6::/48 | Valid | RIR databaseRIPE | 629 99% |
AS-SET
AS62005'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 12 are in fix.csv.
- ROA: origin4
- ROA: none2
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 85.239.53.0/24 | ROAs covering it name AS9123, not AS62005. If AS62005 should announce it, add a ROA for AS62005. |
| Route object: none | 85.239.53.0/24 | No route object for it. Add a route object with origin AS62005 in the RIR database for the space. |
| ROA: origin | 85.239.55.0/24 | ROAs covering it name AS9123, not AS62005. If AS62005 should announce it, add a ROA for AS62005. |
| Route object: none | 85.239.55.0/24 | No route object for it. Add a route object with origin AS62005 in the RIR database for the space. |
| ROA: origin | 85.239.52.0/24 | ROAs covering it name AS9123, not AS62005. If AS62005 should announce it, add a ROA for AS62005. |
| Route object: none | 85.239.52.0/24 | No route object for it. Add a route object with origin AS62005 in the RIR database for the space. |
| ROA: origin | 85.239.54.0/24 | ROAs covering it name AS9123, not AS62005. If AS62005 should announce it, add a ROA for AS62005. |
| Route object: none | 85.239.54.0/24 | No route object for it. Add a route object with origin AS62005 in the RIR database for the space. |
| ROA: none | 91.227.77.0/24 | No ROA covers it. Add a ROA for AS62005, maxLength 24. |
| ROA: none | 185.28.119.0/24 | No ROA covers it. Add a ROA for AS62005, maxLength 24. |
| Route object: none | 2a10:1fc0:15::/48 | No route object for it. Add a route object with origin AS62005 in the RIR database for the space. |
| Route object: none | 2a10:1fc0:16::/48 | No route object for it. Add a route object with origin AS62005 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS62005 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.