Network · data from 2026-11-12
AS27902 AS27902 - GPF CORPORACION - POWERFAST
Registry name: AS27902 - GPF CORPORACION - POWERFAST, EC · not in PeeringDB
21IPv4 routes
100.0% RPKI valid · 4.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
20 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS27902, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS27902, 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.107.64.0/24 | Valid | Nonecovered by 190.107.64.0/22 | 666 99% |
| 190.107.65.0/24 | Valid | Nonecovered by 190.107.64.0/22 | 666 99% |
| 190.107.66.0/24 | Valid | Nonecovered by 190.107.64.0/22 | 666 99% |
| 190.107.67.0/24 | Valid | Nonecovered by 190.107.64.0/22 | 666 99% |
| 190.107.72.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 190.107.73.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 190.107.74.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 190.107.75.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 190.107.76.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 190.107.77.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 190.107.78.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 190.107.79.0/24 | Valid | Nonecovered by 190.107.72.0/21 | 666 99% |
| 200.93.248.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 200.93.249.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 200.93.250.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 200.93.251.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 200.93.252.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 200.93.253.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 200.93.254.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 200.93.255.0/24 | Valid | Nonecovered by 200.93.248.0/21 | 666 99% |
| 190.107.71.0/24 | Valid | Other IRR onlyRADB | 666 99% |
AS-SET
AS27902 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 26 are in fix.csv.
- Route object: none20
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.107.64.0/24 | No route object for it. A route object for 190.107.64.0/22 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.65.0/24 | No route object for it. A route object for 190.107.64.0/22 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.66.0/24 | No route object for it. A route object for 190.107.64.0/22 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.67.0/24 | No route object for it. A route object for 190.107.64.0/22 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.72.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.73.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.74.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.75.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.76.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.77.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.78.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 190.107.79.0/24 | No route object for it. A route object for 190.107.72.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.248.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.249.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.250.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.251.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.252.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.253.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.254.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: none | 200.93.255.0/24 | No route object for it. A route object for 200.93.248.0/21 with origin AS27902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27902 in the RIR database for the space. |
| Route object: RIR | 190.107.71.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27902 whose prefix no peer sees AS27902 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.107.64.0/20 | LACNIC, RADB | Valid |
| 190.107.64.0/22 | LACNIC | Valid |
| 190.107.70.0/23 | LACNIC | Valid |
| 190.107.72.0/21 | LACNIC | Valid |
| 200.93.248.0/21 | LACNIC, RADB | 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.