Announced routes
Every prefix a peer of the route collectors sees with origin AS29310, 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.182.106.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 195.68.208.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 45.147.64.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.147.65.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.147.66.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.147.67.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.223.252.0/24 | Valid | Nonecovered by 193.223.252.0/23 | 42 6%low visibility |
| 193.223.253.0/24 | Valid | Nonecovered by 193.223.252.0/23 | 42 6%low visibility |
| 213.244.115.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.244.116.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.244.117.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.244.122.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS29310'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 15 are in fix.csv.
- ROA: none6
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.182.106.0/24 | No ROA covers it. Add a ROA for AS29310, maxLength 24. |
| ROA: none | 195.68.208.0/23 | No ROA covers it. Add a ROA for AS29310, maxLength 23. |
| ROA: none | 45.147.64.0/24 | No ROA covers it. Add a ROA for AS29310, maxLength 24. |
| ROA: none | 45.147.65.0/24 | No ROA covers it. Add a ROA for AS29310, maxLength 24. |
| ROA: none | 45.147.66.0/24 | No ROA covers it. Add a ROA for AS29310, maxLength 24. |
| ROA: none | 45.147.67.0/24 | No ROA covers it. Add a ROA for AS29310, maxLength 24. |
| Route object: none | 193.223.252.0/24 | No route object for it. A route object for 193.223.252.0/23 with origin AS29310 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29310 in the RIR database for the space. |
| Route object: none | 193.223.253.0/24 | No route object for it. A route object for 193.223.252.0/23 with origin AS29310 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29310 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29310 whose prefix no peer sees AS29310 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.223.252.0/23 | RIPE | Valid |
| 213.244.112.0/21 | RIPE | Invalid: origin |
| 213.244.114.0/23 | RIPE | Invalid: origin |
| 213.244.118.0/24 | RIPE | Invalid: origin |
| 213.244.119.0/24 | RIPE | Invalid: origin |
| 213.244.120.0/22 | RIPE | Invalid: origin |
| 213.244.120.0/24 | RIPE | Invalid: origin |
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.