Receive daily results and performance alerts free for 30 days Get Started

Network Latency

as of

This grid displays the network latency of pings between each monitoring location in the Dotcom-Monitor cloud network. With over two dozen monitoring locations throughout the world, the Dotcom-Monitor network serves as a standard baseline for detecting trends in backbone latency communication issues as well as regional outages and slowdowns.

  Madrid Beijing Sydney Copenhagen Seattle IPv6 San Franciso Mumbai Warsaw Paris Johannesburg Buenos Aires Shanghai Tokyo AWS US-East Washington DC Tel-Aviv Amsterdam Dallas Brisbane Denver Frankfurt Montreal Hong Kong Miami San Francisco London New York Minneapolis
Madrid 1 378 329 97 163 170 115 47 19 176 272 383 289 105 96 106 35 145 338 133 37 101 276 126 154 27 99 120
Beijing 376 1 175 206 200
 
281 332 264
 
 
30 58 305 226 360 250 182
 
207 202 230 168 248 190 312 247 230
Sydney 329 175 1 312 174 156 247 329 297 441 360 185 166 213 230 351 298 202 12 192 298 224 270 223 156 287 231 233
Copenhagen 74 206 314 1 161 204 147 18 28 166 267 223 273 92 94 93 12 130 322 163 33 94 272 130 157 30 88 131
Seattle 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
IPv6 San Franciso 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mumbai 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Warsaw 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Paris 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Johannesburg 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Buenos Aires 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Shanghai 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Tokyo 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
AWS US-East 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Washington DC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Tel-Aviv 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Amsterdam 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Dallas 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Brisbane 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Denver 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Frankfurt 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Montreal 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Hong Kong 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Miami 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
San Francisco 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
London 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
New York 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Minneapolis 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

What is Network Latency?

Network latency is the delay in time it takes information (packets) to travel from one node or location to another. This grid reveals any locations that are consistently performing slower that the average locations. Each monitoring location is situated in a Tier 3 data center with multiple pipelines connected directly to the backbone internet providers in that geographic region. Dotcom-Monitor performs thousands of tests to websites, servers and other online systems around the world each minute, so we understand the importance of backbone latency as well as the broader network latency in between the many different nodes along the path of internet traffic.

Test Network Latency

There are several interesting observations when you begin to study the network latency grid. The first to stand out is the stream of 1s diagonally down the page - this is because there is never any lag between a host and itself. You can see a similar result on your local machine by opening a command line and typing: ping localhost. The result should be <1ms which means that it takes less than one millisecond to ping itself.

You may also notice gaps in the grid, particularly between the IPv6 only locations and the locations that are IPv4 only - if the node is unable to communicate using IPv6 or does not have an IPv6 address, then no results will be shown.

Feel free to bookmark this page to come back and perform a quick check of overall internet backbone health.

Great Firewall of China

You may notice that most of the network latency results to and from the Shanghai China monitoring location are orders of magnitude higher than the rest of the locations. This is due to the amount of filtering on internet traffic by the Chinese government. In fact, there are many public websites such as Google, YouTube and Facebook that are completely blocked by the Great Firewall of China. Another reason for higher latency is due to a poorer infrastructure in China than other Western countries.

Additional Network Tools

For additional analytics feel free to navigate to the free tools section of Dotcom-Monitor where you can perform custom ping, traceroute or website speed tests. If you're here troubleshooting network latency issues with a website or server that you manage, please sign up for a free trial for 30 days and gain complete access to the entire suite of Dotcom-Monitor tools to help troubleshoot issues with your network, website availability and much more.