Network · data from 2026-11-12
AS28051 Villa Flandria
Registry name: AS28051 - Coop. Telefonica y de obras y serv. publicos de Villa Flandria, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28051, 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.0.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.1.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.2.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.3.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.4.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.5.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.6.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.7.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.8.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.9.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.15.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 671 100% |
| 190.124.10.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 666 99% |
| 190.124.11.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 666 99% |
| 190.124.12.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 666 99% |
| 190.124.13.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 666 99% |
| 190.124.14.0/24 | Valid | Nonecovered by 190.124.0.0/20 | 666 99% |
| 190.124.0.0/20 | Valid | RIR databaseLACNIC | 671 100% |
AS-SET
AS28051'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 16 are in fix.csv.
- Route object: none16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.124.0.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.1.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.2.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.3.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.4.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.5.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.6.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.7.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.8.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.9.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.15.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.10.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.11.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.12.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.13.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
| Route object: none | 190.124.14.0/24 | No route object for it. A route object for 190.124.0.0/20 with origin AS28051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28051 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS28051 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.