Announced routes
Every prefix a peer of the route collectors sees with origin AS49463, 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.
| 185.7.161.0/24 | Valid | Nonecovered by 185.7.160.0/22 | 671 100% |
| 185.7.162.0/23 | Valid | Nonecovered by 185.7.160.0/22 | 671 100% |
| 46.21.112.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.179.120.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 31.216.16.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 46.21.112.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 213.215.28.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.21.114.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.21.115.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.21.116.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a02:27d0::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a02:27d0:100::/48 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
AS49463'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 30 are in fix.csv.
- Route object: none2
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.7.161.0/24 | No route object for it. A route object for 185.7.160.0/22 with origin AS49463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49463 in the RIR database for the space. |
| Route object: none | 185.7.162.0/23 | No route object for it. A route object for 185.7.160.0/22 with origin AS49463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49463 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49463 whose prefix no peer sees AS49463 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.216.16.0/24 | RIPE | Valid |
| 31.216.17.0/24 | RIPE | Valid |
| 31.216.18.0/24 | RIPE | Valid |
| 31.216.19.0/24 | RIPE | Valid |
| 31.216.20.0/24 | RIPE | Valid |
| 31.216.21.0/24 | RIPE | Valid |
| 31.216.22.0/24 | RIPE | Valid |
| 31.216.23.0/24 | RIPE | Valid |
| 31.216.24.0/22 | RIPE | Valid |
| 31.216.24.0/24 | RIPE | Valid |
| 31.216.25.0/24 | RIPE | Valid |
| 31.216.26.0/24 | RIPE | Valid |
| 31.216.27.0/24 | RIPE | Valid |
| 31.216.28.0/24 | RIPE | Valid |
| 31.216.29.0/24 | RIPE | Valid |
| 31.216.30.0/23 | RIPE | Valid |
| 31.216.30.0/24 | RIPE | Valid |
| 31.216.31.0/24 | RIPE | Valid |
| 46.21.112.0/21 | RIPE | Valid |
| 46.21.112.0/23 | RIPE | Valid |
| 46.21.113.0/24 | RIPE | Valid |
| 46.21.114.0/23 | RIPE | Valid |
| 46.21.120.0/21 | RIPE | Valid |
| 185.7.160.0/22 | RIPE | Valid |
| 2001:7a8:820::/44 | RIPE | Invalid: origin |
| 2a02:27d0::/48 | RIPE | Valid |
| 2a02:27d0:17::/48 | RIPE | Valid |
| 2a02:27d0:116::/48 | 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.