Network · data from 2026-11-12
AS136975 Global Technology Myanmar
Registry name: GNET-AS-AP - Global Technology, MM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136975, 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.
| 154.18.220.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.18.221.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.18.222.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.101.16.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.101.17.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.101.18.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.101.19.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 2403:3240::/32 | Valid | RIR databaseAPNIC, RADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS136975: AS-136975-TRANSIT. 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 (AS136975 isn't in the set, or no route object for AS136975 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 | AS136975 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-136975-TRANSIT | In no IRR database read today. | |||||
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 18 are in fix.csv.
- ROA: none3
- Route object: RIR3
- AS-SET: not found1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.18.220.0/24 | No ROA covers it. Add a ROA for AS136975, maxLength 24. |
| Route object: RIR | 154.18.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.18.221.0/24 | No ROA covers it. Add a ROA for AS136975, maxLength 24. |
| Route object: RIR | 154.18.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.18.222.0/24 | No ROA covers it. Add a ROA for AS136975, maxLength 24. |
| Route object: RIR | 154.18.222.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-136975-TRANSIT | PeeringDB names AS-136975-TRANSIT; no IRR database read has it. |
Route objects not announced
Route objects with origin AS136975 whose prefix no peer sees AS136975 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.47.40.0/21 | RADB | No ROA |
| 38.47.40.0/24 | RADB | No ROA |
| 38.47.41.0/24 | RADB | No ROA |
| 38.47.42.0/24 | RADB | No ROA |
| 38.47.43.0/24 | RADB | No ROA |
| 38.47.44.0/24 | RADB | No ROA |
| 38.47.45.0/24 | RADB | No ROA |
| 38.47.46.0/24 | RADB | No ROA |
| 38.47.47.0/24 | RADB | No ROA |
| 103.101.16.0/22 | APNIC, NTTCOM, RADB | Valid |
| 154.18.223.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.