Receive daily results and performance alerts free for 30 days

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 Warsaw Paris Johannesburg Buenos Aires Shanghai Tokyo N. Virginia Washington DC Tel-Aviv Amsterdam Dallas Brisbane Denver Frankfurt Montreal Hong Kong Miami San Francisco London New York Minneapolis
Madrid 1 378 301 41 149 133 52 17 171 252 261 245 76 99 79 32 105 281 110 35 101 376 130 133 26 83 118
Beijing
 
1 223 183 238
 
195 271 321 374 31 109 219 228 287
 
270 351
 
185 247 56
 
225 171 237 194
Sydney 301
 
1 299 154 156 318 284 381 377 168 134 210 224 331 295 182 12 177 297 211 120 216 153 279 210 226
Copenhagen 41 183 299 1 166
 
23 21 165 252 210 274 99 96 82 14 134 293 121 16 91 184 117 147 25 92 122
Seattle 149 237 154 166 1
 
161 144 285 213 228 124 76 68 190 154 52 179 28 143 68 221 74 20 142 58 47
IPv6 San Franciso
 
 
 
 
 
1
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
70
 
 
 
 
Warsaw 52 196 318 23 161
 
1 36 195 251 275 266 114 109 97 27 141 307 140 37 106 198 130 177 40 99 152
Paris 17
 
284 22 144
 
36 1 175 228 279 274 85 78 54 15 118 276 113 20 83 175 109 134 11 83 103
Johannesburg 171 320 381 165 285
 
195 175 1 400 312 375 237 227 210 150 254 425 257 176 259 329 255 282 157 227 271
Buenos Aires 252 374 377 251 213
 
251 228 400 1 416 315 156 160 289 229 170 370 190 236 163 383 155 215 222 151 175
Shanghai 271 31 165 198 227
 
265 262 307 416 1 72 201 227 280 202 289 352 299 192 220 131 238 176 253 253 259
Tokyo 245 99 134 274 124
 
266 274 375 315 64 1 169 169 284 259 143 111 113 241 175 62 173 108 233 182 205
N. Virginia 2620 218 210 99 77
 
114 86 236 156
 
169 1 1 142 87 32 234 38 93 18 217 29 61 77 8 28
Washington DC 99 227 224 96 68
 
105 78 227 160 227 169 1 1 138 80 76 300 44 83 14 249 27 68 75 13 27
Tel-Aviv 79 287 394 82 194
 
97 54 211 288 282 284 142 138 1 62 167 336 162 64 144 242 156 192 66 136 157
Amsterdam 32 169 295 14 154
 
27 15 150 229 234 259 87 80 62 1 124 300 110 10 87 365 116 136 8 74 105
Dallas 105 257 182 134 52 37 141 117 254 170 304 143 32 76 167 124 1 195 21 119 43 190 29 36 109 40 38
Brisbane 282 350 12 293 179
 
307 276 425 370 405 111 312 301 336 300 193 1 189 304 232 124 234 167 279 231 210
Denver 109 290 177 121 28 27 140 113 258 189 310 113 36 44 162 110 21 189 1 118 43 168 48 25 113 37 26
Frankfurt 36 185 296 16 143 153 36 20 176 236 198 241 93 83 64 10 119 304 118 1 90 179 120 146 17 85 112
Montreal 101 247 211 91 68
 
107 83 259 163 228 174 15 14 144 87 43 232 43 90 1 202 39 88 87 9 35
Hong Kong 172 57 155 190 127
 
198 175 329 384 123 62 217 241 244 177 190 123 169 179 203 1 210 163 185 198 202
Miami 130 213 211 117 74 70 130 109 255 155 237 173 27 27 156 116 29 234 48 120 39 210 1 88 103 31 44
San Francisco 133 228 153 161 23 1 174 134 283 215 201 108 60 68 192 134 37 167 26 145 87 166 88 1 135 67 52
London 26 171 279 25 142 133 40 11 157 222 265 232 77 75 66 8 109 279 114 17 87 185 103 134 1 80 97
New York 81
 
209 90 63 67 99 83 222 151 268 180 8 6 136 74 39 230 37 82 9 201 31 67 71 1 30
Minneapolis 118 193 226 122 47 55 152 103 271 175 254 205 28 27 157 105 38 210 26 112 34 202 44 52 98 30 1

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.