Announced routes
Every prefix a peer of the route collectors sees with origin AS265776, 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.
| 190.124.56.0/24 | Valid | Nonecovered by 190.124.56.0/21 | 671 100% |
| 190.124.57.0/24 | Valid | Nonecovered by 190.124.56.0/21 | 671 100% |
| 190.124.58.0/24 | Valid | Nonecovered by 190.124.56.0/21 | 671 100% |
| 190.124.60.0/24 | Valid | Nonecovered by 190.124.56.0/21 | 671 100% |
| 190.124.61.0/24 | Valid | Nonecovered by 190.124.56.0/21 | 671 100% |
| 190.124.62.0/24 | Valid | Nonecovered by 190.124.56.0/21 | 671 100% |
| 190.124.63.0/24 | Valid | Nonecovered by 190.124.56.0/21 | 671 100% |
AS-SET
AS265776'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 8 are in fix.csv.
- Route object: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.124.56.0/24 | No route object for it. A route object for 190.124.56.0/21 with origin AS265776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265776 in the RIR database for the space. |
| Route object: none | 190.124.57.0/24 | No route object for it. A route object for 190.124.56.0/21 with origin AS265776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265776 in the RIR database for the space. |
| Route object: none | 190.124.58.0/24 | No route object for it. A route object for 190.124.56.0/21 with origin AS265776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265776 in the RIR database for the space. |
| Route object: none | 190.124.60.0/24 | No route object for it. A route object for 190.124.56.0/21 with origin AS265776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265776 in the RIR database for the space. |
| Route object: none | 190.124.61.0/24 | No route object for it. A route object for 190.124.56.0/21 with origin AS265776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265776 in the RIR database for the space. |
| Route object: none | 190.124.62.0/24 | No route object for it. A route object for 190.124.56.0/21 with origin AS265776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265776 in the RIR database for the space. |
| Route object: none | 190.124.63.0/24 | No route object for it. A route object for 190.124.56.0/21 with origin AS265776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265776 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265776 whose prefix no peer sees AS265776 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.124.56.0/21 | LACNIC | 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.