Network · data from 2026-11-12
AS58820 ApikNet
Registry name: IDNIC-PTAMI-AS-ID - APIK Media Networks, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58820, 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.
| 2407:72c0::/32 | Invalid: origin | None | 3 0%low visibility |
| 2405:a740::/32 | No ROA | Other IRR onlyRADB | 635 100% |
| 103.113.28.0/24 | Valid | Other IRR onlyRADB, RIPE-NONAUTH | 672 100% |
| 103.169.210.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.169.211.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2407:6d40::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 2407:6f40::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 2407:7240::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 2001:df1:9000::/48 | Valid | Other IRR onlyRIPE-NONAUTH | 335 53% |
| 103.97.111.0/24 | Valid | RIR databaseAPNIC, RADB, RIPE-NONAUTH | 672 100% |
| 103.136.17.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.136.18.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.136.19.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.241.24.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, RIPE-NONAUTH | 672 100% |
| 103.136.16.0/23 | Valid | RIR databaseAPNIC, RADB | 184 27% |
| 103.136.16.0/24 | Valid | RIR databaseAPNIC, RADB | 184 27% |
| 103.136.18.0/23 | Valid | RIR databaseAPNIC, RADB | 184 27% |
AS-SET
PeeringDB's irr_as_set for AS58820: AS-APIK. 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 (AS58820 isn't in the set, or no route object for AS58820 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 | AS58820 in it | Not covered |
|---|---|---|---|---|---|
| AS-APIK | RADB | 21 | 2 | Yes | 1 |
| APNIC (also) | 7 | 1 | Yes | 1 |
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 26 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR8
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2407:72c0::/32 | ROAs covering it name AS138860, not AS58820. If AS58820 should announce it, add a ROA for AS58820. |
| Route object: none | 2407:72c0::/32 | No route object for it. Add a route object with origin AS58820 in the RIR database for the space. |
| ROA: none | 2405:a740::/32 | No ROA covers it. Add a ROA for AS58820, maxLength 32. |
| Route object: RIR | 2405:a740::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.113.28.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 103.169.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.169.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2407:6d40::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2407:6f40::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2407:7240::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df1:9000::/48 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58820 whose prefix no peer sees AS58820 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.97.140.0/23 | APNIC, RADB | Valid |
| 103.136.16.0/22 | APNIC, RADB | Valid |
| 103.152.242.0/23 | RADB | Valid |
| 103.167.132.0/23 | RADB | Valid |
| 103.167.136.0/23 | RADB | Valid |
| 103.169.210.0/23 | RADB | Valid |
| 103.185.38.0/23 | RADB | Valid |
| 103.185.44.0/23 | RADB | Valid |
| 103.185.48.0/23 | RADB | Valid |
| 103.185.52.0/23 | RADB | Valid |
| 103.185.82.0/23 | RADB | Valid |
| 2001:df4:580::/48 | RADB | No ROA |
| 2001:df4:2480::/48 | RADB | No ROA |
| 2001:df4:5d00::/48 | RADB, RIPE-NONAUTH | No ROA |
| 2405:a6c0::/32 | 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.