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.
For information about the mapping between regions and zones, see Zone mapping per account.
30 Mar 2025
Inter-region latency
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
31 |
123 |
113 |
117 |
150 |
185 |
142 |
141 |
| Toronto |
34 |
|
19 |
92 |
82 |
106 |
170 |
214 |
162 |
129 |
| Washington DC |
31 |
19 |
|
88 |
76 |
88 |
176 |
214 |
171 |
120 |
| Frankfurt |
123 |
92 |
87 |
|
13 |
29 |
233 |
250 |
225 |
193 |
| London |
113 |
82 |
76 |
13 |
|
27 |
245 |
262 |
237 |
187 |
| Madrid |
116 |
105 |
87 |
29 |
27 |
|
258 |
276 |
251 |
208 |
| Osaka |
149 |
170 |
175 |
233 |
244 |
260 |
|
123 |
9 |
290 |
| Sydney |
184 |
216 |
214 |
250 |
262 |
276 |
123 |
|
117 |
325 |
| Tokyo |
143 |
162 |
167 |
225 |
237 |
251 |
9 |
117 |
|
281 |
| Sao Paulo |
140 |
128 |
124 |
196 |
188 |
207 |
289 |
325 |
282 |
|
Inter-AZ latency
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
us-south-dal10-a |
us-south-dal12-a |
us-south-dal13-a |
us-south-dal14-a |
| us-south-dal10-a |
0.09 |
1.76 |
1.91 |
2.17 |
| us-south-dal12-a |
1.76 |
0.1 |
1.89 |
2.15 |
| us-south-dal13-a |
1.91 |
1.89 |
0.1 |
2.31 |
| us-south-dal14-a |
2.17 |
2.15 |
2.31 |
0.1 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
ca-tor-tor01-a |
ca-tor-tor04-a |
ca-tor-tor05-a |
| ca-tor-tor01-a |
0.1 |
1.52 |
1.74 |
| ca-tor-tor04-a |
1.52 |
0.09 |
1.7 |
| ca-tor-tor05-a |
1.74 |
1.7 |
0.1 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
us-east-wdc04-a |
us-east-wdc06-a |
us-east-wdc07-a |
| us-east-wdc04-a |
0.09 |
0.64 |
0.67 |
| us-east-wdc06-a |
0.64 |
0.1 |
0.6 |
| us-east-wdc07-a |
0.67 |
0.6 |
0.08 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
eu-de-fra02-a |
eu-de-fra04-a |
eu-de-fra05-a |
| eu-de-fra02-a |
0.11 |
0.74 |
0.67 |
| eu-de-fra04-a |
0.74 |
0.11 |
0.66 |
| eu-de-fra05-a |
0.67 |
0.66 |
0.12 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
eu-gb-lon04-a |
eu-gb-lon05-a |
eu-gb-lon06-a |
| eu-gb-lon04-a |
0.08 |
2.18 |
1.99 |
| eu-gb-lon05-a |
2.18 |
0.08 |
1.71 |
| eu-gb-lon06-a |
1.99 |
1.71 |
0.09 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
eu-es-mad02-a |
eu-es-mad04-a |
eu-es-mad05-a |
| eu-es-mad02-a |
0.1 |
0.68 |
0.61 |
| eu-es-mad04-a |
0.68 |
0.1 |
0.79 |
| eu-es-mad05-a |
0.61 |
0.79 |
0.1 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
jp-osa-osa21-a |
jp-osa-osa22-a |
jp-osa-osa23-a |
| jp-osa-osa21-a |
0.1 |
1.48 |
1.42 |
| jp-osa-osa22-a |
1.48 |
0.1 |
1.48 |
| jp-osa-osa23-a |
1.42 |
1.48 |
0.1 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
au-syd-syd01-a |
au-syd-syd04-a |
au-syd-syd05-a |
| au-syd-syd01-a |
0.09 |
1.62 |
0.91 |
| au-syd-syd04-a |
1.62 |
0.09 |
1.78 |
| au-syd-syd05-a |
0.91 |
1.78 |
0.1 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
jp-tok-tok02-a |
jp-tok-tok04-a |
jp-tok-tok05-a |
| jp-tok-tok02-a |
0.1 |
1.47 |
0.97 |
| jp-tok-tok04-a |
1.47 |
0.11 |
1.67 |
| jp-tok-tok05-a |
0.97 |
1.67 |
0.1 |
1 Mar 2025–30 Mar 2025
| Average latency (ms) |
br-sao-sao01-a |
br-sao-sao04-a |
br-sao-sao05-a |
| br-sao-sao01-a |
0.09 |
1.64 |
2.7 |
| br-sao-sao04-a |
1.64 |
0.08 |
1.94 |
| br-sao-sao05-a |
2.7 |
1.94 |
0.1 |
23 Mar 2025
Inter-region latency
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
31 |
123 |
113 |
117 |
151 |
184 |
142 |
141 |
| Toronto |
34 |
|
19 |
92 |
83 |
105 |
171 |
213 |
162 |
132 |
| Washington DC |
31 |
19 |
|
87 |
76 |
88 |
176 |
214 |
171 |
119 |
| Frankfurt |
123 |
92 |
87 |
|
13 |
29 |
233 |
250 |
225 |
195 |
| London |
113 |
83 |
76 |
13 |
|
27 |
244 |
262 |
237 |
188 |
| Madrid |
117 |
105 |
87 |
29 |
27 |
|
259 |
276 |
251 |
208 |
| Osaka |
150 |
170 |
175 |
233 |
244 |
259 |
|
124 |
9 |
290 |
| Sydney |
184 |
215 |
214 |
250 |
262 |
277 |
123 |
|
117 |
324 |
| Tokyo |
143 |
163 |
167 |
225 |
237 |
251 |
9 |
117 |
|
282 |
| Sao Paulo |
141 |
131 |
122 |
199 |
191 |
205 |
289 |
325 |
283 |
|
Inter-AZ latency
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
us-south-dal10-a |
us-south-dal12-a |
us-south-dal13-a |
us-south-dal14-a |
| us-south-dal10-a |
0.09 |
1.77 |
1.91 |
2.16 |
| us-south-dal12-a |
1.77 |
0.1 |
1.89 |
2.14 |
| us-south-dal13-a |
1.91 |
1.89 |
0.1 |
2.3 |
| us-south-dal14-a |
2.16 |
2.14 |
2.3 |
0.1 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
ca-tor-tor01-a |
ca-tor-tor04-a |
ca-tor-tor05-a |
| ca-tor-tor01-a |
0.1 |
1.52 |
1.73 |
| ca-tor-tor04-a |
1.52 |
0.09 |
1.7 |
| ca-tor-tor05-a |
1.73 |
1.7 |
0.1 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
us-east-wdc04-a |
us-east-wdc06-a |
us-east-wdc07-a |
| us-east-wdc04-a |
0.09 |
0.65 |
0.65 |
| us-east-wdc06-a |
0.65 |
0.11 |
0.59 |
| us-east-wdc07-a |
0.65 |
0.59 |
0.08 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
eu-de-fra02-a |
eu-de-fra04-a |
eu-de-fra05-a |
| eu-de-fra02-a |
0.11 |
0.74 |
0.66 |
| eu-de-fra04-a |
0.74 |
0.11 |
0.66 |
| eu-de-fra05-a |
0.66 |
0.66 |
0.12 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
eu-gb-lon04-a |
eu-gb-lon05-a |
eu-gb-lon06-a |
| eu-gb-lon04-a |
0.08 |
2.18 |
2.04 |
| eu-gb-lon05-a |
2.18 |
0.08 |
1.72 |
| eu-gb-lon06-a |
2.04 |
1.72 |
0.09 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
eu-es-mad02-a |
eu-es-mad04-a |
eu-es-mad05-a |
| eu-es-mad02-a |
0.09 |
0.67 |
0.61 |
| eu-es-mad04-a |
0.67 |
0.11 |
0.8 |
| eu-es-mad05-a |
0.61 |
0.8 |
0.09 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
jp-osa-osa21-a |
jp-osa-osa22-a |
jp-osa-osa23-a |
| jp-osa-osa21-a |
0.1 |
1.48 |
1.42 |
| jp-osa-osa22-a |
1.48 |
0.1 |
1.46 |
| jp-osa-osa23-a |
1.42 |
1.46 |
0.1 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
au-syd-syd01-a |
au-syd-syd04-a |
au-syd-syd05-a |
| au-syd-syd01-a |
0.09 |
1.61 |
0.93 |
| au-syd-syd04-a |
1.61 |
0.09 |
1.8 |
| au-syd-syd05-a |
0.93 |
1.8 |
0.1 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
jp-tok-tok02-a |
jp-tok-tok04-a |
jp-tok-tok05-a |
| jp-tok-tok02-a |
0.1 |
1.45 |
0.97 |
| jp-tok-tok04-a |
1.45 |
0.1 |
1.68 |
| jp-tok-tok05-a |
0.97 |
1.68 |
0.1 |
22 Feb 2025–23 Mar 2025
| Average latency (ms) |
br-sao-sao01-a |
br-sao-sao04-a |
br-sao-sao05-a |
| br-sao-sao01-a |
0.09 |
1.64 |
2.7 |
| br-sao-sao04-a |
1.64 |
0.08 |
1.93 |
| br-sao-sao05-a |
2.7 |
1.93 |
0.1 |
16 Mar 2025
Inter-region latency
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
31 |
124 |
115 |
116 |
150 |
184 |
142 |
140 |
| Toronto |
34 |
|
19 |
95 |
86 |
106 |
173 |
214 |
163 |
137 |
| Washington DC |
31 |
19 |
|
89 |
78 |
88 |
176 |
213 |
171 |
118 |
| Frankfurt |
124 |
95 |
89 |
|
13 |
29 |
232 |
250 |
225 |
201 |
| London |
117 |
87 |
78 |
13 |
|
27 |
244 |
262 |
237 |
197 |
| Madrid |
118 |
106 |
86 |
29 |
27 |
|
259 |
276 |
251 |
206 |
| Osaka |
150 |
170 |
175 |
232 |
244 |
259 |
|
123 |
9 |
290 |
| Sydney |
185 |
215 |
214 |
250 |
262 |
277 |
123 |
|
116 |
323 |
| Tokyo |
142 |
162 |
168 |
225 |
236 |
251 |
9 |
117 |
|
282 |
| Sao Paulo |
141 |
138 |
117 |
204 |
197 |
206 |
288 |
325 |
283 |
|
Inter-AZ latency
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
us-south-dal10-a |
us-south-dal12-a |
us-south-dal13-a |
us-south-dal14-a |
| us-south-dal10-a |
0.09 |
1.78 |
1.91 |
2.15 |
| us-south-dal12-a |
1.78 |
0.1 |
1.9 |
2.13 |
| us-south-dal13-a |
1.91 |
1.9 |
0.1 |
2.3 |
| us-south-dal14-a |
2.15 |
2.13 |
2.3 |
0.1 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
ca-tor-tor01-a |
ca-tor-tor04-a |
ca-tor-tor05-a |
| ca-tor-tor01-a |
0.1 |
1.51 |
1.73 |
| ca-tor-tor04-a |
1.51 |
0.1 |
1.71 |
| ca-tor-tor05-a |
1.73 |
1.71 |
0.1 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
us-east-wdc04-a |
us-east-wdc06-a |
us-east-wdc07-a |
| us-east-wdc04-a |
0.09 |
0.65 |
0.65 |
| us-east-wdc06-a |
0.65 |
0.11 |
0.57 |
| us-east-wdc07-a |
0.65 |
0.57 |
0.08 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
eu-de-fra02-a |
eu-de-fra04-a |
eu-de-fra05-a |
| eu-de-fra02-a |
0.1 |
0.74 |
0.66 |
| eu-de-fra04-a |
0.74 |
0.11 |
0.66 |
| eu-de-fra05-a |
0.66 |
0.66 |
0.12 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
eu-gb-lon04-a |
eu-gb-lon05-a |
eu-gb-lon06-a |
| eu-gb-lon04-a |
0.08 |
2.17 |
2.02 |
| eu-gb-lon05-a |
2.17 |
0.08 |
1.8 |
| eu-gb-lon06-a |
2.02 |
1.8 |
0.09 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
eu-es-mad02-a |
eu-es-mad04-a |
eu-es-mad05-a |
| eu-es-mad02-a |
0.1 |
0.67 |
0.61 |
| eu-es-mad04-a |
0.67 |
0.11 |
0.79 |
| eu-es-mad05-a |
0.61 |
0.79 |
0.1 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
jp-osa-osa21-a |
jp-osa-osa22-a |
jp-osa-osa23-a |
| jp-osa-osa21-a |
0.09 |
1.45 |
1.42 |
| jp-osa-osa22-a |
1.45 |
0.1 |
1.44 |
| jp-osa-osa23-a |
1.42 |
1.44 |
0.1 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
au-syd-syd01-a |
au-syd-syd04-a |
au-syd-syd05-a |
| au-syd-syd01-a |
0.09 |
1.61 |
0.9 |
| au-syd-syd04-a |
1.61 |
0.09 |
1.8 |
| au-syd-syd05-a |
0.9 |
1.8 |
0.1 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
jp-tok-tok02-a |
jp-tok-tok04-a |
jp-tok-tok05-a |
| jp-tok-tok02-a |
0.1 |
1.47 |
0.97 |
| jp-tok-tok04-a |
1.47 |
0.1 |
1.69 |
| jp-tok-tok05-a |
0.97 |
1.69 |
0.1 |
15 Feb 2025–16 Mar 2025
| Average latency (ms) |
br-sao-sao01-a |
br-sao-sao04-a |
br-sao-sao05-a |
| br-sao-sao01-a |
0.09 |
1.65 |
2.67 |
| br-sao-sao04-a |
1.65 |
0.08 |
1.93 |
| br-sao-sao05-a |
2.67 |
1.93 |
0.1 |
9 Mar 2025
Inter-region latency
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
35 |
31 |
124 |
118 |
116 |
150 |
185 |
142 |
140 |
| Toronto |
34 |
|
19 |
99 |
93 |
106 |
172 |
213 |
163 |
137 |
| Washington DC |
31 |
19 |
|
90 |
82 |
89 |
176 |
213 |
170 |
119 |
| Frankfurt |
125 |
99 |
90 |
|
13 |
29 |
232 |
250 |
225 |
204 |
| London |
119 |
93 |
82 |
13 |
|
27 |
244 |
262 |
236 |
200 |
| Madrid |
118 |
104 |
86 |
29 |
27 |
|
259 |
276 |
251 |
205 |
| Osaka |
150 |
169 |
174 |
233 |
244 |
259 |
|
123 |
9 |
289 |
| Sydney |
185 |
215 |
212 |
250 |
262 |
276 |
122 |
|
116 |
324 |
| Tokyo |
143 |
163 |
168 |
225 |
236 |
251 |
9 |
116 |
|
282 |
| Sao Paulo |
141 |
143 |
118 |
204 |
201 |
207 |
288 |
325 |
283 |
|
Inter-AZ latency
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
us-south-dal10-a |
us-south-dal12-a |
us-south-dal13-a |
us-south-dal14-a |
| us-south-dal10-a |
0.09 |
1.77 |
1.91 |
2.14 |
| us-south-dal12-a |
1.77 |
0.1 |
1.92 |
2.12 |
| us-south-dal13-a |
1.91 |
1.92 |
0.09 |
2.28 |
| us-south-dal14-a |
2.14 |
2.12 |
2.28 |
0.09 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
ca-tor-tor01-a |
ca-tor-tor04-a |
ca-tor-tor05-a |
| ca-tor-tor01-a |
0.1 |
1.52 |
1.74 |
| ca-tor-tor04-a |
1.52 |
0.09 |
1.71 |
| ca-tor-tor05-a |
1.74 |
1.71 |
0.1 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
us-east-wdc04-a |
us-east-wdc06-a |
us-east-wdc07-a |
| us-east-wdc04-a |
0.09 |
0.65 |
0.66 |
| us-east-wdc06-a |
0.65 |
0.11 |
0.59 |
| us-east-wdc07-a |
0.66 |
0.59 |
0.08 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
eu-de-fra02-a |
eu-de-fra04-a |
eu-de-fra05-a |
| eu-de-fra02-a |
0.1 |
0.75 |
0.67 |
| eu-de-fra04-a |
0.75 |
0.1 |
0.68 |
| eu-de-fra05-a |
0.67 |
0.68 |
0.13 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
eu-gb-lon04-a |
eu-gb-lon05-a |
eu-gb-lon06-a |
| eu-gb-lon04-a |
0.08 |
2.19 |
1.99 |
| eu-gb-lon05-a |
2.19 |
0.08 |
1.83 |
| eu-gb-lon06-a |
1.99 |
1.83 |
0.09 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
eu-es-mad02-a |
eu-es-mad04-a |
eu-es-mad05-a |
| eu-es-mad02-a |
0.1 |
0.67 |
0.61 |
| eu-es-mad04-a |
0.67 |
0.11 |
0.8 |
| eu-es-mad05-a |
0.61 |
0.8 |
0.1 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
jp-osa-osa21-a |
jp-osa-osa22-a |
jp-osa-osa23-a |
| jp-osa-osa21-a |
0.09 |
1.45 |
1.44 |
| jp-osa-osa22-a |
1.45 |
0.1 |
1.44 |
| jp-osa-osa23-a |
1.44 |
1.44 |
0.1 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
au-syd-syd01-a |
au-syd-syd04-a |
au-syd-syd05-a |
| au-syd-syd01-a |
0.09 |
1.61 |
0.89 |
| au-syd-syd04-a |
1.61 |
0.09 |
1.81 |
| au-syd-syd05-a |
0.89 |
1.81 |
0.1 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
jp-tok-tok02-a |
jp-tok-tok04-a |
jp-tok-tok05-a |
| jp-tok-tok02-a |
0.1 |
1.48 |
0.98 |
| jp-tok-tok04-a |
1.48 |
0.11 |
1.69 |
| jp-tok-tok05-a |
0.98 |
1.69 |
0.1 |
8 Feb 2025–9 Mar 2025
| Average latency (ms) |
br-sao-sao01-a |
br-sao-sao04-a |
br-sao-sao05-a |
| br-sao-sao01-a |
0.09 |
1.68 |
2.65 |
| br-sao-sao04-a |
1.68 |
0.09 |
1.94 |
| br-sao-sao05-a |
2.65 |
1.94 |
0.1 |
2 Mar 2025
Inter-region latency
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
31 |
124 |
119 |
117 |
151 |
184 |
142 |
140 |
| Toronto |
34 |
|
20 |
100 |
94 |
106 |
172 |
214 |
163 |
134 |
| Washington DC |
31 |
19 |
|
91 |
84 |
89 |
176 |
212 |
168 |
119 |
| Frankfurt |
125 |
101 |
90 |
|
13 |
29 |
232 |
250 |
225 |
206 |
| London |
119 |
97 |
84 |
13 |
|
27 |
243 |
261 |
236 |
201 |
| Madrid |
118 |
105 |
87 |
29 |
27 |
|
259 |
276 |
250 |
205 |
| Osaka |
150 |
170 |
176 |
233 |
244 |
259 |
|
123 |
9 |
289 |
| Sydney |
185 |
214 |
210 |
250 |
262 |
277 |
122 |
|
115 |
323 |
| Tokyo |
142 |
165 |
169 |
225 |
236 |
250 |
9 |
115 |
|
282 |
| Sao Paulo |
142 |
140 |
118 |
206 |
199 |
206 |
288 |
326 |
283 |
|
Inter-AZ latency
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
us-south-dal10-a |
us-south-dal12-a |
us-south-dal13-a |
us-south-dal14-a |
| us-south-dal10-a |
0.09 |
1.75 |
1.93 |
2.14 |
| us-south-dal12-a |
1.75 |
0.1 |
1.93 |
2.14 |
| us-south-dal13-a |
1.93 |
1.93 |
0.09 |
2.28 |
| us-south-dal14-a |
2.14 |
2.14 |
2.28 |
0.09 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
ca-tor-tor01-a |
ca-tor-tor04-a |
ca-tor-tor05-a |
| ca-tor-tor01-a |
0.1 |
1.53 |
1.74 |
| ca-tor-tor04-a |
1.53 |
0.09 |
1.72 |
| ca-tor-tor05-a |
1.74 |
1.72 |
0.1 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
us-east-wdc04-a |
us-east-wdc06-a |
us-east-wdc07-a |
| us-east-wdc04-a |
0.09 |
0.67 |
0.66 |
| us-east-wdc06-a |
0.67 |
0.11 |
0.6 |
| us-east-wdc07-a |
0.66 |
0.6 |
0.08 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
eu-de-fra02-a |
eu-de-fra04-a |
eu-de-fra05-a |
| eu-de-fra02-a |
0.1 |
0.75 |
0.67 |
| eu-de-fra04-a |
0.75 |
0.1 |
0.67 |
| eu-de-fra05-a |
0.67 |
0.67 |
0.12 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
eu-gb-lon04-a |
eu-gb-lon05-a |
eu-gb-lon06-a |
| eu-gb-lon04-a |
0.08 |
2.18 |
1.98 |
| eu-gb-lon05-a |
2.18 |
0.09 |
1.79 |
| eu-gb-lon06-a |
1.98 |
1.79 |
0.09 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
eu-es-mad02-a |
eu-es-mad04-a |
eu-es-mad05-a |
| eu-es-mad02-a |
0.1 |
0.67 |
0.61 |
| eu-es-mad04-a |
0.67 |
0.12 |
0.8 |
| eu-es-mad05-a |
0.61 |
0.8 |
0.1 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
jp-osa-osa21-a |
jp-osa-osa22-a |
jp-osa-osa23-a |
| jp-osa-osa21-a |
0.09 |
1.44 |
1.48 |
| jp-osa-osa22-a |
1.44 |
0.1 |
1.44 |
| jp-osa-osa23-a |
1.48 |
1.44 |
0.1 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
au-syd-syd01-a |
au-syd-syd04-a |
au-syd-syd05-a |
| au-syd-syd01-a |
0.1 |
1.61 |
0.88 |
| au-syd-syd04-a |
1.61 |
0.09 |
1.8 |
| au-syd-syd05-a |
0.88 |
1.8 |
0.1 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
jp-tok-tok02-a |
jp-tok-tok04-a |
jp-tok-tok05-a |
| jp-tok-tok02-a |
0.1 |
1.49 |
0.97 |
| jp-tok-tok04-a |
1.49 |
0.11 |
1.68 |
| jp-tok-tok05-a |
0.97 |
1.68 |
0.1 |
1 Feb 2025–2 Mar 2025
| Average latency (ms) |
br-sao-sao01-a |
br-sao-sao04-a |
br-sao-sao05-a |
| br-sao-sao01-a |
0.09 |
1.71 |
2.65 |
| br-sao-sao04-a |
1.71 |
0.09 |
1.94 |
| br-sao-sao05-a |
2.65 |
1.94 |
0.1 |