Network · data from 2026-11-12
AS27912 AS27912 - UNIVERSIDAD TECNOLOGICA CENTROAMERICANA
Registry name: AS27912 - UNIVERSIDAD TECNOLOGICA CENTROAMERICANA, HN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27912, 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.
| 200.107.208.0/24 | No ROA | Other origin onlycovered by 200.107.208.0/23 | 672 100% |
| 200.107.213.0/24 | No ROA | Other origin onlycovered by 200.107.208.0/21 | 672 100% |
| 200.107.215.0/24 | No ROA | Other origin onlycovered by 200.107.208.0/21 | 672 100% |
| 200.107.209.0/24 | No ROA | Other origin onlycovered by 200.107.208.0/23 | 671 100% |
| 200.107.212.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 200.107.211.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 200.107.210.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
AS-SET
AS27912 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 16 are in fix.csv.
- ROA: none7
- Route object: none4
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.107.208.0/24 | No ROA covers it. Add a ROA for AS27912, maxLength 24. |
| Route object: none | 200.107.208.0/24 | Route objects for it name AS28513. A route object for 200.107.208.0/23 with origin AS27912 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27912 in the RIR database for the space. |
| ROA: none | 200.107.213.0/24 | No ROA covers it. Add a ROA for AS27912, maxLength 24. |
| Route object: none | 200.107.213.0/24 | Route objects for it name AS27932, AS28513. A route object for 200.107.208.0/21 with origin AS27912 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27912 in the RIR database for the space. |
| ROA: none | 200.107.215.0/24 | No ROA covers it. Add a ROA for AS27912, maxLength 24. |
| Route object: none | 200.107.215.0/24 | Route objects for it name AS27932, AS28513. A route object for 200.107.208.0/21 with origin AS27912 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27912 in the RIR database for the space. |
| ROA: none | 200.107.209.0/24 | No ROA covers it. Add a ROA for AS27912, maxLength 24. |
| Route object: none | 200.107.209.0/24 | Route objects for it name AS28513. A route object for 200.107.208.0/23 with origin AS27912 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27912 in the RIR database for the space. |
| ROA: none | 200.107.212.0/24 | No ROA covers it. Add a ROA for AS27912, maxLength 24. |
| Route object: RIR | 200.107.212.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.107.211.0/24 | No ROA covers it. Add a ROA for AS27912, maxLength 24. |
| Route object: RIR | 200.107.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.107.210.0/24 | No ROA covers it. Add a ROA for AS27912, maxLength 24. |
| Route object: RIR | 200.107.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27912 whose prefix no peer sees AS27912 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.107.208.0/21 | ALTDB, NTTCOM | No ROA |
| 200.107.208.0/23 | 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.