Menu

The data behind the test

23 test points in 20 regions, 2 regions without one, 28 games with server facts from their publishers, and every source with the date we read it.

Updated

Regions and test points

The test times 23 test points in 20 regions. Each test point is an Amazon DynamoDB endpoint that answers a short request from any browser at the address /ping. Amazon documents the endpoint hosts but not that address, so it can change without notice; the test then shows not reachable, never a guess.

Every test point the browser times, by region from west to east
RegionAmazon regionHostNote
North America WestUS West (N. California)dynamodb.us-west-1.amazonaws.comOne of several; the best counts
North America WestUS West (Oregon)dynamodb.us-west-2.amazonaws.comOne of several; the best counts
North America CentralUS East (Ohio)dynamodb.us-east-2.amazonaws.comStands in for Chicago, Dallas and Atlanta
North America EastUS East (N. Virginia)dynamodb.us-east-1.amazonaws.comNone
Latin America NorthMexico (Central)dynamodb.mx-central-1.amazonaws.comNone
Brazil (Sao Paulo)South America (São Paulo)dynamodb.sa-east-1.amazonaws.comNone
Europe WestEurope (Ireland)dynamodb.eu-west-1.amazonaws.comOne of several; the best counts
Europe WestEurope (London)dynamodb.eu-west-2.amazonaws.comOne of several; the best counts
Europe WestEurope (Paris)dynamodb.eu-west-3.amazonaws.comOne of several; the best counts
Europe CentralEurope (Frankfurt)dynamodb.eu-central-1.amazonaws.comNone
Europe NorthEurope (Stockholm)dynamodb.eu-north-1.amazonaws.comNone
Israel (Tel Aviv)Israel (Tel Aviv)dynamodb.il-central-1.amazonaws.comNone
Middle East (Gulf)Middle East (UAE)dynamodb.me-central-1.amazonaws.comStands in for Bahrain
South AfricaAfrica (Cape Town)dynamodb.af-south-1.amazonaws.comStands in for Johannesburg
India (Mumbai)Asia Pacific (Mumbai)dynamodb.ap-south-1.amazonaws.comNone
Southeast Asia (Singapore)Asia Pacific (Singapore)dynamodb.ap-southeast-1.amazonaws.comNone
Indonesia (Jakarta)Asia Pacific (Jakarta)dynamodb.ap-southeast-3.amazonaws.comNone
Hong KongAsia Pacific (Hong Kong)dynamodb.ap-east-1.amazonaws.comNone
Taiwan (Taipei)Asia Pacific (Taipei)dynamodb.ap-east-2.amazonaws.comNone
Japan (Tokyo)Asia Pacific (Tokyo)dynamodb.ap-northeast-1.amazonaws.comNone
Korea (Seoul)Asia Pacific (Seoul)dynamodb.ap-northeast-2.amazonaws.comNone
Oceania (Sydney)Asia Pacific (Sydney)dynamodb.ap-southeast-2.amazonaws.comNone
Oceania (Melbourne)Asia Pacific (Melbourne)dynamodb.ap-southeast-4.amazonaws.comNone

Latin America South and Turkey (Istanbul) have no test point yet. A region with more than one test point takes its best one, a steady test point before an unstable one, then the faster of the two. The method page has the full order.

Terms

Amazon's Acceptable Use Policy, read October 15, 2026, applies to everyone who uses Amazon's services. It forbids use that harms the security, integrity or availability of any system and has no clause about latency checks. One run of the test sends 11 small requests to each test point, the warm-up included.

Reference times from Germany

Our own server in a German data center times every test point every 30 minutes with the same request, using curl. The table holds October 15, 2026 to October 18, 2026: the number of runs, the median of the run medians, and the fastest and slowest run. It is one data center line, not a home line: another network can read a region tens of milliseconds faster or slower, so no verdict ever uses it.

