---
name: vpc-about-network-latency
title: Network latency dashboards
description: 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.
last-updated: 2026-08-31
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vpc?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Network latency dashboards
{: #network-latency-dashboard}

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](https://cloud.ibm.com/docs/overview?topic=overview-locations&format=markdown#zone-mapping).
{: note}



## 30 Aug 2026
{: #network-latency-2026-08-30}

### Inter-region latency
{: #network-latency-2026-08-30-mzr}
| Average latency (ms) | Dallas | Toronto | Washington DC | Frankfurt | London | Madrid | Montreal | Chennai | Mumbai | Osaka | Sydney | Tokyo | Sao Paulo |
| --- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
| **Dallas** |   | 34 | 32 | 123 | 113 | 120 | 43 | 251 | 249 | 151 | 185 | 143 | 142 |
| **Toronto** |  35 |  | 19 | 93 | 83 | 108 | 10 | 222 | 200 | 142 | 215 | 135 | 125 |
| **Washington DC** |  31 | 19 |  | 87 | 76 | 90 | 16 | 241 | 219 | 147 | 215 | 140 | 123 |
| **Frankfurt** |  123 | 92 | 86 |  | 13 | 29 | 89 | 141 | 118 | 232 | 248 | 224 | 190 |
| **London** |  113 | 82 | 76 | 13 |  | 25 | 79 | 144 | 117 | 244 | 260 | 236 | 181 |
| **Madrid** |  118 | 107 | 87 | 29 | 26 |  | 105 | 154 | 129 | 258 | 274 | 251 | 208 |
| **Montreal** |  43 | 10 | 16 | 89 | 79 | 106 |  | 219 | 196 | 152 | 223 | 145 | 122 |
| **Chennai** |  254 | 223 | 242 | 143 | 141 | 155 | 221 |  | 24 | 110 | 126 | 102 | 358 |
| **Mumbai** |  246 | 198 | 219 | 119 | 119 | 130 | 195 | 23 |  | 136 | 152 | 128 | 341 |
| **Osaka** |  151 | 142 | 147 | 232 | 244 | 258 | 150 | 110 | 136 |  | 108 | 9 | 290 |
| **Sydney** |  186 | 214 | 214 | 248 | 260 | 274 | 222 | 126 | 152 | 108 |  | 101 | 327 |
| **Tokyo** |  144 | 135 | 140 | 224 | 236 | 251 | 143 | 102 | 128 | 9 | 101 |  | 282 |
| **Sao Paulo** |  142 | 124 | 123 | 192 | 181 | 211 | 122 | 365 | 340 | 291 | 325 | 283 |  |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}

### Inter-AZ latency
{: #network-latency-2026-08-30-az}

| Average latency (ms) | us-south-dal10-a | us-south-dal12-a | us-south-dal13-a | us-south-dal14-a |
| --- | :---: | :---: | :---: | :---: |
| **us-south-dal10-a** |  0.08 | 1.57 | 2.09 | 1.85 |
| **us-south-dal12-a** |  1.57 | 0.09 | 1.47 | 0.6 |
| **us-south-dal13-a** |  2.09 | 1.47 | 0.09 | 1.54 |
| **us-south-dal14-a** |  1.85 | 0.6 | 1.54 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-us-south}
{: tab-title="Dallas"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-tor-tor01-a | ca-tor-tor04-a | ca-tor-tor05-a |
| --- | :---: | :---: | :---: |
| **ca-tor-tor01-a** |  0.09 | 1.53 | 1.71 |
| **ca-tor-tor04-a** |  1.53 | 0.1 | 1.65 |
| **ca-tor-tor05-a** |  1.71 | 1.65 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-ca-tor}
{: tab-title="Toronto"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | us-east-wdc04-a | us-east-wdc06-a | us-east-wdc07-a |
| --- | :---: | :---: | :---: |
| **us-east-wdc04-a** |  0.09 | 0.69 | 0.76 |
| **us-east-wdc06-a** |  0.69 | 0.11 | 0.28 |
| **us-east-wdc07-a** |  0.76 | 0.28 | 0.08 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-us-east}
{: tab-title="Washington DC"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-de-fra02-a | eu-de-fra04-a | eu-de-fra05-a |
| --- | :---: | :---: | :---: |
| **eu-de-fra02-a** |  0.1 | 0.75 | 0.69 |
| **eu-de-fra04-a** |  0.75 | 0.1 | 0.46 |
| **eu-de-fra05-a** |  0.69 | 0.46 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-eu-de}
{: tab-title="Frankfurt"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-gb-lon04-a | eu-gb-lon05-a | eu-gb-lon06-a |
| --- | :---: | :---: | :---: |
| **eu-gb-lon04-a** |  0.09 | 1.39 | 0.74 |
| **eu-gb-lon05-a** |  1.39 | 0.08 | 0.68 |
| **eu-gb-lon06-a** |  0.74 | 0.68 | 0.08 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-eu-gb}
{: tab-title="London"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-es-mad02-a | eu-es-mad04-a | eu-es-mad05-a |
| --- | :---: | :---: | :---: |
| **eu-es-mad02-a** |  0.09 | 0.66 | 0.61 |
| **eu-es-mad04-a** |  0.66 | 0.1 | 0.78 |
| **eu-es-mad05-a** |  0.61 | 0.78 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-eu-es}
{: tab-title="Madrid"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-mon-mon04-a | ca-mon-mon04-b | ca-mon-mon04-c |
| --- | :---: | :---: | :---: |
| **ca-mon-mon04-a** |  0.07 | 0.13 | 0.13 |
| **ca-mon-mon04-b** |  0.13 | 0.07 | 0.13 |
| **ca-mon-mon04-c** |  0.13 | 0.13 | 0.08 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-ca-mon}
{: tab-title="Montreal"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | in-che-che02-a | in-che-che02-b | in-che-che02-c |
| --- | :---: | :---: | :---: |
| **in-che-che02-a** |  0.08 | 0.13 | 0.14 |
| **in-che-che02-b** |  0.13 | 0.08 | 0.14 |
| **in-che-che02-c** |  0.14 | 0.14 | 0.08 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-in-che}
{: tab-title="Chennai"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | in-mum-mum05-a | in-mum-mum02-a | in-mum-mum03-a |
| --- | :---: | :---: | :---: |
| **in-mum-mum05-a** |  0.08 | 0.28 | 0.74 |
| **in-mum-mum02-a** |  0.28 | 0.08 | 0.74 |
| **in-mum-mum03-a** |  0.74 | 0.74 | 0.08 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-in-mum}
{: tab-title="Mumbai"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-osa-osa21-a | jp-osa-osa22-a | jp-osa-osa23-a |
| --- | :---: | :---: | :---: |
| **jp-osa-osa21-a** |  0.1 | 1.4 | 1.38 |
| **jp-osa-osa22-a** |  1.4 | 0.1 | 1.39 |
| **jp-osa-osa23-a** |  1.38 | 1.39 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-jp-osa}
{: tab-title="Osaka"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | au-syd-syd01-a | au-syd-syd04-a | au-syd-syd05-a |
| --- | :---: | :---: | :---: |
| **au-syd-syd01-a** |  0.1 | 1.69 | 0.86 |
| **au-syd-syd04-a** |  1.69 | 0.1 | 1.75 |
| **au-syd-syd05-a** |  0.86 | 1.75 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-au-syd}
{: tab-title="Sydney"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-tok-tok02-a | jp-tok-tok04-a | jp-tok-tok05-a |
| --- | :---: | :---: | :---: |
| **jp-tok-tok02-a** |  0.1 | 1.49 | 0.98 |
| **jp-tok-tok04-a** |  1.49 | 0.1 | 1.63 |
| **jp-tok-tok05-a** |  0.98 | 1.63 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-jp-tok}
{: tab-title="Tokyo"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

| Average latency (ms) | br-sao-sao01-a | br-sao-sao04-a | br-sao-sao05-a |
| --- | :---: | :---: | :---: |
| **br-sao-sao01-a** |  0.1 | 1.58 | 0.53 |
| **br-sao-sao04-a** |  1.58 | 0.1 | 1.66 |
| **br-sao-sao05-a** |  0.53 | 1.66 | 0.1 |
{: caption="1 Aug 2026–30 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-30-br-sao}
{: tab-title="Sao Paulo"}
{: tab-group="network-latency-az-tabs-2026-08-30"}
{: class="simple-tab-table"}

## 23 Aug 2026
{: #network-latency-2026-08-23}

### Inter-region latency
{: #network-latency-2026-08-23-mzr}
| Average latency (ms) | Dallas | Toronto | Washington DC | Frankfurt | London | Madrid | Montreal | Chennai | Mumbai | Osaka | Sydney | Tokyo | Sao Paulo |
| --- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
| **Dallas** |   | 35 | 32 | 123 | 113 | 119 | 43 | 248 | 249 | 152 | 187 | 144 | 143 |
| **Toronto** |  35 |  | 19 | 93 | 83 | 108 | 11 | 223 | 201 | 142 | 216 | 135 | 125 |
| **Washington DC** |  31 | 19 |  | 87 | 76 | 89 | 16 | 240 | 218 | 147 | 215 | 142 | 122 |
| **Frankfurt** |  124 | 92 | 86 |  | 13 | 29 | 89 | 142 | 119 | 233 | 250 | 227 | 191 |
| **London** |  113 | 82 | 76 | 13 |  | 26 | 79 | 142 | 118 | 242 | 260 | 235 | 181 |
| **Madrid** |  119 | 109 | 86 | 29 | 25 |  | 104 | 155 | 130 | 257 | 275 | 250 | 210 |
| **Montreal** |  43 | 10 | 16 | 89 | 79 | 105 |  | 220 | 197 | 152 | 224 | 145 | 121 |
| **Chennai** |  248 | 222 | 245 | 143 | 141 | 154 | 220 |  | 24 | 110 | 126 | 102 | 361 |
| **Mumbai** |  247 | 201 | 219 | 119 | 121 | 128 | 196 | 24 |  | 136 | 152 | 128 | 337 |
| **Osaka** |  152 | 142 | 147 | 232 | 244 | 259 | 150 | 110 | 136 |  | 108 | 9 | 290 |
| **Sydney** |  187 | 216 | 215 | 248 | 260 | 274 | 222 | 126 | 152 | 108 |  | 101 | 327 |
| **Tokyo** |  145 | 135 | 139 | 224 | 236 | 251 | 143 | 102 | 128 | 9 | 101 |  | 285 |
| **Sao Paulo** |  142 | 124 | 123 | 192 | 180 | 213 | 122 | 366 | 341 | 290 | 326 | 283 |  |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}

### Inter-AZ latency
{: #network-latency-2026-08-23-az}

| Average latency (ms) | us-south-dal10-a | us-south-dal12-a | us-south-dal13-a | us-south-dal14-a |
| --- | :---: | :---: | :---: | :---: |
| **us-south-dal10-a** |  0.08 | 1.53 | 2.14 | 1.84 |
| **us-south-dal12-a** |  1.53 | 0.09 | 1.45 | 0.6 |
| **us-south-dal13-a** |  2.14 | 1.45 | 0.09 | 1.53 |
| **us-south-dal14-a** |  1.84 | 0.6 | 1.53 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-us-south}
{: tab-title="Dallas"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-tor-tor01-a | ca-tor-tor04-a | ca-tor-tor05-a |
| --- | :---: | :---: | :---: |
| **ca-tor-tor01-a** |  0.1 | 1.54 | 1.7 |
| **ca-tor-tor04-a** |  1.54 | 0.1 | 1.66 |
| **ca-tor-tor05-a** |  1.7 | 1.66 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-ca-tor}
{: tab-title="Toronto"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | us-east-wdc04-a | us-east-wdc06-a | us-east-wdc07-a |
| --- | :---: | :---: | :---: |
| **us-east-wdc04-a** |  0.09 | 0.69 | 0.76 |
| **us-east-wdc06-a** |  0.69 | 0.11 | 0.28 |
| **us-east-wdc07-a** |  0.76 | 0.28 | 0.08 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-us-east}
{: tab-title="Washington DC"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-de-fra02-a | eu-de-fra04-a | eu-de-fra05-a |
| --- | :---: | :---: | :---: |
| **eu-de-fra02-a** |  0.1 | 0.75 | 0.68 |
| **eu-de-fra04-a** |  0.75 | 0.1 | 0.46 |
| **eu-de-fra05-a** |  0.68 | 0.46 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-eu-de}
{: tab-title="Frankfurt"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-gb-lon04-a | eu-gb-lon05-a | eu-gb-lon06-a |
| --- | :---: | :---: | :---: |
| **eu-gb-lon04-a** |  0.09 | 1.39 | 0.74 |
| **eu-gb-lon05-a** |  1.39 | 0.08 | 0.68 |
| **eu-gb-lon06-a** |  0.74 | 0.68 | 0.08 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-eu-gb}
{: tab-title="London"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-es-mad02-a | eu-es-mad04-a | eu-es-mad05-a |
| --- | :---: | :---: | :---: |
| **eu-es-mad02-a** |  0.09 | 0.66 | 0.61 |
| **eu-es-mad04-a** |  0.66 | 0.1 | 0.78 |
| **eu-es-mad05-a** |  0.61 | 0.78 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-eu-es}
{: tab-title="Madrid"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-mon-mon04-a | ca-mon-mon04-b | ca-mon-mon04-c |
| --- | :---: | :---: | :---: |
| **ca-mon-mon04-a** |  0.07 | 0.13 | 0.13 |
| **ca-mon-mon04-b** |  0.13 | 0.07 | 0.13 |
| **ca-mon-mon04-c** |  0.13 | 0.13 | 0.07 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-ca-mon}
{: tab-title="Montreal"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | in-che-che02-a | in-che-che02-b | in-che-che02-c |
| --- | :---: | :---: | :---: |
| **in-che-che02-a** |  0.08 | 0.13 | 0.14 |
| **in-che-che02-b** |  0.13 | 0.08 | 0.14 |
| **in-che-che02-c** |  0.14 | 0.14 | 0.08 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-in-che}
{: tab-title="Chennai"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | in-mum-mum05-a | in-mum-mum02-a | in-mum-mum03-a |
| --- | :---: | :---: | :---: |
| **in-mum-mum05-a** |  0.08 | 0.27 | 0.74 |
| **in-mum-mum02-a** |  0.27 | 0.08 | 0.74 |
| **in-mum-mum03-a** |  0.74 | 0.74 | 0.08 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-in-mum}
{: tab-title="Mumbai"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-osa-osa21-a | jp-osa-osa22-a | jp-osa-osa23-a |
| --- | :---: | :---: | :---: |
| **jp-osa-osa21-a** |  0.1 | 1.4 | 1.38 |
| **jp-osa-osa22-a** |  1.4 | 0.1 | 1.38 |
| **jp-osa-osa23-a** |  1.38 | 1.38 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-jp-osa}
{: tab-title="Osaka"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | au-syd-syd01-a | au-syd-syd04-a | au-syd-syd05-a |
| --- | :---: | :---: | :---: |
| **au-syd-syd01-a** |  0.1 | 1.7 | 0.89 |
| **au-syd-syd04-a** |  1.7 | 0.1 | 1.76 |
| **au-syd-syd05-a** |  0.89 | 1.76 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-au-syd}
{: tab-title="Sydney"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-tok-tok02-a | jp-tok-tok04-a | jp-tok-tok05-a |
| --- | :---: | :---: | :---: |
| **jp-tok-tok02-a** |  0.1 | 1.5 | 0.99 |
| **jp-tok-tok04-a** |  1.5 | 0.1 | 1.64 |
| **jp-tok-tok05-a** |  0.99 | 1.64 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-jp-tok}
{: tab-title="Tokyo"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

| Average latency (ms) | br-sao-sao01-a | br-sao-sao04-a | br-sao-sao05-a |
| --- | :---: | :---: | :---: |
| **br-sao-sao01-a** |  0.1 | 1.58 | 0.54 |
| **br-sao-sao04-a** |  1.58 | 0.1 | 1.66 |
| **br-sao-sao05-a** |  0.54 | 1.66 | 0.1 |
{: caption="25 Jul 2026–23 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-23-br-sao}
{: tab-title="Sao Paulo"}
{: tab-group="network-latency-az-tabs-2026-08-23"}
{: class="simple-tab-table"}

## 16 Aug 2026
{: #network-latency-2026-08-16}

### Inter-region latency
{: #network-latency-2026-08-16-mzr}
| Average latency (ms) | Dallas | Toronto | Washington DC | Frankfurt | London | Madrid | Montreal | Chennai | Mumbai | Osaka | Sydney | Tokyo | Sao Paulo |
| --- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
| **Dallas** |   | 35 | 32 | 123 | 113 | 119 | 42 | 248 | 249 | 152 | 186 | 145 | 142 |
| **Toronto** |  34 |  | 19 | 93 | 83 | 108 | 11 | 223 | 200 | 142 | 216 | 135 | 126 |
| **Washington DC** |  31 | 19 |  | 86 | 76 | 89 | 15 | 240 | 218 | 147 | 215 | 142 | 122 |
| **Frankfurt** |  124 | 93 | 86 |  | 13 | 29 | 89 | 141 | 118 | 236 | 250 | 229 | 191 |
| **London** |  113 | 83 | 76 | 13 |  | 26 | 79 | 141 | 118 | 245 | 261 | 238 | 181 |
| **Madrid** |  118 | 110 | 88 | 29 | 26 |  | 104 | 154 | 130 | 259 | 276 | 253 | 215 |
| **Montreal** |  43 | 10 | 16 | 89 | 79 | 106 |  | 219 | 197 | 150 | 224 | 143 | 121 |
| **Chennai** |  248 | 221 | 244 | 141 | 140 | 152 | 219 |  | 24 | 112 | 126 | 105 | 363 |
| **Mumbai** |  248 | 201 | 219 | 121 | 120 | 129 | 196 | 24 |  | 139 | 152 | 132 | 343 |
| **Osaka** |  152 | 142 | 147 | 236 | 246 | 262 | 150 | 122 | 139 |  | 108 | 9 | 291 |
| **Sydney** |  187 | 214 | 216 | 249 | 260 | 275 | 222 | 126 | 152 | 108 |  | 101 | 327 |
| **Tokyo** |  145 | 135 | 139 | 228 | 239 | 253 | 143 | 104 | 131 | 9 | 101 |  | 284 |
| **Sao Paulo** |  141 | 125 | 124 | 192 | 181 | 211 | 123 | 369 | 338 | 289 | 325 | 283 |  |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}

### Inter-AZ latency
{: #network-latency-2026-08-16-az}

| Average latency (ms) | us-south-dal10-a | us-south-dal12-a | us-south-dal13-a | us-south-dal14-a |
| --- | :---: | :---: | :---: | :---: |
| **us-south-dal10-a** |  0.08 | 2.01 | 2.16 | 1.82 |
| **us-south-dal12-a** |  2.01 | 0.09 | 1.43 | 0.6 |
| **us-south-dal13-a** |  2.16 | 1.43 | 0.1 | 1.54 |
| **us-south-dal14-a** |  1.82 | 0.6 | 1.54 | 0.1 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-us-south}
{: tab-title="Dallas"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-tor-tor01-a | ca-tor-tor04-a | ca-tor-tor05-a |
| --- | :---: | :---: | :---: |
| **ca-tor-tor01-a** |  0.1 | 1.55 | 1.71 |
| **ca-tor-tor04-a** |  1.55 | 0.1 | 1.64 |
| **ca-tor-tor05-a** |  1.71 | 1.64 | 0.1 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-ca-tor}
{: tab-title="Toronto"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | us-east-wdc04-a | us-east-wdc06-a | us-east-wdc07-a |
| --- | :---: | :---: | :---: |
| **us-east-wdc04-a** |  0.09 | 0.69 | 0.74 |
| **us-east-wdc06-a** |  0.69 | 0.11 | 0.28 |
| **us-east-wdc07-a** |  0.74 | 0.28 | 0.08 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-us-east}
{: tab-title="Washington DC"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-de-fra02-a | eu-de-fra04-a | eu-de-fra05-a |
| --- | :---: | :---: | :---: |
| **eu-de-fra02-a** |  0.1 | 0.75 | 0.68 |
| **eu-de-fra04-a** |  0.75 | 0.1 | 0.46 |
| **eu-de-fra05-a** |  0.68 | 0.46 | 0.11 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-eu-de}
{: tab-title="Frankfurt"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-gb-lon04-a | eu-gb-lon05-a | eu-gb-lon06-a |
| --- | :---: | :---: | :---: |
| **eu-gb-lon04-a** |  0.09 | 1.39 | 0.74 |
| **eu-gb-lon05-a** |  1.39 | 0.08 | 0.67 |
| **eu-gb-lon06-a** |  0.74 | 0.67 | 0.08 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-eu-gb}
{: tab-title="London"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-es-mad02-a | eu-es-mad04-a | eu-es-mad05-a |
| --- | :---: | :---: | :---: |
| **eu-es-mad02-a** |  0.09 | 0.66 | 0.61 |
| **eu-es-mad04-a** |  0.66 | 0.1 | 0.77 |
| **eu-es-mad05-a** |  0.61 | 0.77 | 0.1 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-eu-es}
{: tab-title="Madrid"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-mon-mon04-a | ca-mon-mon04-b | ca-mon-mon04-c |
| --- | :---: | :---: | :---: |
| **ca-mon-mon04-a** |  0.07 | 0.13 | 0.13 |
| **ca-mon-mon04-b** |  0.13 | 0.07 | 0.13 |
| **ca-mon-mon04-c** |  0.13 | 0.13 | 0.08 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-ca-mon}
{: tab-title="Montreal"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | in-che-che02-a | in-che-che02-b | in-che-che02-c |
| --- | :---: | :---: | :---: |
| **in-che-che02-a** |  0.08 | 0.13 | 0.14 |
| **in-che-che02-b** |  0.13 | 0.08 | 0.14 |
| **in-che-che02-c** |  0.14 | 0.14 | 0.08 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-in-che}
{: tab-title="Chennai"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | in-mum-mum05-a | in-mum-mum02-a | in-mum-mum03-a |
| --- | :---: | :---: | :---: |
| **in-mum-mum05-a** |  0.08 | 0.27 | 0.74 |
| **in-mum-mum02-a** |  0.27 | 0.08 | 0.74 |
| **in-mum-mum03-a** |  0.74 | 0.74 | 0.08 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-in-mum}
{: tab-title="Mumbai"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-osa-osa21-a | jp-osa-osa22-a | jp-osa-osa23-a |
| --- | :---: | :---: | :---: |
| **jp-osa-osa21-a** |  0.1 | 1.4 | 1.37 |
| **jp-osa-osa22-a** |  1.4 | 0.1 | 1.36 |
| **jp-osa-osa23-a** |  1.37 | 1.36 | 0.1 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-jp-osa}
{: tab-title="Osaka"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | au-syd-syd01-a | au-syd-syd04-a | au-syd-syd05-a |
| --- | :---: | :---: | :---: |
| **au-syd-syd01-a** |  0.1 | 1.72 | 0.95 |
| **au-syd-syd04-a** |  1.72 | 0.1 | 1.78 |
| **au-syd-syd05-a** |  0.95 | 1.78 | 0.1 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-au-syd}
{: tab-title="Sydney"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-tok-tok02-a | jp-tok-tok04-a | jp-tok-tok05-a |
| --- | :---: | :---: | :---: |
| **jp-tok-tok02-a** |  0.1 | 1.46 | 0.98 |
| **jp-tok-tok04-a** |  1.46 | 0.1 | 1.64 |
| **jp-tok-tok05-a** |  0.98 | 1.64 | 0.1 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-jp-tok}
{: tab-title="Tokyo"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

| Average latency (ms) | br-sao-sao01-a | br-sao-sao04-a | br-sao-sao05-a |
| --- | :---: | :---: | :---: |
| **br-sao-sao01-a** |  0.1 | 1.57 | 0.53 |
| **br-sao-sao04-a** |  1.57 | 0.1 | 1.68 |
| **br-sao-sao05-a** |  0.53 | 1.68 | 0.09 |
{: caption="18 Jul 2026–16 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-16-br-sao}
{: tab-title="Sao Paulo"}
{: tab-group="network-latency-az-tabs-2026-08-16"}
{: class="simple-tab-table"}

## 9 Aug 2026
{: #network-latency-2026-08-09}

### Inter-region latency
{: #network-latency-2026-08-09-mzr}
| Average latency (ms) | Dallas | Toronto | Washington DC | Frankfurt | London | Madrid | Montreal | Chennai | Mumbai | Osaka | Sydney | Tokyo | Sao Paulo |
| --- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
| **Dallas** |   | 36 | 32 | 123 | 113 | 119 | 42 | 248 | 247 | 152 | 184 | 144 | 142 |
| **Toronto** |  34 |  | 19 | 93 | 83 | 109 | 11 | 220 | 198 | 144 | 216 | 135 | 125 |
| **Washington DC** |  32 | 20 |  | 86 | 76 | 89 | 16 | 242 | 224 | 147 | 217 | 139 | 123 |
| **Frankfurt** |  123 | 93 | 86 |  | 13 | 29 | 89 | 142 | 118 | 235 | 249 | 227 | 192 |
| **London** |  113 | 83 | 76 | 13 |  | 26 | 79 | 144 | 126 | 246 | 260 | 240 | 181 |
| **Madrid** |  119 | 109 | 89 | 30 | 26 |  | 104 | 156 | 138 | 261 | 275 | 254 | 212 |
| **Montreal** |  42 | 10 | 16 | 89 | 79 | 105 |  | 223 | 198 | 151 | 224 | 143 | 122 |
| **Chennai** |  248 | 221 | 242 | 142 | 141 | 152 | 218 |  | 24 | 112 | 126 | 105 | 362 |
| **Mumbai** |  248 | 200 | 220 | 121 | 117 | 131 | 196 | 25 |  | 139 | 153 | 132 | 347 |
| **Osaka** |  152 | 142 | 147 | 236 | 246 | 262 | 150 | 122 | 139 |  | 113 | 9 | 290 |
| **Sydney** |  186 | 214 | 214 | 249 | 260 | 275 | 224 | 126 | 154 | 114 |  | 107 | 325 |
| **Tokyo** |  143 | 135 | 140 | 228 | 239 | 253 | 143 | 104 | 131 | 9 | 104 |  | 282 |
| **Sao Paulo** |  143 | 125 | 122 | 191 | 181 | 209 | 122 | 368 | 345 | 290 | 324 | 283 |  |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}

### Inter-AZ latency
{: #network-latency-2026-08-09-az}

| Average latency (ms) | us-south-dal10-a | us-south-dal12-a | us-south-dal13-a | us-south-dal14-a |
| --- | :---: | :---: | :---: | :---: |
| **us-south-dal10-a** |  0.08 | 2.14 | 1.96 | 1.83 |
| **us-south-dal12-a** |  2.14 | 0.1 | 1.41 | 0.6 |
| **us-south-dal13-a** |  1.96 | 1.41 | 0.1 | 1.54 |
| **us-south-dal14-a** |  1.83 | 0.6 | 1.54 | 0.1 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-us-south}
{: tab-title="Dallas"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-tor-tor01-a | ca-tor-tor04-a | ca-tor-tor05-a |
| --- | :---: | :---: | :---: |
| **ca-tor-tor01-a** |  0.1 | 1.53 | 1.72 |
| **ca-tor-tor04-a** |  1.53 | 0.1 | 1.65 |
| **ca-tor-tor05-a** |  1.72 | 1.65 | 0.1 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-ca-tor}
{: tab-title="Toronto"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | us-east-wdc04-a | us-east-wdc06-a | us-east-wdc07-a |
| --- | :---: | :---: | :---: |
| **us-east-wdc04-a** |  0.1 | 0.69 | 0.69 |
| **us-east-wdc06-a** |  0.69 | 0.12 | 0.28 |
| **us-east-wdc07-a** |  0.69 | 0.28 | 0.09 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-us-east}
{: tab-title="Washington DC"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-de-fra02-a | eu-de-fra04-a | eu-de-fra05-a |
| --- | :---: | :---: | :---: |
| **eu-de-fra02-a** |  0.1 | 0.74 | 0.68 |
| **eu-de-fra04-a** |  0.74 | 0.1 | 0.46 |
| **eu-de-fra05-a** |  0.68 | 0.46 | 0.11 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-eu-de}
{: tab-title="Frankfurt"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-gb-lon04-a | eu-gb-lon05-a | eu-gb-lon06-a |
| --- | :---: | :---: | :---: |
| **eu-gb-lon04-a** |  0.09 | 1.42 | 0.74 |
| **eu-gb-lon05-a** |  1.42 | 0.08 | 0.66 |
| **eu-gb-lon06-a** |  0.74 | 0.66 | 0.08 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-eu-gb}
{: tab-title="London"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| 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.1 | 0.79 |
| **eu-es-mad05-a** |  0.61 | 0.79 | 0.1 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-eu-es}
{: tab-title="Madrid"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-mon-mon04-a | ca-mon-mon04-b | ca-mon-mon04-c |
| --- | :---: | :---: | :---: |
| **ca-mon-mon04-a** |  0.07 | 0.13 | 0.13 |
| **ca-mon-mon04-b** |  0.13 | 0.07 | 0.13 |
| **ca-mon-mon04-c** |  0.13 | 0.13 | 0.08 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-ca-mon}
{: tab-title="Montreal"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | in-che-che02-a | in-che-che02-b | in-che-che02-c |
| --- | :---: | :---: | :---: |
| **in-che-che02-a** |  0.08 | 0.14 | 0.14 |
| **in-che-che02-b** |  0.14 | 0.08 | 0.13 |
| **in-che-che02-c** |  0.14 | 0.13 | 0.08 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-in-che}
{: tab-title="Chennai"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | in-mum-mum05-a | in-mum-mum02-a | in-mum-mum03-a |
| --- | :---: | :---: | :---: |
| **in-mum-mum05-a** |  0.08 | 0.28 | 0.75 |
| **in-mum-mum02-a** |  0.28 | 0.08 | 0.74 |
| **in-mum-mum03-a** |  0.75 | 0.74 | 0.08 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-in-mum}
{: tab-title="Mumbai"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-osa-osa21-a | jp-osa-osa22-a | jp-osa-osa23-a |
| --- | :---: | :---: | :---: |
| **jp-osa-osa21-a** |  0.1 | 1.41 | 1.38 |
| **jp-osa-osa22-a** |  1.41 | 0.1 | 1.35 |
| **jp-osa-osa23-a** |  1.38 | 1.35 | 0.1 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-jp-osa}
{: tab-title="Osaka"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | au-syd-syd01-a | au-syd-syd04-a | au-syd-syd05-a |
| --- | :---: | :---: | :---: |
| **au-syd-syd01-a** |  0.1 | 1.72 | 0.96 |
| **au-syd-syd04-a** |  1.72 | 0.1 | 1.75 |
| **au-syd-syd05-a** |  0.96 | 1.75 | 0.1 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-au-syd}
{: tab-title="Sydney"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| 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.1 | 1.62 |
| **jp-tok-tok05-a** |  0.97 | 1.62 | 0.1 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-jp-tok}
{: tab-title="Tokyo"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

| Average latency (ms) | br-sao-sao01-a | br-sao-sao04-a | br-sao-sao05-a |
| --- | :---: | :---: | :---: |
| **br-sao-sao01-a** |  0.1 | 1.57 | 0.53 |
| **br-sao-sao04-a** |  1.57 | 0.1 | 1.69 |
| **br-sao-sao05-a** |  0.53 | 1.69 | 0.1 |
{: caption="11 Jul 2026–9 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-09-br-sao}
{: tab-title="Sao Paulo"}
{: tab-group="network-latency-az-tabs-2026-08-09"}
{: class="simple-tab-table"}

## 2 Aug 2026
{: #network-latency-2026-08-02}

### Inter-region latency
{: #network-latency-2026-08-02-mzr}
| Average latency (ms) | Dallas | Toronto | Washington DC | Frankfurt | London | Madrid | Montreal | Chennai | Mumbai | Osaka | Sydney | Tokyo | Sao Paulo |
| --- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
| **Dallas** |   | 35 | 32 | 123 | 113 | 122 | 42 | 248 | 246 | 150 | 185 | 143 | 141 |
| **Toronto** |  34 |  | 19 | 92 | 82 | 108 | 10 | 221 | 197 | 144 | 216 | 135 | 125 |
| **Washington DC** |  32 | 19 |  | 86 | 76 | 89 | 16 | 243 | 225 | 147 | 218 | 139 | 125 |
| **Frankfurt** |  123 | 92 | 86 |  | 13 | 29 | 89 | 143 | 119 | 234 | 249 | 226 | 192 |
| **London** |  113 | 82 | 76 | 13 |  | 25 | 79 | 146 | 126 | 245 | 260 | 239 | 182 |
| **Madrid** |  120 | 108 | 90 | 30 | 26 |  | 105 | 157 | 138 | 260 | 274 | 253 | 210 |
| **Montreal** |  42 | 11 | 16 | 89 | 79 | 105 |  | 224 | 197 | 151 | 226 | 143 | 122 |
| **Chennai** |  248 | 222 | 242 | 143 | 142 | 154 | 221 |  | 24 | 110 | 126 | 103 | 360 |
| **Mumbai** |  249 | 197 | 219 | 121 | 119 | 130 | 197 | 24 |  | 137 | 153 | 130 | 343 |
| **Osaka** |  151 | 142 | 148 | 234 | 245 | 261 | 150 | 111 | 137 |  | 120 | 9 | 289 |
| **Sydney** |  185 | 213 | 215 | 249 | 260 | 275 | 223 | 126 | 154 | 120 |  | 113 | 322 |
| **Tokyo** |  142 | 135 | 140 | 226 | 236 | 252 | 143 | 103 | 129 | 9 | 113 |  | 281 |
| **Sao Paulo** |  142 | 125 | 119 | 192 | 182 | 209 | 121 | 369 | 347 | 289 | 324 | 282 |  |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}

### Inter-AZ latency
{: #network-latency-2026-08-02-az}

| Average latency (ms) | us-south-dal10-a | us-south-dal12-a | us-south-dal13-a | us-south-dal14-a |
| --- | :---: | :---: | :---: | :---: |
| **us-south-dal10-a** |  0.08 | 2.08 | 1.94 | 1.83 |
| **us-south-dal12-a** |  2.08 | 0.1 | 1.4 | 0.6 |
| **us-south-dal13-a** |  1.94 | 1.4 | 0.1 | 1.53 |
| **us-south-dal14-a** |  1.83 | 0.6 | 1.53 | 0.1 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-us-south}
{: tab-title="Dallas"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-tor-tor01-a | ca-tor-tor04-a | ca-tor-tor05-a |
| --- | :---: | :---: | :---: |
| **ca-tor-tor01-a** |  0.1 | 1.52 | 1.71 |
| **ca-tor-tor04-a** |  1.52 | 0.1 | 1.64 |
| **ca-tor-tor05-a** |  1.71 | 1.64 | 0.1 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-ca-tor}
{: tab-title="Toronto"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | us-east-wdc04-a | us-east-wdc06-a | us-east-wdc07-a |
| --- | :---: | :---: | :---: |
| **us-east-wdc04-a** |  0.09 | 0.67 | 0.69 |
| **us-east-wdc06-a** |  0.67 | 0.12 | 0.28 |
| **us-east-wdc07-a** |  0.69 | 0.28 | 0.08 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-us-east}
{: tab-title="Washington DC"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-de-fra02-a | eu-de-fra04-a | eu-de-fra05-a |
| --- | :---: | :---: | :---: |
| **eu-de-fra02-a** |  0.1 | 0.74 | 0.69 |
| **eu-de-fra04-a** |  0.74 | 0.1 | 0.46 |
| **eu-de-fra05-a** |  0.69 | 0.46 | 0.11 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-eu-de}
{: tab-title="Frankfurt"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | eu-gb-lon04-a | eu-gb-lon05-a | eu-gb-lon06-a |
| --- | :---: | :---: | :---: |
| **eu-gb-lon04-a** |  0.09 | 1.52 | 0.75 |
| **eu-gb-lon05-a** |  1.52 | 0.08 | 0.66 |
| **eu-gb-lon06-a** |  0.75 | 0.66 | 0.08 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-eu-gb}
{: tab-title="London"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| 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.1 | 0.79 |
| **eu-es-mad05-a** |  0.61 | 0.79 | 0.1 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-eu-es}
{: tab-title="Madrid"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | ca-mon-mon04-a | ca-mon-mon04-b | ca-mon-mon04-c |
| --- | :---: | :---: | :---: |
| **ca-mon-mon04-a** |  0.07 | 0.13 | 0.13 |
| **ca-mon-mon04-b** |  0.13 | 0.07 | 0.13 |
| **ca-mon-mon04-c** |  0.13 | 0.13 | 0.08 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-ca-mon}
{: tab-title="Montreal"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | in-che-che02-a | in-che-che02-b | in-che-che02-c |
| --- | :---: | :---: | :---: |
| **in-che-che02-a** |  0.08 | 0.14 | 0.14 |
| **in-che-che02-b** |  0.14 | 0.08 | 0.13 |
| **in-che-che02-c** |  0.14 | 0.13 | 0.08 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-in-che}
{: tab-title="Chennai"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | in-mum-mum05-a | in-mum-mum02-a | in-mum-mum03-a |
| --- | :---: | :---: | :---: |
| **in-mum-mum05-a** |  0.08 | 0.28 | 0.74 |
| **in-mum-mum02-a** |  0.28 | 0.08 | 0.74 |
| **in-mum-mum03-a** |  0.74 | 0.74 | 0.08 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-in-mum}
{: tab-title="Mumbai"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-osa-osa21-a | jp-osa-osa22-a | jp-osa-osa23-a |
| --- | :---: | :---: | :---: |
| **jp-osa-osa21-a** |  0.1 | 1.41 | 1.39 |
| **jp-osa-osa22-a** |  1.41 | 0.1 | 1.35 |
| **jp-osa-osa23-a** |  1.39 | 1.35 | 0.1 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-jp-osa}
{: tab-title="Osaka"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | au-syd-syd01-a | au-syd-syd04-a | au-syd-syd05-a |
| --- | :---: | :---: | :---: |
| **au-syd-syd01-a** |  0.1 | 1.71 | 0.89 |
| **au-syd-syd04-a** |  1.71 | 0.1 | 1.78 |
| **au-syd-syd05-a** |  0.89 | 1.78 | 0.1 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-au-syd}
{: tab-title="Sydney"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | jp-tok-tok02-a | jp-tok-tok04-a | jp-tok-tok05-a |
| --- | :---: | :---: | :---: |
| **jp-tok-tok02-a** |  0.1 | 1.5 | 0.97 |
| **jp-tok-tok04-a** |  1.5 | 0.1 | 1.65 |
| **jp-tok-tok05-a** |  0.97 | 1.65 | 0.1 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-jp-tok}
{: tab-title="Tokyo"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}

| Average latency (ms) | br-sao-sao01-a | br-sao-sao04-a | br-sao-sao05-a |
| --- | :---: | :---: | :---: |
| **br-sao-sao01-a** |  0.1 | 1.58 | 0.54 |
| **br-sao-sao04-a** |  1.58 | 0.1 | 1.69 |
| **br-sao-sao05-a** |  0.54 | 1.69 | 0.1 |
{: caption="4 Jul 2026–2 Aug 2026" caption-side="bottom"}
{: #network-latency-az-tabs-2026-08-02-br-sao}
{: tab-title="Sao Paulo"}
{: tab-group="network-latency-az-tabs-2026-08-02"}
{: class="simple-tab-table"}