Network · data from 2026-11-12
AS138123 ADEAKSA INDO JAYATAMA
Registry name: DEXA-AS-ID - PT. ADEAKSA INDO JAYATAMA, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138123, 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:3040::/48 | No ROA | Nonecovered by 2404:3040::/32 | 34 5%low visibility |
| 2404:3040::/32 | No ROA | Other IRR onlyRADB | 635 100% |
| 103.132.52.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.132.53.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.132.55.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.132.54.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS138123: AS138123:AS-DEXA. 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 (AS138123 isn't in the set, or no route object for AS138123 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 | AS138123 in it | Not covered |
|---|---|---|---|---|---|
| AS138123:AS-DEXA | APNIC | 3 | 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 7 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2404:3040::/48 | No ROA covers it. Add a ROA for AS138123, maxLength 48. |
| Route object: none | 2404:3040::/48 | No route object for it. A route object for 2404:3040::/32 with origin AS138123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138123 in the RIR database for the space. |
| ROA: none | 2404:3040::/32 | No ROA covers it. Add a ROA for AS138123, maxLength 32. |
| Route object: RIR | 2404:3040::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138123 whose prefix no peer sees AS138123 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.132.52.0/22 | APNIC | Valid |
| 103.132.52.0/23 | RADB | Valid |
| 103.132.54.0/23 | 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.