How Traffic Actually Reaches Dota 2's SEA Servers from the Philippines

When you queue a ranked match from Manila or Cebu, the packets carrying your inputs travel through several networks before they reach a Dota 2 SEA server. The path is not a straight line, and the path you actually get is decided by routing policies you don't control. This piece walks through what that path looks like, based on publicly available networking data.

Sources for every claim are listed at the bottom. No first-person measurements are presented as data here; where numbers are quoted they come from published references.

1. Where are the SEA servers, actually?

Valve runs Dota 2's matchmaking servers from datacentres in several regions. The SEA region is primarily hosted in Singapore. There is no Valve datacentre in Manila or Cebu, so every Filipino player's packets must leave the country to reach the match server.^[1]

This is the fundamental shape of the problem. The minimum round-trip from Manila to Singapore is around 30 ms in theory, and roughly 35–60 ms in practice when you account for equipment, routing, and the fact that fibre cables don't run in straight lines.

2. The submarine cables your packets ride

International internet traffic from the Philippines runs over submarine cables. The relevant ones for Singapore-bound traffic include the Asia-America Gateway (AAG), Asia Submarine-cable Express (ASE), Southeast Asia–Japan Cable (SJC), and Asia Pacific Gateway (APG). Each cable has multiple landing stations in the Philippines — Batangas, Nasugbu, La Union, Davao — and lands again in Singapore or transits via Brunei, Vietnam, or Hong Kong.^[2]

Which cable your traffic takes is decided by your ISP's peering relationships, not your geography. A Cebu player can have a longer fibre path to Singapore than a Manila player on the same ISP, if their traffic is hauled back to Manila and then out again. Cable outages — which do happen — also force ISPs to reroute, sometimes for weeks.

3. How to read a tracert from Manila

You can see your own route with tracert from any Windows command prompt. The command lists every router your packets hop through, with a hostname for each. Hostnames are often labelled with city codes — read them, and the route tells its own story.

> tracert -d 103.10.124.1

  1     1 ms     1 ms     1 ms  192.168.1.1                     ← your router
  2     8 ms     7 ms     8 ms  10.x.x.x                        ← ISP CGNAT
  3    11 ms    11 ms    12 ms  pldt-mnl-bgw1.example.net       ← Manila core
  4    13 ms    14 ms    13 ms  pldt-mnl-edge1.example.net      ← Manila edge
  5    42 ms    43 ms    41 ms  sg-singtel-core.example.net     ← Singapore arrival
  6    44 ms    45 ms    43 ms  sg-akamai-edge.example.net      ← Singapore CDN edge
  7    47 ms    46 ms    46 ms  sg-valve.example.net            ← Dota 2 SEA server

Things to look for: the latency jump from a Manila hop to a Singapore hop should be around 25–35 ms. If you see a hop labelled hkg (Hong Kong), nrt (Tokyo), or lax (Los Angeles), your packets are taking a long way around and your ping is going to suffer.

4. PH ISP peering at PHOpenIX and SGIX

Internet exchange points (IXPs) are physical locations where networks meet to exchange traffic. PHOpenIX is the main Philippine IXP. SGIX (Singapore Internet Exchange) is its counterpart in Singapore. ISPs that peer at both ends, and ride a direct submarine cable between them, tend to deliver lower and more stable ping to Singapore-hosted services.^[3]

Peering decisions are commercial. ISPs negotiate them in private. You can't inspect them directly, but you can observe their results — by running tracerts at different times of day and noting which hops appear, and by comparing consistency across ISPs (which is the entire premise of the PH ISP guide).

5. Common bad paths and how they happen

A few patterns appear repeatedly in community-reported tracerts and forum threads.^[4][5]

• Hong Kong detour: packets transit via Hong Kong before reaching Singapore. Adds roughly 20–40 ms of latency. Often a symptom of cable maintenance or a peering change.
• US transit: packets cross the Pacific to Los Angeles and come back. Adds 150+ ms. Rare but catastrophic; happens during major cable cuts.
• Asymmetric routing:your traffic to the server takes one path; the server's traffic back to you takes a different one. Round-trip ping can be unstable even when individual hops look fine.
• Congested peering at peak hours: the route stays the same but a busy IXP link buffers packets. Ping stays low but jitter and packet loss spike between 7pm and midnight.

6. What you can (and can't) do about routing

You can't directly tell your ISP to use a different submarine cable. What you can do:

• Run tracertwhen ping is bad and when it's good. If the routes differ, send both to your ISP support channel — they have the leverage to escalate.
• Try a gaming VPN such as ExitLag or NoPing as a diagnostic. If a VPN-routed connection ends up materially better, the problem is upstream of your ISP's egress.
• Switch ISPs. Brutal, but on a long enough timeline this is sometimes the only fix — see the comparative summary in the PH ISP guide.

The most important takeaway: routing is upstream of you. If your ping doubles overnight on a connection that was fine last week, you didn't do anything wrong. Something upstream changed, and the path your packets take to Singapore changed with it.

Sources

1. Steam Database and Valve's public matchmaking documentation, on regional server locations.
2. TeleGeography Submarine Cable Map — submarinecablemap.com (Philippine landing stations, AAG/ASE/SJC/APG routing).
3. PHOpenIX and SGIX participant lists (publicly published by each exchange operator).
4. Reddit r/Philippines and r/DotA2 routing threads, community-reported tracerts (anecdotal but consistent).
5. BGP route data from public Looking Glass servers operated by PCH and RIPE.