Network · data from 2026-11-12
AS38760 PT Media Sarana Akses
Registry name: IDNIC-MSA-AS-ID - PT Media Sarana Akses, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38760, 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.
| 103.217.211.0/24 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 673 100% |
| 103.217.208.0/24 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 672 100% |
| 103.217.209.0/24 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 672 100% |
| 103.217.210.0/24 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 672 100% |
AS-SET
AS38760'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 52 are in fix.csv.
- Route object: RIR4
- Route object: not announced48
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.217.211.0/24 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.217.208.0/24 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.217.209.0/24 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.217.210.0/24 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38760 whose prefix no peer sees AS38760 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.4.52.0/23 | ALTDB, RADB | Valid |
| 103.4.52.0/24 | ALTDB, RADB | Valid |
| 103.4.53.0/24 | ALTDB, RADB | Valid |
| 103.99.164.0/22 | ALTDB, RADB | Valid |
| 103.99.164.0/23 | RADB | Valid |
| 103.99.164.0/24 | ALTDB, RADB | Valid |
| 103.99.165.0/24 | ALTDB, RADB | Valid |
| 103.99.166.0/23 | RADB | Valid |
| 103.99.166.0/24 | ALTDB, RADB | Valid |
| 103.99.167.0/24 | ALTDB, RADB | Valid |
| 103.217.208.0/22 | ALTDB, NTTCOM, RADB | Valid |
| 103.217.208.0/23 | NTTCOM | Valid |
| 103.217.210.0/23 | NTTCOM | Valid |
| 2001:df2:a00::/48 | RADB | No ROA |
| 2400:9b60::/32 | ALTDB, RADB | Valid |
| 2400:9b60::/33 | RADB | Valid |
| 2400:9b60::/48 | ALTDB | Valid |
| 2400:9b60:1::/48 | ALTDB, RADB | Valid |
| 2400:9b60:2::/48 | ALTDB, RADB | Valid |
| 2400:9b60:3::/48 | ALTDB, RADB | Valid |
| 2400:9b60:4::/48 | ALTDB, RADB | Valid |
| 2400:9b60:5::/48 | ALTDB | Valid |
| 2400:9b60:6::/48 | ALTDB | Valid |
| 2400:9b60:7::/48 | ALTDB | Valid |
| 2400:9b60:8::/48 | ALTDB | Valid |
| 2400:9b60:9::/48 | ALTDB | Valid |
| 2400:9b60:a::/48 | ALTDB | Valid |
| 2400:9b60:b::/48 | ALTDB | Valid |
| 2400:9b60:c::/48 | ALTDB | Valid |
| 2400:9b60:d::/48 | ALTDB | Valid |
| 2400:9b60:e::/48 | ALTDB | Valid |
| 2400:9b60:f::/48 | ALTDB | Valid |
| 2400:9b60:10::/48 | ALTDB | Valid |
| 2400:9b60:11::/48 | ALTDB | Valid |
| 2400:9b60:12::/48 | ALTDB | Valid |
| 2400:9b60:13::/48 | ALTDB | Valid |
| 2400:9b60:14::/48 | ALTDB | Valid |
| 2400:9b60:15::/48 | ALTDB | Valid |
| 2400:9b60:16::/48 | ALTDB | Valid |
| 2400:9b60:17::/48 | ALTDB | Valid |
| 2400:9b60:18::/48 | ALTDB | Valid |
| 2400:9b60:19::/48 | ALTDB | Valid |
| 2400:9b60:1a::/48 | ALTDB | Valid |
| 2400:9b60:1b::/48 | ALTDB | Valid |
| 2400:9b60:1c::/48 | ALTDB | Valid |
| 2400:9b60:1d::/48 | ALTDB | Valid |
| 2400:9b60:1e::/48 | ALTDB | Valid |
| 2400:9b60:1f::/48 | ALTDB | 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.