Round trip from a data center in Germany, October 15, 2026 to October 18, 2026
Test pointRegionRunsMedianFastest runSlowest run
US East (N. Virginia)North America East9194 ms91 ms895 ms
US East (Ohio)North America Central91105 ms100 ms116 ms
US West (N. California)North America West91166 ms160 ms178 ms
US West (Oregon)North America West91172 ms166 ms197 ms
Mexico (Central)Latin America North91149 ms146 ms163 ms
South America (São Paulo)Brazil (Sao Paulo)91220 ms216 ms227 ms
Europe (Ireland)Europe West9124 ms23 ms26 ms
Europe (London)Europe West9116 ms15 ms17 ms
Europe (Paris)Europe West9113 ms13 ms14 ms
Europe (Frankfurt)Europe Central915 ms4 ms6 ms
Europe (Stockholm)Europe North9127 ms25 ms30 ms
Middle East (UAE)Middle East (Gulf)91121 ms120 ms125 ms
Africa (Cape Town)South Africa91154 ms150 ms156 ms
Asia Pacific (Mumbai)India (Mumbai)91167 ms126 ms592 ms
Asia Pacific (Singapore)Southeast Asia (Singapore)91160 ms160 ms167 ms
Asia Pacific (Hong Kong)Hong Kong91258 ms254 ms387 ms
Asia Pacific (Tokyo)Japan (Tokyo)91227 ms226 ms465 ms
Asia Pacific (Seoul)Korea (Seoul)91227 ms226 ms233 ms
Asia Pacific (Sydney)Oceania (Sydney)91314 ms312 ms384 ms
Asia Pacific (Jakarta)Indonesia (Jakarta)9175 ms173 ms176 ms
Asia Pacific (Taipei)Taiwan (Taipei)9204 ms204 ms208 ms
Israel (Tel Aviv)Israel (Tel Aviv)961 ms59 ms62 ms
Asia Pacific (Melbourne)Oceania (Melbourne)9328 ms323 ms334 ms

A slowest run far above the median marks one bad run, not the usual time. The route guide shows how a route change looks across runs.

Game server facts

28 games, each read from its publisher's own pages: where the servers are, how to see your ping, how to change server and what the publisher says about a good ping. 11 publishers present a complete server list, 5 name some locations only, and 12 name none. A fact a publisher does not publish shows as not published, and a missing instruction as does not document this.

Every game page lists its sources with the date we read them. On October 18, 2026 we read every game's instructions for seeing ping and changing server again on the publisher's page before publishing them. The games hub shows each game's checked month.

Sources

Every page the site's facts come from, 194 in all, with the date we last read it and what it supports. Pages from route optimizer makers support only the GearUP Booster page and the description of route optimizers; they never decide a verdict.

Game publishers (154)

Amazon Web Services (3)

Route optimizer makers and the affiliate network (37)

Dates

  • Research behind the site: October 15, 2026.
  • Instructions for seeing ping and changing server read again: October 18, 2026.
  • Reference times from Germany: October 15, 2026 to October 18, 2026.
  • Browser overhead study: October 17, 2026.

Changelog

  • October 18, 2026. Every game's instructions for seeing your ping and changing server read again on the publisher's own page. Four corrected: Counter-Strike 2, Call of Duty: Mobile and Marvel Rivals now say only what their pages state, and Overwatch gained Blizzard's answer that you cannot pick a server. PUBG MOBILE gained the line that a party across servers plays on the host's server.
  • October 17, 2026. Four test points added: Indonesia (Jakarta), Taiwan (Taipei), Israel (Tel Aviv), Oceania (Melbourne). Indonesia, Taiwan and Tel Aviv entries of game server lists now measure on their own test point.
  • October 15, 2026. First research: 28 games, 22 regions and their test points from publisher and Amazon pages. The reference measurement from our server in Germany starts.

Corrections

If a publisher moved a server or changed a menu, send the page that shows it to info@whyismyping.com. We check every report against that page and date the change here.