Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS138839 (AIL-AS-ID) announces 7 IPv4 and 1 IPv6 prefixes. 2 warnings
| AS page | AS138839 |
|---|---|
| Holder | AIL-AS-ID - PT Adidaya Infocom Lestari |
| Allocation | APNIC, Indonesia (ID), allocated 2019-02-21 |
| Prefixes (IPv4 / IPv6) | 7 / 1 |
| RPKI valid | 63% (5 / 8) |
| Upstreams and peers | 3 |
| Peering policy | Open |
What to fix
-
Warning
3 of 8 announced prefixes have no ROA (RPKI not found): 103.176.66.0/23, 103.176.66.0/24, 103.176.67.0/24.
Without a ROA, networks cannot tell your routes from a hijack.
Fix: Create a ROA for each at your RIR portal, with origin AS138839 and a max length equal to the prefix length:
103.176.66.0/23 AS138839 max-length /23 103.176.66.0/24 AS138839 max-length /24 103.176.67.0/24 AS138839 max-length /24
-
Warning
2 of 8 announced prefixes have no IRR route object: 103.166.93.0/24, 2404:bdc0:a11::/48.
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS138839 in your RIR’s IRR database (or RADB).
route: 103.166.93.0/24 origin: AS138839 route6: 2404:bdc0:a11::/48 origin: AS138839
Checks
Routing and RPKI 3 of 8 announced prefixes have no ROA (RPKI not found): 103.176.66.0/23, 103.176.66.0/24, 103.176.67.0/24.
- Pass: AS138839 announces 7 IPv4 and 1 IPv6 prefixes.
- Warning: 3 of 8 announced prefixes have no ROA (RPKI not found): 103.176.66.0/23, 103.176.66.0/24, 103.176.67.0/24.
- Info: 5 of 8 announced prefixes are RPKI valid.
- Warning: 2 of 8 announced prefixes have no IRR route object: 103.166.93.0/24, 2404:bdc0:a11::/48.
- Info: 3 upstreams and peers, 3 downstream networks seen.
| Holder | AIL-AS-ID - PT Adidaya Infocom Lestari |
|---|---|
| IPv4 prefixes | 7 |
| IPv6 prefixes | 1 |
| RPKI | 5 valid · 3 not found |
| Without IRR route object | 2 |
| Downstream networks | 3 |
| Prefix | RPKI |
|---|---|
| 103.176.66.0/23 | No ROA |
| 103.176.66.0/24 | No ROA |
| 103.176.67.0/24 | No ROA |
Upstreams and peers seen to the left 3
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.apnic.net.
- Pass: Found at rdap.apnic.net.
| Name | AIL-AS-ID |
|---|---|
| Handle | AS138839 |
| Range | AS138839 |
| Country | ID |
| Status | active |
| Registered | 2020-10-30T03:45:55Z |
| Last changed | 2024-08-20T07:58:53Z |
| Abuse contact | adidaya@infocom.co.id |
| Registry (RIR) | APNIC |
|---|---|
| Country | Indonesia (ID) |
| Delegated on | 2019-02-21 |
| Status | Allocated |
| Delegated range | AS138802 – AS138901 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| abuse | IRT-AIL-ID | adidaya@infocom.co.id |
| technical, administrative | Adi Antonio Limianto | adidaya@infocom.co.id |
Source: https://rdap.apnic.net/autnum/138839. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB AS138839 is in PeeringDB as AIL Network.
- Pass: AS138839 is in PeeringDB as AIL Network.
- Info: Peering policy: Open.
- Info: Present at 4 internet exchanges with 4 ports (13G in total).
| Network | AIL Network (Wiznet - Infocom) |
|---|---|
| AS number | AS138839 |
| Type | Cable/DSL/ISP, Asia Pacific |
| Website | https://www.infocom.co.id |
| IRR as-set | AS138839:AS-SET-WIZNET |
| Prefixes (IPv4 / IPv6) | 20 / 50 |
| Traffic | 1-5Gbps, Mostly Inbound |
| Peering policy | Open |
| Policy URL | http://lg.infocom.co.id |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Looking glass | http://lg.infocom.co.id |
| Last updated | 2025-01-17 |
| NOC | noc@infocom.co.id |
|---|
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup