Network · data from 2026-11-12
AS262206 Tigo - Millicom
Registry name: AS262206 - COMCEL GUATEMALA S.A., GT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262206, 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.30.173.0/24 | No ROA | None | 213 32% |
| 181.189.155.0/24 | Valid | None | 673 100% |
| 181.189.156.0/24 | Valid | None | 673 100% |
| 181.189.158.0/24 | Valid | None | 673 100% |
| 181.189.153.0/24 | Valid | None | 672 100% |
| 200.94.248.0/24 | Valid | None | 672 100% |
| 186.189.217.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.106.192.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 200.30.158.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 2803:16a0:2::/48 | Valid | RIR databaseLACNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS262206: AS262206:AS-GLOBAL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262206 isn't in the set, or no route object for AS262206 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS262206 in it | Not covered |
|---|---|---|---|---|---|
| AS262206:AS-GLOBAL | RADB | 321 | 8 | Yes | 6 |
| NTTCOM (also) | 167 | 7 | Yes | 6 |
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 19 are in fix.csv.
- ROA: none1
- Route object: none6
- Route object: RIR2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.30.173.0/24 | No ROA covers it. Add a ROA for AS262206, maxLength 24. |
| Route object: none | 200.30.173.0/24 | No route object for it. Add a route object with origin AS262206 in the RIR database for the space. |
| Route object: none | 181.189.155.0/24 | No route object for it. Add a route object with origin AS262206 in the RIR database for the space. |
| Route object: none | 181.189.156.0/24 | No route object for it. Add a route object with origin AS262206 in the RIR database for the space. |
| Route object: none | 181.189.158.0/24 | No route object for it. Add a route object with origin AS262206 in the RIR database for the space. |
| Route object: none | 181.189.153.0/24 | No route object for it. Add a route object with origin AS262206 in the RIR database for the space. |
| Route object: none | 200.94.248.0/24 | No route object for it. Add a route object with origin AS262206 in the RIR database for the space. |
| Route object: RIR | 186.189.217.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.106.192.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262206 whose prefix no peer sees AS262206 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.108.36.0/22 | LACNIC | Valid |
| 181.174.64.0/18 | RADB | No ROA |
| 186.4.0.0/18 | LACNIC | Valid |
| 186.32.0.0/18 | LACNIC | Valid |
| 186.32.160.0/19 | LACNIC | Valid |
| 186.32.192.0/19 | LACNIC | Valid |
| 186.176.0.0/16 | LACNIC | Valid |
| 186.177.0.0/17 | LACNIC | Valid |
| 186.177.128.0/18 | LACNIC | Valid |
| 2800:860::/32 | 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.