Network · data from 2026-11-12
AS46061 Adi Inti Mandiri
Registry name: AIM-AS-ID - PT. Adi Inti Mandiri, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46061, 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.24.72.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.24.72.0/23 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 103.24.72.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.24.73.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.24.74.0/23 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 103.24.74.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.24.75.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.52.140.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.52.141.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 2400:ea40::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 202.52.140.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS46061: AS46061. 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 (AS46061 isn't in the set, or no route object for AS46061 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 | AS46061 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS46061 | A single AS number, not a set: AS46061 (this network), 18 route objects. | |||||
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 17 are in fix.csv.
- Route object: RIR10
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.24.72.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.72.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.72.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.73.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.74.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.74.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.75.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.52.140.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.52.141.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:ea40::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46061 whose prefix no peer sees AS46061 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.111.220.0/22 | APNIC, RADB | No ROA |
| 103.111.220.0/23 | RADB | No ROA |
| 103.111.220.0/24 | RADB | No ROA |
| 103.111.221.0/24 | RADB | No ROA |
| 103.111.222.0/23 | RADB | No ROA |
| 103.111.222.0/24 | RADB | No ROA |
| 103.111.223.0/24 | 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.