MTR from Indonesia runs a continuous path trace from the Google LLC node in Jakarta to your target, showing per-hop latency and packet loss. The first few hops will be within Google's Jakarta infrastructure before the path enters the public internet. For most international destinations, traffic will exit via Singapore within the first few hops — the Jakarta-Singapore segment (~15 ms) will be visible as a small but consistent latency jump before reaching the main Equinix Singapore or transit carrier infrastructure.

Traces from Jakarta toward Australia via direct cable (Indigo-West, SEA-US) should show a latency jump from ~15 ms (Jakarta to the cable head) to around 60 ms total at the Sydney entry point. If an MTR trace from Jakarta to Sydney instead shows traffic routing through Singapore (adding another peering exchange) and then continuing south, the path is not taking the direct cable route. The difference in end-to-end RTT between direct and indirect routing to Sydney can be 20–30 ms, which is meaningful for latency-sensitive applications.

MTR from Indonesia to European or US targets will always pass through Singapore as the first major waypoint. This means the MTR output from Jakarta to London will look similar to a Singapore-to-London trace for most of the path, with the additional ~15 ms segment from Jakarta to Singapore prepended. Loss on the Singapore-side hops that does not persist through subsequent hops is ICMP rate-limiting, not a real outage. Loss that appears in the European or North American portion of the trace and persists to the final destination is where to focus diagnostic attention.

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.