# AMER Region Metro Connect – Latency Here is the latency data in microseconds for the Layer 1 Dense Metro Connect connections (Round Trip) in the Americas (AMER) region. (Refer to footnote 3 for packet-based Layer 2 Metro Connect latency.) Testing Methodology – Refer to RFC2544, Industry-standard service activation test for single-service Ethernet and IP. Test data collection occurred on 15-Sep-2021 unless otherwise stated. | A-Z and Z-A Sides | Short Path(µs) | Long Path(µs) | Notes | | ------------------------------------------------------- | -------------- | ------------- | ------------------------------------------------------------------------ | | Atlanta AT1 – AT4 | 396 | 1167 | | | Bogota BG1 – BG2 | 50 | 100 | Latency data applies to packet-based Metro Connect only. | | Chicago CH1/2/4 – CH3 | 471 | 498 | | | Chicago CH1/2/4 – CH7 | 428 | 1086 | | | Chicago CH3 – CH7 | 482 | 1034 | | | Calgary CL1 – CL2 | 119 | 430 | | | Calgary CL1 – CL3 | 337 | 404 | | | Calgary CL2 – CL3 | 210 | 430 | | | Culpeper CU1/2/3/4/6 – DC1/2/3/4/5/6/10/11/12/15/16/21 | 1569 | 1600 | | | Dallas DA4 – DA1/2/3/6/11 | 121 | 1604 | | | Dallas DA4 – DA7 | 762 | 963 | | | Dallas DA1/2/3/6/11 – DA7 | 842 | 883 | | | Washington, D.C. DC1/2/3/4/5/6/10/11/12/15/16/21 – DC13 | 105 | 3064 | | | Washington, D.C. DC1/2/3/4/5/6/10/11/12/15/16/21 – DC14 | 635 | 2523 | | | Los Angeles LA1 – LA4 | 296 | 335 | | | Los Angeles LA1 – LA6 | 49 | 581 | | | Los Angeles LA1 – LA7 | TBC | TBC | See footnote 6. | | Los Angeles LA3/4 – LA7 | 441 | 613 | | | Los Angeles LA4 – LA6 | 285 | 345 | | | Miami MI1 – MI3 | 984 | 1738 | | | Miami MI1 – MI6 | 393 | 2312 | | | Miami MI2 – MI1 | N/A | N/A | Fiber Connect recommended; see footnote 1. | | Miami MI2 – MI3 | 1013 | 1767 | For testing methodology, see footnote 2. | | Miami MI2 – MI6 | 422 | 2341 | For testing methodology, see footnote 2. | | Miami MI3 – MI6 | 1399 | 1320 | | | Montreal MT1 – MT2 | 517 | 1005 | | | New York NY11 – NY2/4/5/6 | 425 | 655 | | | New York NY13 – NY2/4/5/6 | 902 | TBC | See footnote 6; 1G packet-based Metro Connect recommended for long path. | | New York NY13 – NY9 | 591 | N/A | Fabric is recommended for long path. | | New York NY1 – NY11 | 323 | N/A | Fabric is recommended for long path. | | New York NY1 – NY2/4/5/6 | 211 | 400 | | | New York NY1 – NY7 | 442 | 632 | | | New York NY1 – NY9 | 241 | 871 | | | New York NY2/4/5/6 – NY7 | 269 | 550 | | | New York NY2/4/5/6 – NY9 | 159 | 660 | | | New York NY7 – NY9 | 391 | 429 | | | Rio de Janeiro RJ1 – RJ2 | 155 | 235 | | | Seattle SE2/3 – SE4 | 1526 | 4728 | | | São Paulo SP1 – SP2 | 223 | 287 | 2019 latency data; current data +/- 20% | | São Paulo SP1 – SP3 | 235 | 275 | 2019 latency data; current data +/- 20% | | São Paulo SP1 – SP4 | 177 | 333 | 2019 latency data; current data +/- 20% | | São Paulo SP2 – SP3 | 73 | 437 | 2019 latency data; current data +/- 20% | | São Paulo SP2 – SP4 | 132 | 379 | 2019 latency data; current data +/- 20% | | São Paulo SP3 – SP4 | 79 | 431 | 2019 latency data; current data +/- 20% | | Santiago ST1/2 – ST3 | 576 | 636 | | | Silicon Valley SV1/5/10/11 – SV2 (SV14/15/16/17) | 234 | 868 | See footnote 5. | | Silicon Valley SV1/5/10/11 – SV3 | 167 | 935 | | | Silicon Valley SV1/5/10/11 – SV4 | 383 | 747 | | | Silicon Valley SV1/5/10/11 – SV8 | 383 | 602 | | | Silicon Valley SV2 – SV3 | 172 | 701 | | | Silicon Valley SV2 – SV4 | 383 | 422 | | | Silicon Valley SV2 – SV8 | 368 | 734 | | | Silicon Valley SV3 – SV4 | 188 | 914 | | | Silicon Valley SV3 – SV8 | 375 | 769 | | | Silicon Valley SV4 – SV8 | 145 | 883 | | | Toronto TR1/2 – TR5 | 493 | 1321 | See footnote 4. | | Toronto TR1/2 – TR6/7 | 704 | 1087 | See footnote 4. | | Toronto TR5 – TR6/7 | N/A | N/A | Fabric is recommended via Metro Connect to TR2. | Footnotes: 1. For Miami MI1 to MI2, we recommend using Fiber Connect. Refer to the [Fiber Connect data sheet](https://www.equinix.com/resources/data-sheets/fiber-connect/) for latency data. 2. Total latency is the sum of the Fiber Connect latency for the first segment (MI2 – MI1) and the Dense Wavelength Multiplexer latency for the second segment (MI1 – MI3 or MI1 – MI6). 3. For packet-based Layer 2 Metro Connect, the latency could be 20% more than the data shown here due to additional infrastructure. 4. For TR1 – TR5, and TR1 – TR6/7, add 30 microsecond latency due to Fiber Connect sub-segment TR1 – TR2. The optical switch is located at TR2. 5. For SV1/5/10/11 to SV14/15/16/17, add 70 microsecond latency due to Fiber Connect sub-segment SV14/15/16/17 to SV2. The optical switch is located at SV2. 6. These values are to be completed (TBC).