Network · data from 2026-11-12
AS13682 AS13682 - TELECOMUNICACIONES DE GUATEMALA, SOCIEDAD ANONIMA
Registry name: AS13682 - TELECOMUNICACIONES DE GUATEMALA, SOCIEDAD ANONIMA, GT · not in PeeringDB
29IPv4 routes
93.1% RPKI valid · 17.2% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
1No ROA
24 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS13682, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS13682, 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.143.192.0/19 | Invalid: origin | Other origin only | 107 16% |
| 200.119.144.0/20 | No ROA | None | 672 100% |
| 190.143.201.0/24 | Valid | Nonecovered by 190.143.192.0/20 | 672 100% |
| 190.143.128.0/21 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.136.0/23 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.138.0/24 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.139.0/24 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.140.0/22 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.144.0/21 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.152.0/22 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.156.0/23 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.160.0/20 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.176.0/22 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.184.0/22 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.188.0/22 | Valid | Nonecovered by 190.143.128.0/18 | 671 100% |
| 190.143.200.0/24 | Valid | Nonecovered by 190.143.192.0/20 | 671 100% |
| 190.143.210.0/24 | Valid | Nonecovered by 190.143.210.0/23 | 671 100% |
| 190.143.211.0/24 | Valid | Nonecovered by 190.143.210.0/23 | 671 100% |
| 190.143.213.0/24 | Valid | Nonecovered by 190.143.212.0/22 | 671 100% |
| 190.143.216.0/22 | Valid | Nonecovered by 190.143.216.0/21 | 671 100% |
| 190.143.217.0/24 | Valid | Nonecovered by 190.143.216.0/21 | 671 100% |
| 190.143.220.0/22 | Valid | Nonecovered by 190.143.216.0/21 | 671 100% |
| 190.143.128.0/19 | Valid | Nonecovered by 190.143.128.0/18 | 117 17% |
| 190.143.160.0/19 | Valid | Nonecovered by 190.143.128.0/18 | 117 17% |
| 200.119.128.0/20 | Valid | RIR databaseLACNIC | 672 100% |
| 200.119.160.0/20 | Valid | RIR databaseLACNIC | 672 100% |
| 190.143.192.0/20 | Valid | RIR databaseLACNIC | 671 100% |
| 190.143.209.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 190.143.212.0/22 | Valid | RIR databaseLACNIC | 671 100% |
AS-SET
AS13682 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 32 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none24
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 190.143.192.0/19 | ROAs covering it name AS14754, AS262172, not AS13682. If AS13682 should announce it, add a ROA for AS13682. |
| Route object: none | 190.143.192.0/19 | Route objects for it name AS14754, AS262172. Add a route object with origin AS13682 in the RIR database for the space. |
| ROA: none | 200.119.144.0/20 | No ROA covers it. Add a ROA for AS13682, maxLength 20. |
| Route object: none | 200.119.144.0/20 | No route object for it. Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.201.0/24 | No route object for it. A route object for 190.143.192.0/20 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.128.0/21 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.136.0/23 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.138.0/24 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.139.0/24 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.140.0/22 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.144.0/21 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.152.0/22 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.156.0/23 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.160.0/20 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.176.0/22 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.184.0/22 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.188.0/22 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.200.0/24 | No route object for it. A route object for 190.143.192.0/20 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.210.0/24 | No route object for it. A route object for 190.143.210.0/23 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.211.0/24 | No route object for it. A route object for 190.143.210.0/23 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.213.0/24 | No route object for it. A route object for 190.143.212.0/22 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.216.0/22 | No route object for it. A route object for 190.143.216.0/21 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.217.0/24 | No route object for it. A route object for 190.143.216.0/21 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.220.0/22 | No route object for it. A route object for 190.143.216.0/21 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.128.0/19 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
| Route object: none | 190.143.160.0/19 | No route object for it. A route object for 190.143.128.0/18 with origin AS13682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13682 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13682 whose prefix no peer sees AS13682 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.143.128.0/18 | LACNIC | Valid |
| 190.143.210.0/23 | LACNIC | Valid |
| 190.143.216.0/21 | LACNIC | Valid |
| 200.119.128.0/24 | RADB | Valid |
| 200.119.156.0/22 | LACNIC | Valid |
| 200.119.176.0/21 | 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.