Telkom Indonesia IP Ranges
Telkom Indonesia is the country's largest fixed-line and broadband carrier, based in Jakarta. AS7713 is the autonomous system that carries its Indonesian traffic, recorded at APNIC as telkomnet-as-ap for PT Telekomunikasi Indonesia under the organisation handle ORG-TI10-AP, described in the record as an internet access provider and NAP, and last modified in February 2026. Its other number, AS17974, has not announced a prefix in the global routing table since 2021, so a Telkom Indonesia address seen today has almost certainly arrived through AS7713.
- Provider
- Telkom Indonesia
- Primary ASN
- AS7713
- Category
- ISP
- Headquarters
- Jakarta, Indonesia
- Announced IPv4 prefixes
- 3806
- Registry
- APNIC
Known IP ranges
These prefixes are currently announced to the global routing table by AS7713 (telkomnet-as-ap - PT Telekomunikasi Indonesia). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
125.166.0.0/15
36.65.0.0/16
36.69.0.0/16
180.241.0.0/16
180.253.0.0/16
180.248.0.0/16
36.81.0.0/16
110.139.0.0/16
180.249.0.0/16
125.165.0.0/16
2001:4489::/32
2001:4488::/32
2001:448a::/32 (IPv6)
What does a Telkom Indonesia IP mean in a privacy test?
An address on AS7713 puts the exit inside Indonesia on Telkom's own network, which for someone running a tunnel is the result to worry about rather than the one to want. Confirming it by reverse DNS does not work. Lookups for addresses in 36.65.0.0/16, 180.241.0.0/16 and 110.139.0.0/16 do not come back empty, they fail: the nameservers for those in-addr.arpa zones answer REFUSED and the resolver returns a server failure. That is worth knowing before drawing conclusions from a blank hostname column in a log viewer, because on this network a blank means broken delegation, not an unnamed or deliberately hidden host. It also means the only identification available is the origin ASN and the APNIC record, and both point at PT Telekomunikasi Indonesia regardless of whether the line behind the address is a household or an office.
Telkom's published records, and who actually filed them
The public documentation for AS7713 is filed under a different company name than the one on the addresses. Its PeeringDB entry belongs to PT Telekomunikasi Indonesia International, the group's international carrier arm, trading as TELIN, and it declares a restrictive peering policy, a looking glass at lg.telin.co.id, and presence at 39 exchanges running from IIX-Jakarta and JKT-IX out to AMS-IX, DE-CIX Frankfurt, HKIX and SIX Seattle. The IRR set it points at is AS7713:AS-TELKOM-TRANSIT. Read that record as documentation of the transit product, not as a description of the domestic broadband pools.
There is no geofeed and no published allowlist. The registry side is straightforward: the covering objects carry the netname TELKOMNET, allocated to PT Telekomunikasi Indonesia at Menara Multimedia on Jl. Kebon Sirih in Jakarta, with abuse routed to abuse@telkom.net.id and an incident-response object IRT-IDTELKOM-ID. The trap is the IRR itself: route objects created between 2011 and 2015 still name AS17974 as origin for prefixes AS7713 announces today, and AS17974 now has no prefixes and no observed BGP neighbours at all. When a filter or an attribution tool disagrees with the live origin, a stale object of that vintage is the likely reason.
Subscriber, transit customer, or Telkom itself
With reverse DNS unavailable, the practical split is between the transit customers listed under AS7713:AS-TELKOM-TRANSIT and the retail pools that keep AS7713 as their own origin. Expanding that AS-SET gives the member networks Telkom carries; anything originating in AS7713 itself and sitting inside the large consumer allocations is an access line. The registry will not separate them for you - the covering objects are ALLOCATED PORTABLE blocks in Telkom's name at /11 and /15 size with no per-customer assignment objects beneath them, so a whois query on a subscriber address and on a Telkom router returns the same TELKOMNET record.
For inbound traffic the ASN's own description is the useful marker. AS7713 is registered as an internet access provider and NAP, and its space is consumed by access customers rather than rented out as compute, so an unsolicited connection arriving from it is far more likely to be a compromised subscriber device than anything Telkom operates. Two checks are worth doing before attributing it anywhere: confirm the live origin really is AS7713 and not the dormant AS17974 that stale route objects still claim, and confirm the prefix is not announced by a downstream member of the transit set, which would place the machine on a customer's network rather than on Telkom's.
Related tools
Frequently asked questions
What IP ranges does Telkom Indonesia use?
They are announced under AS7713, recorded at APNIC as telkomnet-as-ap for PT Telekomunikasi Indonesia and described there as an internet access provider and NAP. The largest blocks currently in the routing table are listed above. The covering registry objects carry the netname TELKOMNET and a Jakarta address at Menara Multimedia on Jl. Kebon Sirih.
Why does a Telkom Indonesia IP appear in my privacy test?
An address on AS7713 puts the exit inside Indonesia on Telkom's own network, which for someone running a tunnel is the result to worry about rather than the one to want. Confirming it by reverse DNS does not work. Lookups for addresses in 36.65.0.0/16, 180.241.0.0/16 and 110.139.0.0/16 do not come back empty, they fail: the nameservers for those in-addr.arpa zones answer REFUSED and the resolver returns a server failure. That is worth knowing before drawing conclusions from a blank hostname column in a log viewer, because on this network a blank means broken delegation, not an unnamed or deliberately hidden host. It also means the only identification available is the origin ASN and the APNIC record, and both point at PT Telekomunikasi Indonesia regardless of whether the line behind the address is a household or an office.
Why does a reverse lookup on a Telkom Indonesia IP fail?
Because the reverse zones are not answering. Queries for addresses in 36.65.0.0/16, 180.241.0.0/16 and 110.139.0.0/16 return a server failure rather than an empty result, with the nameservers for those in-addr.arpa zones responding REFUSED. A blank hostname on one of these addresses is a delegation problem, not evidence that the host is unnamed or hiding.
Is AS17974 still Telkom Indonesia?
It is still registered to the company but it has stopped announcing. AS17974, TELKOMNET-AS2-AP, has no prefixes in the global table and no observed BGP neighbours, and its last IPv6 announcement was seen in 2021. Route objects created between 2011 and 2015 still name it as the origin for prefixes AS7713 announces today, which is a frequent source of wrong attribution.
Does Telkom Indonesia publish a geofeed?
No. There is no RFC 8805 geofeed, no geofeed attribute on the APNIC objects and no published allowlist. For placing an address the only sources are the APNIC country field, which says nothing more precise than ID, and the ASN itself. For abuse the record points to abuse@telkom.net.id and the incident-response object IRT-IDTELKOM-ID.