Network · data from 2026-11-12
AS52371 XF Comunicaciones
Registry name: AS52371 - XF Comunicaciones S.A., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52371, 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.
| 186.159.120.0/23 | Valid | Nonecovered by 186.159.120.0/22 | 670 100% |
| 186.159.121.0/24 | Valid | Nonecovered by 186.159.120.0/22 | 670 100% |
| 186.159.122.0/24 | Valid | Nonecovered by 186.159.120.0/22 | 670 100% |
| 186.159.123.0/24 | Valid | Nonecovered by 186.159.120.0/22 | 670 100% |
| 186.159.120.0/24 | Valid | Nonecovered by 186.159.120.0/22 | 8 1%low visibility |
| 186.159.124.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 186.159.125.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 186.159.126.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 201.252.229.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 190.226.33.0/24 | Valid | RIR databaseLACNIC | 663 99% |
| 190.226.32.0/24 | Valid | RIR databaseLACNIC | 661 98% |
| 186.159.120.0/22 | Valid | RIR databaseLACNIC | 104 15% |
AS-SET
PeeringDB's irr_as_set for AS52371: AS52371:AS-XFLY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS52371 isn't in the set, or no route object for AS52371 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS52371 in it | Not covered |
|---|---|---|---|---|---|
| AS52371:AS-XFLY | LACNIC | 1 | 1 | Yes | 0 |
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 5 are in fix.csv.
- Route object: none5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.159.120.0/23 | No route object for it. A route object for 186.159.120.0/22 with origin AS52371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52371 in the RIR database for the space. |
| Route object: none | 186.159.121.0/24 | No route object for it. A route object for 186.159.120.0/22 with origin AS52371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52371 in the RIR database for the space. |
| Route object: none | 186.159.122.0/24 | No route object for it. A route object for 186.159.120.0/22 with origin AS52371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52371 in the RIR database for the space. |
| Route object: none | 186.159.123.0/24 | No route object for it. A route object for 186.159.120.0/22 with origin AS52371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52371 in the RIR database for the space. |
| Route object: none | 186.159.120.0/24 | No route object for it. A route object for 186.159.120.0/22 with origin AS52371 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52371 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS52371 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.