Network latency dashboards
The Inter-region latency dashboard provides the average network round-trip latency (round-trip time or RTT) for all pairs of regions in IBM Cloud®. The dashboard shows a snapshot of inter-region RTT expressed in milliseconds.
This snapshot is an average of multiple measurements over the previous 30 days. For each measurement, a pair of Linux VMs (of cx2-8x16 profile) is provisioned in the two corresponding regions in IBM Cloud. VM-to-VM network connectivity is provided
by the Transit Gateway. Netperf TCP RR test is used for measuring the VM-to-VM latency between regions.
The Inter-AZ latency dashboard provides the average network RTT latency within a zone (Intra-Zone) and between availability zones (Inter-Zone) in a multi-zone region (MZR) in IBM Cloud. The dashboard shows a snapshot of inter-availability
zone RTT expressed in milliseconds. This snapshot is an average of multiple measurements over the previous 30 days. For each measurement, a pair of Linux VMs (of cx2-8x16 profile) is provisioned in the two corresponding availability zones in
the same VPC. VM-to-VM network connectivity is provided by the private network within the VPC. Netperf TCP RR test is used for measuring the VM-to-VM latency between the availability zones. The latency between storage and compute instances within
the same zone is dependent on workload characteristics, and on average, expected target latency is in single-digit ms.
The results reported are as measured. There are no performance guarantees implied by these dashboards. These statistics provide visibility into latency between all regions and zones to help you plan the optimal selection for your cloud deployment
and plan for scenarios, such as data residency and performance. These dashboards are not intended for use in troubleshooting.
30 Jun 2024
Inter-region latency
Table 1. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
123 |
113 |
118 |
153 |
185 |
146 |
145 |
| Toronto |
34 |
|
19 |
93 |
83 |
108 |
172 |
214 |
165 |
132 |
| Washington DC |
31 |
20 |
|
98 |
75 |
88 |
176 |
214 |
169 |
120 |
| Frankfurt |
123 |
93 |
98 |
|
13 |
29 |
260 |
278 |
260 |
196 |
| London |
113 |
82 |
75 |
13 |
|
26 |
260 |
280 |
243 |
186 |
| Madrid |
118 |
108 |
88 |
30 |
26 |
|
272 |
291 |
258 |
208 |
| Osaka |
152 |
172 |
177 |
261 |
262 |
271 |
|
123 |
9 |
295 |
| Sydney |
185 |
215 |
216 |
280 |
280 |
290 |
123 |
|
116 |
329 |
| Tokyo |
145 |
165 |
169 |
262 |
243 |
257 |
9 |
116 |
|
288 |
| Sao Paulo |
145 |
131 |
118 |
195 |
187 |
211 |
295 |
326 |
287 |
|
Inter-AZ latency
Table 2. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
0.1 |
2.03 |
2.16 |
| Dallas 2 |
2.03 |
0.1 |
2.19 |
| Dallas 3 |
2.16 |
2.19 |
0.09 |
Table 3. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
0.1 |
1.77 |
1.96 |
| Toronto 2 |
1.77 |
0.09 |
1.97 |
| Toronto 3 |
1.96 |
1.97 |
0.1 |
Table 4. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
0.09 |
0.86 |
0.86 |
| Washington DC 2 |
0.86 |
0.09 |
0.76 |
| Washington DC 3 |
0.86 |
0.76 |
0.07 |
Table 5. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
0.1 |
0.89 |
0.79 |
| Frankfurt 2 |
0.89 |
0.12 |
0.79 |
| Frankfurt 3 |
0.79 |
0.79 |
0.1 |
Table 6. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
0.08 |
2.29 |
1.83 |
| London 2 |
2.29 |
0.08 |
1.91 |
| London 3 |
1.83 |
1.91 |
0.08 |
Table 7. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
0.09 |
0.67 |
0.62 |
| Madrid 2 |
0.67 |
0.09 |
0.79 |
| Madrid 3 |
0.62 |
0.79 |
0.09 |
Table 8. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
0.09 |
1.65 |
1.62 |
| Osaka 2 |
1.65 |
0.1 |
1.66 |
| Osaka 3 |
1.62 |
1.66 |
0.09 |
Table 9. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
0.09 |
1.8 |
0.97 |
| Sydney 2 |
1.8 |
0.1 |
1.86 |
| Sydney 3 |
0.97 |
1.86 |
0.1 |
Table 10. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
0.1 |
1.65 |
1.37 |
| Tokyo 2 |
1.65 |
0.1 |
1.87 |
| Tokyo 3 |
1.37 |
1.87 |
0.1 |
Table 11. 1 Jun 2024–30 Jun 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
0.09 |
1.94 |
2.89 |
| Sao Paulo 2 |
1.94 |
0.09 |
2.09 |
| Sao Paulo 3 |
2.89 |
2.09 |
0.09 |
23 Jun 2024
Inter-region latency
Table 12. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
122 |
113 |
119 |
151 |
185 |
144 |
144 |
| Toronto |
34 |
|
19 |
92 |
82 |
107 |
171 |
214 |
163 |
131 |
| Washington DC |
32 |
20 |
|
97 |
75 |
89 |
175 |
214 |
169 |
119 |
| Frankfurt |
123 |
93 |
97 |
|
13 |
29 |
265 |
284 |
265 |
195 |
| London |
113 |
82 |
75 |
12 |
|
26 |
262 |
283 |
243 |
186 |
| Madrid |
120 |
107 |
89 |
29 |
26 |
|
272 |
291 |
257 |
209 |
| Osaka |
152 |
171 |
176 |
264 |
264 |
273 |
|
124 |
9 |
294 |
| Sydney |
184 |
216 |
216 |
285 |
282 |
292 |
124 |
|
117 |
328 |
| Tokyo |
145 |
164 |
168 |
265 |
243 |
256 |
9 |
116 |
|
286 |
| Sao Paulo |
144 |
129 |
118 |
196 |
187 |
209 |
294 |
327 |
287 |
|
Inter-AZ latency
Table 13. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
0.1 |
2.02 |
2.16 |
| Dallas 2 |
2.02 |
0.1 |
2.18 |
| Dallas 3 |
2.16 |
2.18 |
0.09 |
Table 14. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
0.1 |
1.78 |
1.95 |
| Toronto 2 |
1.78 |
0.09 |
1.94 |
| Toronto 3 |
1.95 |
1.94 |
0.1 |
Table 15. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
0.08 |
0.87 |
0.84 |
| Washington DC 2 |
0.87 |
0.11 |
0.76 |
| Washington DC 3 |
0.84 |
0.76 |
0.07 |
Table 16. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
0.1 |
0.89 |
0.77 |
| Frankfurt 2 |
0.89 |
0.11 |
0.79 |
| Frankfurt 3 |
0.77 |
0.79 |
0.1 |
Table 17. 25 May 2024–23 Jun 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
0.08 |
2.3 |
1.84 |
| London 2 |
2.3 |
0.08 |
1.98 |
| London 3 |
1.84 |
1.98 |
0.08 |
Table 18. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
0.09 |
0.67 |
0.63 |
| Madrid 2 |
0.67 |
0.09 |
0.8 |
| Madrid 3 |
0.63 |
0.8 |
0.09 |
Table 19. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
0.09 |
1.65 |
1.61 |
| Osaka 2 |
1.65 |
0.1 |
1.64 |
| Osaka 3 |
1.61 |
1.64 |
0.09 |
Table 20. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
0.09 |
1.86 |
1.1 |
| Sydney 2 |
1.86 |
0.09 |
1.95 |
| Sydney 3 |
1.1 |
1.95 |
0.09 |
Table 21. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
0.1 |
1.66 |
1.39 |
| Tokyo 2 |
1.66 |
0.1 |
1.87 |
| Tokyo 3 |
1.39 |
1.87 |
0.1 |
Table 22. 25 May 2024–23 Jun 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
0.09 |
1.93 |
2.88 |
| Sao Paulo 2 |
1.93 |
0.09 |
2.08 |
| Sao Paulo 3 |
2.88 |
2.08 |
0.09 |
16 Jun 2024
Inter-region latency
Table 23. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
122 |
113 |
119 |
150 |
185 |
143 |
144 |
| Toronto |
34 |
|
19 |
92 |
83 |
108 |
169 |
216 |
163 |
131 |
| Washington DC |
32 |
19 |
|
96 |
75 |
89 |
174 |
214 |
169 |
119 |
| Frankfurt |
123 |
92 |
96 |
|
13 |
29 |
265 |
284 |
265 |
195 |
| London |
113 |
82 |
75 |
12 |
|
26 |
264 |
283 |
243 |
185 |
| Madrid |
121 |
108 |
90 |
29 |
26 |
|
272 |
292 |
255 |
209 |
| Osaka |
150 |
170 |
175 |
265 |
264 |
273 |
|
124 |
9 |
292 |
| Sydney |
184 |
216 |
216 |
287 |
283 |
293 |
123 |
|
117 |
328 |
| Tokyo |
144 |
162 |
167 |
265 |
242 |
256 |
9 |
116 |
|
286 |
| Sao Paulo |
144 |
129 |
119 |
196 |
187 |
208 |
293 |
328 |
287 |
|
Inter-AZ latency
Table 24. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
0.1 |
2.03 |
2.18 |
| Dallas 2 |
2.03 |
0.09 |
2.19 |
| Dallas 3 |
2.18 |
2.19 |
0.09 |
Table 25. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
0.1 |
1.75 |
1.93 |
| Toronto 2 |
1.75 |
0.09 |
1.91 |
| Toronto 3 |
1.93 |
1.91 |
0.1 |
Table 26. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
0.08 |
0.87 |
0.82 |
| Washington DC 2 |
0.87 |
0.13 |
0.79 |
| Washington DC 3 |
0.82 |
0.79 |
0.09 |
Table 27. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
0.1 |
0.89 |
0.78 |
| Frankfurt 2 |
0.89 |
0.11 |
0.79 |
| Frankfurt 3 |
0.78 |
0.79 |
0.1 |
Table 28. 18 May 2024–16 Jun 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
0.08 |
2.29 |
1.82 |
| London 2 |
2.29 |
0.08 |
2.0 |
| London 3 |
1.82 |
2.0 |
0.08 |
Table 29. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
0.09 |
0.67 |
0.63 |
| Madrid 2 |
0.67 |
0.09 |
0.8 |
| Madrid 3 |
0.63 |
0.8 |
0.09 |
Table 30. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
0.09 |
1.65 |
1.58 |
| Osaka 2 |
1.65 |
0.1 |
1.62 |
| Osaka 3 |
1.58 |
1.62 |
0.09 |
Table 31. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
0.09 |
1.88 |
1.13 |
| Sydney 2 |
1.88 |
0.09 |
2.0 |
| Sydney 3 |
1.13 |
2.0 |
0.09 |
Table 32. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
0.1 |
1.69 |
1.4 |
| Tokyo 2 |
1.69 |
0.1 |
1.86 |
| Tokyo 3 |
1.4 |
1.86 |
0.1 |
Table 33. 18 May 2024–16 Jun 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
0.09 |
1.92 |
2.85 |
| Sao Paulo 2 |
1.92 |
0.09 |
2.07 |
| Sao Paulo 3 |
2.85 |
2.07 |
0.09 |
9 Jun 2024
Inter-region latency
Table 34. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
122 |
113 |
119 |
149 |
186 |
142 |
144 |
| Toronto |
34 |
|
19 |
93 |
83 |
108 |
168 |
215 |
162 |
132 |
| Washington DC |
32 |
20 |
|
95 |
75 |
89 |
173 |
214 |
169 |
118 |
| Frankfurt |
123 |
92 |
94 |
|
12 |
29 |
266 |
286 |
264 |
197 |
| London |
113 |
83 |
75 |
12 |
|
26 |
264 |
284 |
241 |
186 |
| Madrid |
121 |
108 |
89 |
29 |
26 |
|
273 |
293 |
254 |
209 |
| Osaka |
149 |
169 |
174 |
266 |
265 |
275 |
|
124 |
9 |
291 |
| Sydney |
185 |
216 |
217 |
288 |
284 |
293 |
124 |
|
117 |
329 |
| Tokyo |
144 |
162 |
166 |
264 |
241 |
255 |
9 |
117 |
|
285 |
| Sao Paulo |
143 |
131 |
119 |
196 |
187 |
209 |
292 |
327 |
286 |
|
Inter-AZ latency
Table 35. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
0.09 |
2.06 |
2.21 |
| Dallas 2 |
2.06 |
0.09 |
2.21 |
| Dallas 3 |
2.21 |
2.21 |
0.09 |
Table 36. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
0.1 |
1.75 |
1.95 |
| Toronto 2 |
1.75 |
0.09 |
1.9 |
| Toronto 3 |
1.95 |
1.9 |
0.09 |
Table 37. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
0.08 |
0.86 |
0.82 |
| Washington DC 2 |
0.86 |
0.14 |
0.9 |
| Washington DC 3 |
0.82 |
0.9 |
0.11 |
Table 38. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
0.09 |
0.89 |
0.81 |
| Frankfurt 2 |
0.89 |
0.1 |
0.78 |
| Frankfurt 3 |
0.81 |
0.78 |
0.09 |
Table 39. 11 May 2024–9 Jun 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
0.08 |
2.29 |
1.86 |
| London 2 |
2.29 |
0.08 |
2.08 |
| London 3 |
1.86 |
2.08 |
0.08 |
Table 40. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
0.09 |
0.67 |
0.63 |
| Madrid 2 |
0.67 |
0.09 |
0.8 |
| Madrid 3 |
0.63 |
0.8 |
0.09 |
Table 41. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
0.09 |
1.69 |
1.61 |
| Osaka 2 |
1.69 |
0.1 |
1.65 |
| Osaka 3 |
1.61 |
1.65 |
0.09 |
Table 42. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
0.09 |
1.91 |
1.22 |
| Sydney 2 |
1.91 |
0.09 |
2.03 |
| Sydney 3 |
1.22 |
2.03 |
0.09 |
Table 43. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
0.1 |
1.72 |
1.46 |
| Tokyo 2 |
1.72 |
0.09 |
1.9 |
| Tokyo 3 |
1.46 |
1.9 |
0.1 |
Table 44. 11 May 2024–9 Jun 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
0.09 |
1.95 |
2.85 |
| Sao Paulo 2 |
1.95 |
0.09 |
2.1 |
| Sao Paulo 3 |
2.85 |
2.1 |
0.09 |
2 Jun 2024
Inter-region latency
Table 45. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
122 |
113 |
120 |
150 |
185 |
142 |
144 |
| Toronto |
34 |
|
19 |
92 |
83 |
107 |
169 |
215 |
162 |
131 |
| Washington DC |
31 |
20 |
|
95 |
76 |
88 |
173 |
214 |
168 |
119 |
| Frankfurt |
123 |
92 |
94 |
|
12 |
29 |
267 |
287 |
264 |
197 |
| London |
113 |
83 |
75 |
12 |
|
26 |
264 |
285 |
242 |
187 |
| Madrid |
121 |
107 |
90 |
29 |
26 |
|
274 |
295 |
255 |
209 |
| Osaka |
149 |
167 |
173 |
267 |
266 |
275 |
|
124 |
9 |
291 |
| Sydney |
185 |
216 |
216 |
289 |
285 |
295 |
124 |
|
116 |
329 |
| Tokyo |
143 |
161 |
166 |
264 |
241 |
255 |
9 |
117 |
|
284 |
| Sao Paulo |
143 |
130 |
119 |
196 |
186 |
208 |
292 |
327 |
285 |
|
Inter-AZ latency
Table 46. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
0.09 |
2.07 |
2.21 |
| Dallas 2 |
2.07 |
0.09 |
2.21 |
| Dallas 3 |
2.21 |
2.21 |
0.09 |
Table 47. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
0.1 |
1.76 |
1.94 |
| Toronto 2 |
1.76 |
0.09 |
1.89 |
| Toronto 3 |
1.94 |
1.89 |
0.09 |
Table 48. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
0.08 |
1.07 |
0.89 |
| Washington DC 2 |
1.07 |
0.15 |
1.11 |
| Washington DC 3 |
0.89 |
1.11 |
0.11 |
Table 49. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
0.09 |
0.91 |
0.82 |
| Frankfurt 2 |
0.91 |
0.1 |
0.79 |
| Frankfurt 3 |
0.82 |
0.79 |
0.09 |
Table 50. 4 May 2024–2 Jun 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
0.08 |
2.32 |
1.85 |
| London 2 |
2.32 |
0.08 |
2.09 |
| London 3 |
1.85 |
2.09 |
0.08 |
Table 51. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
0.09 |
0.68 |
0.63 |
| Madrid 2 |
0.68 |
0.09 |
0.8 |
| Madrid 3 |
0.63 |
0.8 |
0.09 |
Table 52. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
0.09 |
1.7 |
1.64 |
| Osaka 2 |
1.7 |
0.1 |
1.69 |
| Osaka 3 |
1.64 |
1.69 |
0.09 |
Table 53. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
0.09 |
1.95 |
1.27 |
| Sydney 2 |
1.95 |
0.09 |
2.06 |
| Sydney 3 |
1.27 |
2.06 |
0.09 |
Table 54. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
0.1 |
1.75 |
1.51 |
| Tokyo 2 |
1.75 |
0.09 |
1.93 |
| Tokyo 3 |
1.51 |
1.93 |
0.1 |
Table 55. 4 May 2024–2 Jun 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
0.09 |
1.97 |
2.86 |
| Sao Paulo 2 |
1.97 |
0.09 |
2.11 |
| Sao Paulo 3 |
2.86 |
2.11 |
0.09 |