Network · data from 2026-11-12
AS9246 GTA/Teleguam Holdings, LLC
Registry name: GTA-AP - Teleguam Holdings, LLC, GU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9246, 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.
| 120.29.200.0/21 | Invalid: origin | RIR databaseAPNIC | 44 7%low visibility |
| 67.98.160.0/21 | No ROA | None | 673 100% |
| 209.164.184.0/21 | No ROA | None | 673 100% |
| 38.121.24.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 117.20.120.0/21 | Valid | None | 673 100% |
| 202.151.64.0/19 | Valid | None | 673 100% |
| 2405:7400::/32 | Valid | None | 636 100% |
| 114.142.192.0/18 | Valid | RIR databaseAPNIC | 673 100% |
| 43.240.88.0/22 | Valid | RIR databaseAPNIC | 671 100% |
| 103.7.100.0/22 | Valid | RIR databaseAPNIC | 671 100% |
| 202.151.76.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 202.151.85.0/24 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS9246: AS-TELEGUAM. 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 (AS9246 isn't in the set, or no route object for AS9246 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 | AS9246 in it | Not covered |
|---|---|---|---|---|---|
| AS-TELEGUAM | APNIC | 3 | 1 | Yes | 5 |
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 11 are in fix.csv.
- ROA: origin1
- ROA: none3
- Route object: none5
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 120.29.200.0/21 | ROAs covering it name AS6453, not AS9246. If AS9246 should announce it, add a ROA for AS9246. |
| ROA: none | 67.98.160.0/21 | No ROA covers it. Add a ROA for AS9246, maxLength 21. |
| Route object: none | 67.98.160.0/21 | No route object for it. Add a route object with origin AS9246 in the RIR database for the space. |
| ROA: none | 209.164.184.0/21 | No ROA covers it. Add a ROA for AS9246, maxLength 21. |
| Route object: none | 209.164.184.0/21 | No route object for it. Add a route object with origin AS9246 in the RIR database for the space. |
| ROA: none | 38.121.24.0/21 | No ROA covers it. Add a ROA for AS9246, maxLength 21. |
| Route object: RIR | 38.121.24.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 117.20.120.0/21 | No route object for it. Add a route object with origin AS9246 in the RIR database for the space. |
| Route object: none | 202.151.64.0/19 | No route object for it. Add a route object with origin AS9246 in the RIR database for the space. |
| Route object: none | 2405:7400::/32 | No route object for it. Add a route object with origin AS9246 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9246 whose prefix no peer sees AS9246 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 114.142.212.0/24 | APNIC | 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.