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 between availability zones 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 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.
21 Apr 2024
Inter-region latency
Table 1. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
31 |
123 |
112 |
120 |
150 |
184 |
142 |
145 |
| Toronto |
34 |
|
19 |
93 |
84 |
109 |
169 |
215 |
161 |
128 |
| Washington DC |
31 |
19 |
|
98 |
77 |
89 |
174 |
215 |
168 |
121 |
| Frankfurt |
123 |
92 |
98 |
|
12 |
29 |
233 |
250 |
225 |
198 |
| London |
113 |
84 |
77 |
12 |
|
26 |
244 |
261 |
236 |
188 |
| Madrid |
119 |
107 |
88 |
29 |
27 |
|
257 |
274 |
251 |
209 |
| Osaka |
150 |
170 |
175 |
232 |
244 |
257 |
|
144 |
9 |
293 |
| Sydney |
184 |
215 |
215 |
250 |
263 |
275 |
144 |
|
136 |
328 |
| Tokyo |
142 |
162 |
167 |
225 |
237 |
250 |
9 |
131 |
|
286 |
| Sao Paulo |
145 |
132 |
122 |
196 |
187 |
205 |
293 |
327 |
284 |
|
Inter-AZ latency
Table 2. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
|
2.09 |
2.2 |
| Dallas 2 |
2.09 |
|
2.17 |
| Dallas 3 |
2.2 |
2.17 |
|
Table 3. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
|
1.72 |
1.94 |
| Toronto 2 |
1.72 |
|
1.86 |
| Toronto 3 |
1.94 |
1.86 |
|
Table 4. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
|
0.83 |
0.89 |
| Washington DC 2 |
0.83 |
|
0.83 |
| Washington DC 3 |
0.89 |
0.83 |
|
Table 5. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
|
0.89 |
0.8 |
| Frankfurt 2 |
0.89 |
|
0.8 |
| Frankfurt 3 |
0.8 |
0.8 |
|
Table 6. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
|
2.39 |
1.97 |
| London 2 |
2.39 |
|
2.13 |
| London 3 |
1.97 |
2.13 |
|
Table 7. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
|
0.68 |
0.63 |
| Madrid 2 |
0.68 |
|
0.79 |
| Madrid 3 |
0.63 |
0.79 |
|
Table 8. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
|
1.67 |
1.67 |
| Osaka 2 |
1.67 |
|
1.66 |
| Osaka 3 |
1.67 |
1.66 |
|
Table 9. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
|
1.94 |
1.18 |
| Sydney 2 |
1.94 |
|
2.01 |
| Sydney 3 |
1.18 |
2.01 |
|
Table 10. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
|
1.72 |
1.52 |
| Tokyo 2 |
1.72 |
|
1.94 |
| Tokyo 3 |
1.52 |
1.94 |
|
Table 11. 23 Mar 2024–21 Apr 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
|
1.96 |
2.87 |
| Sao Paulo 2 |
1.96 |
|
2.13 |
| Sao Paulo 3 |
2.87 |
2.13 |
|
14 Apr 2024
Inter-region latency
Table 12. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
31 |
124 |
112 |
118 |
150 |
185 |
142 |
145 |
| Toronto |
34 |
|
19 |
93 |
84 |
108 |
168 |
215 |
162 |
128 |
| Washington DC |
31 |
19 |
|
98 |
76 |
89 |
174 |
215 |
167 |
120 |
| Frankfurt |
123 |
93 |
98 |
|
12 |
29 |
234 |
250 |
226 |
198 |
| London |
113 |
84 |
76 |
12 |
|
26 |
245 |
261 |
238 |
187 |
| Madrid |
118 |
107 |
88 |
29 |
26 |
|
259 |
275 |
252 |
209 |
| Osaka |
150 |
170 |
174 |
234 |
245 |
258 |
|
148 |
9 |
293 |
| Sydney |
184 |
215 |
215 |
250 |
262 |
275 |
146 |
|
139 |
328 |
| Tokyo |
143 |
163 |
167 |
226 |
238 |
252 |
9 |
137 |
|
286 |
| Sao Paulo |
146 |
132 |
121 |
196 |
186 |
206 |
293 |
328 |
285 |
|
Inter-AZ latency
Table 13. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
|
2.04 |
2.14 |
| Dallas 2 |
2.04 |
|
2.14 |
| Dallas 3 |
2.14 |
2.14 |
|
Table 14. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
|
1.73 |
1.92 |
| Toronto 2 |
1.73 |
|
1.86 |
| Toronto 3 |
1.92 |
1.86 |
|
Table 15. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
|
0.85 |
0.89 |
| Washington DC 2 |
0.85 |
|
0.83 |
| Washington DC 3 |
0.89 |
0.83 |
|
Table 16. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
|
0.89 |
0.82 |
| Frankfurt 2 |
0.89 |
|
0.79 |
| Frankfurt 3 |
0.82 |
0.79 |
|
Table 17. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
|
2.4 |
1.95 |
| London 2 |
2.4 |
|
2.07 |
| London 3 |
1.95 |
2.07 |
|
Table 18. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
|
0.68 |
0.63 |
| Madrid 2 |
0.68 |
|
0.79 |
| Madrid 3 |
0.63 |
0.79 |
|
Table 19. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
|
1.67 |
1.66 |
| Osaka 2 |
1.67 |
|
1.66 |
| Osaka 3 |
1.66 |
1.66 |
|
Table 20. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
|
1.95 |
1.11 |
| Sydney 2 |
1.95 |
|
2.02 |
| Sydney 3 |
1.11 |
2.02 |
|
Table 21. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
|
1.7 |
1.54 |
| Tokyo 2 |
1.7 |
|
1.95 |
| Tokyo 3 |
1.54 |
1.95 |
|
Table 22. 16 Mar 2024–14 Apr 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
|
1.96 |
2.88 |
| Sao Paulo 2 |
1.96 |
|
2.13 |
| Sao Paulo 3 |
2.88 |
2.13 |
|
7 Apr 2024
Inter-region latency
Table 23. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
124 |
112 |
119 |
150 |
185 |
142 |
145 |
| Toronto |
34 |
|
19 |
93 |
84 |
108 |
168 |
215 |
161 |
128 |
| Washington DC |
31 |
19 |
|
97 |
76 |
88 |
173 |
215 |
166 |
120 |
| Frankfurt |
123 |
93 |
98 |
|
12 |
29 |
236 |
250 |
228 |
197 |
| London |
113 |
84 |
76 |
12 |
|
26 |
247 |
261 |
240 |
187 |
| Madrid |
118 |
107 |
88 |
29 |
26 |
|
261 |
275 |
254 |
208 |
| Osaka |
150 |
170 |
174 |
237 |
247 |
261 |
|
149 |
9 |
293 |
| Sydney |
184 |
215 |
215 |
250 |
262 |
275 |
144 |
|
138 |
328 |
| Tokyo |
143 |
163 |
168 |
229 |
240 |
254 |
9 |
138 |
|
286 |
| Sao Paulo |
146 |
131 |
121 |
196 |
186 |
207 |
293 |
329 |
285 |
|
Inter-AZ latency
Table 24. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
|
2.04 |
2.12 |
| Dallas 2 |
2.04 |
|
2.12 |
| Dallas 3 |
2.12 |
2.12 |
|
Table 25. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
|
1.73 |
1.92 |
| Toronto 2 |
1.73 |
|
1.85 |
| Toronto 3 |
1.92 |
1.85 |
|
Table 26. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
|
0.85 |
0.89 |
| Washington DC 2 |
0.85 |
|
0.84 |
| Washington DC 3 |
0.89 |
0.84 |
|
Table 27. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
|
0.9 |
0.82 |
| Frankfurt 2 |
0.9 |
|
0.8 |
| Frankfurt 3 |
0.82 |
0.8 |
|
Table 28. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
|
2.4 |
1.89 |
| London 2 |
2.4 |
|
2.1 |
| London 3 |
1.89 |
2.1 |
|
Table 29. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
|
0.68 |
0.63 |
| Madrid 2 |
0.68 |
|
0.79 |
| Madrid 3 |
0.63 |
0.79 |
|
Table 30. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
|
1.67 |
1.66 |
| Osaka 2 |
1.67 |
|
1.66 |
| Osaka 3 |
1.66 |
1.66 |
|
Table 31. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
|
1.95 |
1.1 |
| Sydney 2 |
1.95 |
|
2.0 |
| Sydney 3 |
1.1 |
2.0 |
|
Table 32. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
|
1.7 |
1.51 |
| Tokyo 2 |
1.7 |
|
1.96 |
| Tokyo 3 |
1.51 |
1.96 |
|
Table 33. 9 Mar 2024–7 Apr 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
|
1.97 |
2.89 |
| Sao Paulo 2 |
1.97 |
|
2.12 |
| Sao Paulo 3 |
2.89 |
2.12 |
|
31 Mar 2024
Inter-region latency
Table 34. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
124 |
112 |
118 |
150 |
185 |
142 |
146 |
| Toronto |
34 |
|
19 |
93 |
84 |
107 |
168 |
215 |
162 |
129 |
| Washington DC |
31 |
19 |
|
97 |
76 |
87 |
173 |
215 |
166 |
120 |
| Frankfurt |
123 |
93 |
98 |
|
12 |
29 |
238 |
254 |
231 |
197 |
| London |
114 |
84 |
76 |
12 |
|
26 |
250 |
266 |
243 |
186 |
| Madrid |
119 |
108 |
89 |
29 |
26 |
|
264 |
281 |
256 |
208 |
| Osaka |
150 |
169 |
174 |
239 |
249 |
263 |
|
146 |
9 |
293 |
| Sydney |
184 |
213 |
215 |
254 |
266 |
279 |
144 |
|
137 |
327 |
| Tokyo |
143 |
163 |
168 |
231 |
243 |
256 |
9 |
140 |
|
286 |
| Sao Paulo |
146 |
131 |
121 |
195 |
186 |
209 |
293 |
329 |
286 |
|
Inter-AZ latency
Table 35. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
|
2.04 |
2.13 |
| Dallas 2 |
2.04 |
|
2.1 |
| Dallas 3 |
2.13 |
2.1 |
|
Table 36. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
|
1.75 |
1.93 |
| Toronto 2 |
1.75 |
|
1.84 |
| Toronto 3 |
1.93 |
1.84 |
|
Table 37. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
|
0.85 |
0.91 |
| Washington DC 2 |
0.85 |
|
0.82 |
| Washington DC 3 |
0.91 |
0.82 |
|
Table 38. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
|
0.89 |
0.83 |
| Frankfurt 2 |
0.89 |
|
0.8 |
| Frankfurt 3 |
0.83 |
0.8 |
|
Table 39. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
|
2.37 |
1.93 |
| London 2 |
2.37 |
|
2.07 |
| London 3 |
1.93 |
2.07 |
|
Table 40. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
|
0.67 |
0.63 |
| Madrid 2 |
0.67 |
|
0.79 |
| Madrid 3 |
0.63 |
0.79 |
|
Table 41. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
|
1.67 |
1.66 |
| Osaka 2 |
1.67 |
|
1.66 |
| Osaka 3 |
1.66 |
1.66 |
|
Table 42. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
|
1.95 |
1.1 |
| Sydney 2 |
1.95 |
|
1.98 |
| Sydney 3 |
1.1 |
1.98 |
|
Table 43. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
|
1.7 |
1.5 |
| Tokyo 2 |
1.7 |
|
1.95 |
| Tokyo 3 |
1.5 |
1.95 |
|
Table 44. 2 Mar 2024–31 Mar 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
|
1.97 |
2.85 |
| Sao Paulo 2 |
1.97 |
|
2.12 |
| Sao Paulo 3 |
2.85 |
2.12 |
|
24 Mar 2024
Inter-region latency
Table 45. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Dallas |
Toronto |
Washington DC |
Frankfurt |
London |
Madrid |
Osaka |
Sydney |
Tokyo |
Sao Paulo |
| Dallas |
|
34 |
32 |
124 |
112 |
117 |
149 |
184 |
142 |
144 |
| Toronto |
35 |
|
19 |
93 |
84 |
107 |
169 |
215 |
163 |
130 |
| Washington DC |
31 |
19 |
|
97 |
76 |
88 |
173 |
215 |
166 |
120 |
| Frankfurt |
123 |
93 |
98 |
|
12 |
29 |
240 |
261 |
235 |
196 |
| London |
114 |
83 |
76 |
12 |
|
26 |
253 |
271 |
245 |
186 |
| Madrid |
119 |
109 |
88 |
29 |
26 |
|
266 |
283 |
258 |
207 |
| Osaka |
150 |
169 |
173 |
243 |
252 |
266 |
|
135 |
9 |
293 |
| Sydney |
185 |
213 |
215 |
260 |
271 |
285 |
134 |
|
126 |
328 |
| Tokyo |
143 |
163 |
168 |
236 |
245 |
258 |
9 |
128 |
|
286 |
| Sao Paulo |
145 |
131 |
122 |
196 |
187 |
211 |
293 |
327 |
285 |
|
Inter-AZ latency
Table 46. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Dallas 1 |
Dallas 2 |
Dallas 3 |
| Dallas 1 |
|
2.06 |
2.14 |
| Dallas 2 |
2.06 |
|
2.09 |
| Dallas 3 |
2.14 |
2.09 |
|
Table 47. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Toronto 1 |
Toronto 2 |
Toronto 3 |
| Toronto 1 |
|
1.75 |
1.92 |
| Toronto 2 |
1.75 |
|
1.85 |
| Toronto 3 |
1.92 |
1.85 |
|
Table 48. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Washington DC 1 |
Washington DC 2 |
Washington DC 3 |
| Washington DC 1 |
|
0.88 |
0.91 |
| Washington DC 2 |
0.88 |
|
0.83 |
| Washington DC 3 |
0.91 |
0.83 |
|
Table 49. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Frankfurt 1 |
Frankfurt 2 |
Frankfurt 3 |
| Frankfurt 1 |
|
0.89 |
0.82 |
| Frankfurt 2 |
0.89 |
|
0.8 |
| Frankfurt 3 |
0.82 |
0.8 |
|
Table 50. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
London 1 |
London 2 |
London 3 |
| London 1 |
|
2.38 |
1.91 |
| London 2 |
2.38 |
|
2.05 |
| London 3 |
1.91 |
2.05 |
|
Table 51. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Madrid 1 |
Madrid 2 |
Madrid 3 |
| Madrid 1 |
|
0.67 |
0.63 |
| Madrid 2 |
0.67 |
|
0.79 |
| Madrid 3 |
0.63 |
0.79 |
|
Table 52. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Osaka 1 |
Osaka 2 |
Osaka 3 |
| Osaka 1 |
|
1.67 |
1.66 |
| Osaka 2 |
1.67 |
|
1.66 |
| Osaka 3 |
1.66 |
1.66 |
|
Table 53. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Sydney 1 |
Sydney 2 |
Sydney 3 |
| Sydney 1 |
|
1.94 |
1.14 |
| Sydney 2 |
1.94 |
|
2.03 |
| Sydney 3 |
1.14 |
2.03 |
|
Table 54. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Tokyo 1 |
Tokyo 2 |
Tokyo 3 |
| Tokyo 1 |
|
1.7 |
1.5 |
| Tokyo 2 |
1.7 |
|
1.93 |
| Tokyo 3 |
1.5 |
1.93 |
|
Table 55. 24 Feb 2024–24 Mar 2024
| Average latency (ms) |
Sao Paulo 1 |
Sao Paulo 2 |
Sao Paulo 3 |
| Sao Paulo 1 |
|
1.97 |
2.83 |
| Sao Paulo 2 |
1.97 |
|
2.12 |
| Sao Paulo 3 |
2.83 |
2.12 |
|