Network · data from 2026-11-12
AS138839 AIL Network
Registry name: AIL-AS-ID - PT Adidaya Infocom Lestari, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138839, 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.176.66.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.176.66.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.176.67.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.166.93.0/24 | Valid | None | 673 100% |
| 2404:bdc0:a11::/48 | Valid | None | 636 100% |
| 103.138.14.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.138.15.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.166.92.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS138839: AS138839:AS-SET-WIZNET. 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 (AS138839 isn't in the set, or no route object for AS138839 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 | AS138839 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS138839:AS-SET-WIZNET | 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 18 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR6
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.176.66.0/23 | No ROA covers it. Add a ROA for AS138839, maxLength 23. |
| Route object: RIR | 103.176.66.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.176.66.0/24 | No ROA covers it. Add a ROA for AS138839, maxLength 24. |
| Route object: RIR | 103.176.66.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.176.67.0/24 | No ROA covers it. Add a ROA for AS138839, maxLength 24. |
| Route object: RIR | 103.176.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 103.166.93.0/24 | No route object for it. Add a route object with origin AS138839 in the RIR database for the space. |
| Route object: none | 2404:bdc0:a11::/48 | No route object for it. Add a route object with origin AS138839 in the RIR database for the space. |
| Route object: RIR | 103.138.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.138.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.166.92.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS138839:AS-SET-WIZNET | PeeringDB names AS138839:AS-SET-WIZNET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS138839 whose prefix no peer sees AS138839 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.125.172.0/22 | RADB | No ROA |
| 103.125.172.0/24 | RADB | No ROA |
| 103.125.173.0/24 | RADB | No ROA |
| 103.125.174.0/24 | RADB | No ROA |
| 103.125.175.0/24 | RADB | No ROA |
| 103.138.14.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.