Network · data from 2026-11-12
AS262914 AS262914 - Comision Federal de Electricidad
Registry name: AS262914 - Comision Federal de Electricidad, MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262914, 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.
| 159.16.212.0/23 | Valid | Nonecovered by 159.16.128.0/17 | 672 100% |
| 159.16.214.0/23 | Valid | Nonecovered by 159.16.128.0/17 | 672 100% |
| 159.16.241.0/24 | Valid | Nonecovered by 159.16.128.0/17 | 672 100% |
| 159.16.197.0/24 | Valid | Nonecovered by 159.16.128.0/17 | 2 0%low visibility |
| 159.16.198.0/24 | Valid | Nonecovered by 159.16.128.0/17 | 2 0%low visibility |
| 159.16.242.0/24 | Valid | Nonecovered by 159.16.128.0/17 | 2 0%low visibility |
| 159.16.250.0/24 | Valid | Nonecovered by 159.16.128.0/17 | 2 0%low visibility |
| 159.16.0.0/16 | Valid | RIR databaseLACNIC | 672 100% |
AS-SET
AS262914 isn't in PeeringDB, where networks name their 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 22 are in fix.csv.
- Route object: none7
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 159.16.212.0/23 | No route object for it. A route object for 159.16.128.0/17 with origin AS262914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262914 in the RIR database for the space. |
| Route object: none | 159.16.214.0/23 | No route object for it. A route object for 159.16.128.0/17 with origin AS262914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262914 in the RIR database for the space. |
| Route object: none | 159.16.241.0/24 | No route object for it. A route object for 159.16.128.0/17 with origin AS262914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262914 in the RIR database for the space. |
| Route object: none | 159.16.197.0/24 | No route object for it. A route object for 159.16.128.0/17 with origin AS262914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262914 in the RIR database for the space. |
| Route object: none | 159.16.198.0/24 | No route object for it. A route object for 159.16.128.0/17 with origin AS262914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262914 in the RIR database for the space. |
| Route object: none | 159.16.242.0/24 | No route object for it. A route object for 159.16.128.0/17 with origin AS262914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262914 in the RIR database for the space. |
| Route object: none | 159.16.250.0/24 | No route object for it. A route object for 159.16.128.0/17 with origin AS262914 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262914 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262914 whose prefix no peer sees AS262914 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 159.16.5.0/24 | LACNIC | Valid |
| 159.16.6.0/24 | LACNIC | Valid |
| 159.16.7.0/24 | LACNIC | Valid |
| 159.16.8.0/24 | LACNIC | Valid |
| 159.16.9.0/24 | LACNIC | Valid |
| 159.16.10.0/24 | LACNIC | Valid |
| 159.16.11.0/24 | LACNIC | Valid |
| 159.16.12.0/24 | LACNIC | Valid |
| 159.16.13.0/24 | LACNIC | Valid |
| 159.16.14.0/24 | LACNIC | Valid |
| 159.16.15.0/24 | LACNIC | Valid |
| 159.16.16.0/20 | LACNIC | Valid |
| 159.16.32.0/19 | LACNIC | Valid |
| 159.16.64.0/18 | LACNIC | Valid |
| 159.16.128.0/17 | 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.