Announced routes
Every prefix a peer of the route collectors sees with origin AS16190, 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.
| 2a00:1500::/29 | No ROA | RIR databaseRIPE | 0 0%low visibility |
| 217.113.0.0/23 | Valid | Nonecovered by 217.113.0.0/22 | 671 100% |
| 217.113.2.0/23 | Valid | Nonecovered by 217.113.0.0/22 | 671 100% |
| 217.113.4.0/23 | Valid | Nonecovered by 217.113.4.0/22 | 671 100% |
| 217.113.6.0/23 | Valid | Nonecovered by 217.113.4.0/22 | 671 100% |
| 217.113.0.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 217.113.0.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 217.113.4.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 217.113.0.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 217.113.1.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 217.113.2.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 217.113.3.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 217.113.4.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 217.113.6.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 217.113.7.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 217.113.5.0/24 | Valid | RIR databaseRIPE | 0 0%low visibility |
AS-SET
AS16190'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 10 are in fix.csv.
- ROA: none1
- Route object: none4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a00:1500::/29 | No ROA covers it. Add a ROA for AS16190, maxLength 29. |
| Route object: none | 217.113.0.0/23 | No route object for it. A route object for 217.113.0.0/22 with origin AS16190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16190 in the RIR database for the space. |
| Route object: none | 217.113.2.0/23 | No route object for it. A route object for 217.113.0.0/22 with origin AS16190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16190 in the RIR database for the space. |
| Route object: none | 217.113.4.0/23 | No route object for it. A route object for 217.113.4.0/22 with origin AS16190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16190 in the RIR database for the space. |
| Route object: none | 217.113.6.0/23 | No route object for it. A route object for 217.113.4.0/22 with origin AS16190 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16190 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16190 whose prefix no peer sees AS16190 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.249.199.0/24 | RIPE | Invalid: origin |
| 89.249.203.0/24 | RIPE | Invalid: origin |
| 89.249.205.0/24 | RIPE | Invalid: origin |
| 89.249.206.0/24 | RIPE | Invalid: origin |
| 2a00:1500::/32 | RIPE | No ROA |
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.