Packet Loss Statistics From Real Tests
Read this before quoting any number below. These are measurements taken by people who came to a packet loss test — which is not a random sample of anything. Most arrive because something is already wrong. Every figure here therefore describes the tests run on this site, and none of them describes a country's internet. "42 % of tests from country X saw packet loss" is a true sentence about this sample; "42 % of connections in country X have packet loss" is not, and would be wrong by a wide margin.
With that said, the sample is large, it is real UDP rather than a TCP approximation, and it is collected the same way everywhere — so it is useful for comparing like with like: the same kind of visitor, with the same kind of problem, measured with the same method.
Across all 75,051 tests
Two things drive that first figure, and both need saying before anybody quotes it. The obvious one is the sample: almost everyone here came because something was already wrong. The less obvious one is arithmetic — a test counts as "saw loss" if a single packet failed to return, and a two-minute test at 128 packets per second sends more than fifteen thousand of them. The longer and faster the test, the more likely it is to catch one. That is the correct behaviour for a diagnostic tool, and it makes this column a poor measure of severity. The next column along, tests above 1 % loss, is the one that tracks "bad enough to feel".
By country of the person testing
Countries with fewer than 100 stored tests are left out entirely rather than shown with a number that two unlucky measurements could move. Ordered by how many tests there are, not by how bad they look.
| Country | Tests | Tests that saw loss | Median loss, when there was loss | Median ping | Median jitter |
|---|---|---|---|---|---|
| Russia | 21,933 | 78.3 % | 21.54 % | 71 ms | 4 ms |
| United States | 6,544 | 65.31 % | 1.12 % | 42 ms | 5 ms |
| Germany | 5,210 | 68.06 % | 7.12 % | 50 ms | 7 ms |
| Indonesia | 2,806 | 74.34 % | 2.77 % | 39 ms | 8 ms |
| India | 2,055 | 74.45 % | 1.55 % | 90 ms | 5 ms |
| Netherlands | 2,003 | 72.44 % | 9.62 % | 85 ms | 8 ms |
| Ukraine | 1,946 | 69.84 % | 2.89 % | 54 ms | 5 ms |
| Canada | 1,867 | 69.52 % | 1.5 % | 49 ms | 7 ms |
| Iran | 1,740 | 77.07 % | 25.35 % | 130 ms | 13 ms |
| Turkey | 1,674 | 69.95 % | 3.99 % | 71 ms | 6 ms |
| Poland | 1,491 | 65.66 % | 2.03 % | 48 ms | 6 ms |
| Egypt | 1,480 | 56.01 % | 4.25 % | 80 ms | 8 ms |
| Philippines | 1,441 | 73.49 % | 2.83 % | 70 ms | 6 ms |
| United Kingdom | 1,240 | 58.15 % | 2.24 % | 44 ms | 6 ms |
| Finland | 1,070 | 74.67 % | 8.55 % | 79 ms | 7 ms |
| Sweden | 897 | 73.13 % | 0.94 % | 89 ms | 6 ms |
| Italy | 889 | 50.84 % | 3.36 % | 58 ms | 8 ms |
| France | 875 | 71.2 % | 3.87 % | 35 ms | 6 ms |
| Georgia | 803 | 68.87 % | 0.02 % | 66 ms | 2 ms |
| Brazil | 589 | 60.78 % | 1.87 % | 144 ms | 5 ms |
| Colombia | 581 | 86.75 % | 2.58 % | 101 ms | 7 ms |
| Belarus | 538 | 59.85 % | 2.08 % | 57 ms | 4 ms |
| Algeria | 529 | 75.8 % | 5.09 % | 74 ms | 4 ms |
| Kazakhstan | 529 | 66.35 % | 1.79 % | 208 ms | 4 ms |
| Australia | 452 | 57.74 % | 0.88 % | 141 ms | 4 ms |
| Saudi Arabia | 446 | 58.07 % | 1.25 % | 103 ms | 8 ms |
| Switzerland | 422 | 72.27 % | 5.64 % | 77 ms | 10 ms |
| Japan | 413 | 60.29 % | 2.11 % | 104 ms | 5 ms |
| Bangladesh | 410 | 79.02 % | 2.68 % | 63 ms | 6 ms |
| Malaysia | 384 | 69.53 % | 1.89 % | 36 ms | 5 ms |
| Czechia | 383 | 70.5 % | 1.33 % | 30 ms | 6 ms |
| Hungary | 380 | 74.74 % | 2.08 % | 35 ms | 7 ms |
| Venezuela | 366 | 62.57 % | 1.95 % | 87 ms | 3 ms |
| Pakistan | 359 | 72.7 % | 3.96 % | 157 ms | 6 ms |
| Israel | 359 | 57.66 % | 0.45 % | 65 ms | 3 ms |
| Austria | 351 | 64.39 % | 1.74 % | 45 ms | 9 ms |
| South Africa | 336 | 61.9 % | 1.35 % | 209 ms | 9 ms |
| Latvia | 335 | 72.84 % | 9.18 % | 85 ms | 7 ms |
| Slovakia | 326 | 73.01 % | 0.02 % | 55 ms | 4 ms |
| Mexico | 324 | 60.49 % | 2.08 % | 82 ms | 4 ms |
| Peru | 315 | 61.59 % | 0.47 % | 115 ms | 3 ms |
| Vietnam | 306 | 69.28 % | 2.08 % | 59 ms | 4 ms |
| Spain | 300 | 63.67 % | 1.46 % | 62 ms | 6 ms |
| Norway | 289 | 67.82 % | 3.96 % | 49 ms | 6 ms |
| Hong Kong | 276 | 68.12 % | 2.88 % | 96 ms | 4 ms |
| Estonia | 265 | 63.77 % | 7.21 % | 85 ms | 10 ms |
| Iraq | 265 | 64.91 % | 4.69 % | 93 ms | 7 ms |
| Singapore | 260 | 69.23 % | 5.73 % | 72 ms | 6 ms |
| China | 258 | 84.5 % | 13.98 % | 251 ms | 9 ms |
| Denmark | 230 | 67.83 % | 1.94 % | 51 ms | 7 ms |
| Argentina | 211 | 64.93 % | 1.16 % | 174 ms | 5 ms |
| Greece | 210 | 63.81 % | 5.57 % | 66 ms | 8 ms |
| Bulgaria | 209 | 74.64 % | 5.69 % | 96 ms | 9 ms |
| Morocco | 192 | 66.67 % | 1.28 % | 66 ms | 8 ms |
| Lithuania | 189 | 59.79 % | 12.32 % | 73 ms | 6 ms |
| Belgium | 189 | 66.14 % | 1.01 % | 36 ms | 6 ms |
| Portugal | 178 | 56.74 % | 0.93 % | 60 ms | 4 ms |
| Thailand | 176 | 62.5 % | 2.37 % | 54 ms | 6 ms |
| Ecuador | 170 | 50.59 % | 0.64 % | 108 ms | 4 ms |
| Romania | 167 | 59.28 % | 3.99 % | 44 ms | 3 ms |
| Uzbekistan | 162 | 61.11 % | 1.28 % | 242 ms | 4 ms |
| United Arab Emirates | 139 | 58.27 % | 5.5 % | 226 ms | 8 ms |
| Lebanon | 123 | 82.93 % | 4.12 % | 90 ms | 10 ms |
| Nepal | 121 | 66.94 % | 0.88 % | 99 ms | 4 ms |
| Cambodia | 118 | 88.14 % | 3.7 % | 84 ms | 15 ms |
| Moldova | 117 | 55.56 % | 3.86 % | 82 ms | 7 ms |
| Serbia | 111 | 60.36 % | 1.04 % | 38 ms | 7 ms |
| Ireland | 110 | 70.0 % | 2.4 % | 64 ms | 12 ms |
| Azerbaijan | 102 | 64.71 % | 11.35 % | 111 ms | 11 ms |
Medians, not averages: a single half-hour test on a broken line would otherwise drag a whole country with it. The loss column counts tests, not packets — a test appears in it if even one packet failed to come back within a second.
By measurement server
The same tests grouped by which of the four servers they were measured against. This one says more about distance than about anybody's line: a visitor measuring from Jakarta to Frankfurt is measuring half the planet, and the ping column shows it.
| Server | Tests | Tests that saw loss | Median ping | Median jitter |
|---|---|---|---|---|
| Europe (Frankfurt) | 48,609 | 72.59 % | 67 ms | 6 ms |
| Asia (Singapore) | 12,964 | 70.81 % | 94 ms | 6 ms |
| US East (New York) | 9,854 | 67.77 % | 74 ms | 5 ms |
| US West (San Jose) | 3,624 | 61.18 % | 60 ms | 4 ms |
How these numbers were produced
- Every row is a finished test of at least 10 seconds with a real measurement in it. Failed connection attempts, which record a 0 ms ping, are excluded.
- The window is the last 365 days, so a routing change from two years ago no longer shapes what is claimed today.
- Location is the country of the person running the test, derived from their IP address at the time of the test. The IP address itself is never stored — see the privacy policy. Cities are not published: a city row would be a small enough group to start describing identifiable people, and it adds nothing a country row does not.
- No ISP or network operator is named anywhere on this page, and that is deliberate: the same sampling bias applies with much sharper consequences when a company is named, and "provider X has 4 % packet loss" is a claim this data cannot carry.
- Measured over real UDP through WebRTC DataChannels, at the packet rate of the game the visitor picked. The full method is on the methodology page, including what it cannot determine.
- The measurement itself changed in 2026. Before that correction, the reported average ping was biased low for tests at high tick rates — the chart kept the fastest packet of each group instead of a representative one. Rows stored before the fix carry that bias, so the ping columns here should be read as a rough level, not to the millisecond, until a full window of tests has been measured the new way. The share-of-tests-with-loss columns are not affected: they were always counted per packet.
- Rebuilt once a day. This table was generated on 2026-08-16.
Using these figures
You are welcome to quote or reproduce anything on this page, in an article, a forum post or a complaint, with a link back to this page. One request: keep the qualifier attached. The correct form is "of tests run on PingPacketTest.com", not "of connections in" — and if you find a figure here that does not hold up, write to me and it gets corrected.
Want to add a measurement of your own? The test is running by the time the page has loaded, and every finished result can be exported as a PDF report for your provider.