Network · data from 2026-11-12
AS58482 Palapa Media Indonesia
Registry name: PALAPAMEDIA-AS-ID - PT. Palapa Media Indonesia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58482, 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.
| 2404:f900::/32 | Valid | None | 635 100% |
| 2404:f900::/48 | Valid | None | 635 100% |
| 2404:f900:1::/48 | Valid | None | 635 100% |
| 2404:f900:2::/48 | Valid | None | 635 100% |
| 2404:f900:3::/48 | Valid | None | 635 100% |
| 2404:f900:4::/48 | Valid | None | 635 100% |
| 2404:f900:5::/48 | Valid | None | 635 100% |
| 2404:f900:6::/48 | Valid | None | 635 100% |
| 2404:f900:7::/48 | Valid | None | 635 100% |
| 43.254.124.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.254.125.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 673 100% |
| 43.254.126.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 673 100% |
| 43.254.127.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 673 100% |
| 103.11.107.0/24 | Valid | Other IRR onlyREACH | 673 100% |
| 103.28.224.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.28.224.0/24 | Valid | Other IRR onlyREACH | 673 100% |
| 103.28.225.0/24 | Valid | Other IRR onlyREACH | 673 100% |
| 103.28.226.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.28.226.0/24 | Valid | Other IRR onlyREACH | 673 100% |
| 103.28.227.0/24 | Valid | Other IRR onlyREACH | 673 100% |
| 43.254.124.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 672 100% |
| 43.254.124.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.28.224.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS58482: AS-PMI-ID. 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 (AS58482 isn't in the set, or no route object for AS58482 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 | AS58482 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-PMI-ID | 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 25 are in fix.csv.
- Route object: none9
- Route object: RIR12
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2404:f900::/32 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900:1::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900:2::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900:3::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900:4::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900:5::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900:6::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: none | 2404:f900:7::/48 | No route object for it. Add a route object with origin AS58482 in the RIR database for the space. |
| Route object: RIR | 43.254.124.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.254.125.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 43.254.126.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 43.254.127.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.11.107.0/24 | Route object only in REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.224.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.224.0/24 | Route object only in REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.225.0/24 | Route object only in REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.226.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.226.0/24 | Route object only in REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.28.227.0/24 | Route object only in REACH. Add it in the RIR database for the space. |
| Route object: RIR | 43.254.124.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| AS-SET: not found | AS-PMI-ID | PeeringDB names AS-PMI-ID; no IRR database read has it. |
Route objects not announced
Route objects with origin AS58482 whose prefix no peer sees AS58482 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.254.126.0/23 | NTTCOM, RADB | Valid |
| 103.11.106.0/23 | NTTCOM, RADB | No ROA |
| 103.11.106.0/24 | REACH | Invalid: origin |
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.