Network · data from 2026-11-12
AS14920 EVERTEC - Evertec
Registry name: EVERTEC - Evertec, PR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14920, 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.
| 64.178.200.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.211.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.212.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.213.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.214.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.215.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.216.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.217.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.219.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.220.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.178.221.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS14920 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 28 are in fix.csv.
- ROA: none11
- Route object: RIR11
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.178.200.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.200.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.211.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.212.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.212.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.213.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.213.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.214.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.214.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.215.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.215.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.216.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.216.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.217.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.217.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.219.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.219.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.220.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.178.221.0/24 | No ROA covers it. Add a ROA for AS14920, maxLength 24. |
| Route object: RIR | 64.178.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14920 whose prefix no peer sees AS14920 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.178.192.0/19 | RADB | No ROA |
| 64.178.192.0/24 | RADB | No ROA |
| 64.178.194.0/24 | RADB | No ROA |
| 64.178.197.0/24 | RADB | No ROA |
| 64.178.198.0/24 | RADB | No ROA |
| 204.154.228.0/24 | RADB | No ROA |
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.