Network · data from 2026-11-12
AS38759 Transmedia Indonesia
Registry name: AIX-NAP-AS2-ID - TRANSMEDIA INDONESIA, PT, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38759, 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.
| 2001:d68:11::/48 | Valid | Nonecovered by 2001:d68::/32 | 635 100% |
| 202.180.8.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 202.180.9.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.180.10.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.180.11.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 2001:d68:7::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2001:d68:8::/48 | Valid | Other IRR onlyNTTCOM, RADB | 635 100% |
| 2001:d68:9::/48 | Valid | Other IRR onlyNTTCOM, RADB | 635 100% |
| 2001:d68:10::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 202.180.7.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
AS-SET
AS38759's PeeringDB record names no 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 48 are in fix.csv.
- Route object: none1
- Route object: RIR9
- Route object: not announced38
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2001:d68:11::/48 | No route object for it. A route object for 2001:d68::/32 with origin AS38759 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38759 in the RIR database for the space. |
| Route object: RIR | 202.180.8.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.9.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.10.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.11.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2001:d68:7::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:d68:8::/48 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:d68:9::/48 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:d68:10::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.7.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38759 whose prefix no peer sees AS38759 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 182.23.160.0/20 | NTTCOM | No ROA |
| 182.23.160.0/21 | NTTCOM | No ROA |
| 182.23.160.0/22 | NTTCOM | No ROA |
| 182.23.160.0/23 | NTTCOM | No ROA |
| 182.23.162.0/23 | NTTCOM | No ROA |
| 182.23.162.0/24 | NTTCOM | No ROA |
| 182.23.164.0/22 | NTTCOM | No ROA |
| 182.23.164.0/23 | NTTCOM | No ROA |
| 182.23.166.0/23 | NTTCOM | No ROA |
| 182.23.168.0/21 | NTTCOM | No ROA |
| 182.23.168.0/22 | NTTCOM | No ROA |
| 182.23.168.0/23 | NTTCOM | No ROA |
| 182.23.170.0/23 | NTTCOM | No ROA |
| 182.23.172.0/22 | NTTCOM | No ROA |
| 182.23.172.0/23 | NTTCOM | No ROA |
| 182.23.174.0/23 | NTTCOM | No ROA |
| 202.180.0.0/19 | NTTCOM | No ROA |
| 202.180.0.0/20 | NTTCOM | No ROA |
| 202.180.0.0/21 | NTTCOM, RADB | No ROA |
| 202.180.0.0/22 | NTTCOM, RADB | No ROA |
| 202.180.0.0/23 | NTTCOM, RADB | No ROA |
| 202.180.2.0/23 | NTTCOM, RADB | No ROA |
| 202.180.2.0/24 | NTTCOM | No ROA |
| 202.180.3.0/24 | NTTCOM | No ROA |
| 202.180.4.0/22 | NTTCOM, RADB | No ROA |
| 202.180.4.0/23 | NTTCOM, RADB | No ROA |
| 202.180.4.0/24 | NTTCOM | No ROA |
| 202.180.5.0/24 | NTTCOM | No ROA |
| 202.180.6.0/23 | NTTCOM, RADB | No ROA |
| 202.180.6.0/24 | NTTCOM | No ROA |
| 202.180.8.0/21 | NTTCOM, RADB | No ROA |
| 202.180.8.0/22 | NTTCOM, RADB | No ROA |
| 202.180.8.0/23 | NTTCOM, RADB | No ROA |
| 202.180.10.0/23 | NTTCOM, RADB | No ROA |
| 202.180.12.0/24 | NTTCOM | Valid |
| 202.180.13.0/24 | NTTCOM | Valid |
| 2001:d68::/32 | NTTCOM | Valid |
| 2001:dc6::/32 | NTTCOM | 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.