HTTP checks from Indonesia send a full GET request from the Google LLC node in Jakarta, recording the status code, response time, and whether the response completed. CDN providers with Jakarta PoPs include Cloudflare, Akamai, and Google's own CDN layer (given the Google Cloud Jakarta region). For CDN-served content, response times under 20 ms are achievable. For origin servers in Singapore, add roughly 15 ms of network overhead; for origins in Europe, add around 185 ms.

Indonesia is one of the highest-growth markets for e-commerce and streaming in the world, and HTTP performance from Jakarta is a relevant measure for any service targeting Indonesian consumers. The Google LLC node (AS396982) in Jakarta will hit CDN edge PoPs based on anycast routing, which should route to the Google Jakarta region for Google-platform content. For non-Google CDNs, the Jakarta node should be within their catchment area if they have a Jakarta PoP — if HTTP response times indicate Singapore routing instead, the CDN is not serving from its Jakarta capacity for this ASN.

HTTPS connection setup from Jakarta to a US West Coast origin involves at least 190 ms of network overhead for the base RTT. TLS 1.2 handshake adds two more round trips, bringing the connection setup time to around 570 ms before the first application byte. TLS 1.3 reduces this to one round trip (380 ms overhead). If HTTP check times from Indonesia are in the hundreds of milliseconds for a US-origin service and you want to improve them, the fastest options are CDN caching, QUIC/HTTP3 for the first connection, and TLS session resumption for repeat visitors.

Indonesia is the fourth largest internet market in the world by number of users, with over 200 million active internet users. The country is an archipelago of over 17,000 islands, which creates unusual infrastructure challenges — submarine cables connect the major islands (Java, Sumatra, Kalimantan, Sulawesi), but terrestrial fibre density outside Java is significantly lower than in comparable population-size markets. Java, and specifically Jakarta, concentrates the overwhelming majority of the country's internet exchange capacity and international connectivity.

IIX (Indonesia Internet Exchange) in Jakarta is the main national IX, operated by APJII (the Indonesian ISP Association). OpenIXP and JK-IX operate as independent neutral exchanges in Jakarta alongside IIX, giving networks peering options without being dependent on a single fabric. Despite three exchanges being present, a significant share of intra-Indonesian traffic still exits via Singapore for inter-ISP routing — a known inefficiency in the market that APJII has been working to reduce by expanding IIX participation and capacity.

Our probe node in Indonesia runs on AS396982 (Google LLC) in Jakarta. Google Cloud has a region in Jakarta (asia-southeast2), making Indonesia one of the few Southeast Asian markets outside Singapore with a direct Google Cloud presence. The AS396982 node benefits from Google's private backbone for inter-region traffic. Reference RTTs from this node: Jakarta to Singapore ~15 ms, to Hong Kong ~45 ms, to Sydney ~60 ms, to Tokyo ~80 ms, to Mumbai ~70 ms, to Frankfurt ~185 ms, to Los Angeles ~190 ms.

The dominant Indonesian carriers are Telkom Indonesia (AS17451, the incumbent) and its subsidiary Telkomsel, Indosat Ooredoo (AS4761), and XL Axiata (AS24203). Telkom operates the national backbone (NUSANTARA-21) connecting the main islands via domestic submarine cable. Most international capacity exits via Telkom's cable landing stations, which connect to Singapore — Jakarta to Singapore is only 15 ms, and the Singapore-based IX ecosystem (Equinix SG) effectively serves as the international peering layer for Indonesian carriers.

Testing from Jakarta is relevant for operators serving the Indonesian internet market. With 200+ million users and a rapidly expanding middle class driving e-commerce and streaming adoption, Indonesia is an important market for regional services. The 15 ms Jakarta-Singapore RTT means that Singapore-hosted services perform well for Indonesian users, but local Jakarta hosting (as with the Google Jakarta region) offers a further latency advantage, particularly for latency-sensitive applications like gaming, video calling, and financial transactions.