Network · data from 2026-11-12
AS138854 Inter Medialink Solusi
Registry name: IMSNET-AS-ID - PT INTER MEDIALINK SOLUSI, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138854, 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.178.88.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.178.89.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 163.61.191.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.138.218.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.138.219.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 144.79.61.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 163.61.190.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS138854: AS138854:AS-IMS. 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 (AS138854 isn't in the set, or no route object for AS138854 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 | AS138854 in it | Not covered |
|---|---|---|---|---|---|
| AS138854:AS-IMS | APNIC | 5 | 1 | Yes | 0 |
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 5 are in fix.csv.
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.178.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.178.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 163.61.191.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138854 whose prefix no peer sees AS138854 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.138.218.0/23 | APNIC, NTTCOM, RADB | Valid |
| 2404:d5c0::/32 | RADB | 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.