Skip to main content

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 SidesShort Path(µs)Long Path(µs)Notes
Atlanta AT1 – AT43961167
Atlanta AT1 – AT55321032
Atlanta AT4 – AT5691873
Bogota BG1 – BG250100Latency data applies to packet-based Metro Connect only.
Chicago CH1/2/4 – CH3471498
Chicago CH1/2/4 – CH74281086
Chicago CH3 – CH74821034
Calgary CL1 – CL2119430
Calgary CL1 – CL3337404
Calgary CL2 – CL3210430
Culpeper CU1/2/3/4/6 – DC1/2/3/4/5/6/10/11/12/15/16/2115691600
Dallas DA4 – DA1/2/3/6/111211604
Dallas DA4 – DA7762963
Dallas DA1/2/3/6/11 – DA7842883
Washington, D.C. DC1/2/3/4/5/6/10/11/12/15/16/21 – DC131053064
Washington, D.C. DC1/2/3/4/5/6/10/11/12/15/16/21 – DC146352523
Los Angeles LA1 – LA4296335
Los Angeles LA1 – LA649581
Los Angeles LA1 – LA7TBCTBCSee footnote 6.
Los Angeles LA3/4 – LA7441613
Los Angeles LA4 – LA6285345
Miami MI1 – MI39841738
Miami MI1 – MI63932312
Miami MI2 – MI1N/AN/AFiber Connect recommended; see footnote 1.
Miami MI2 – MI310131767For testing methodology, see footnote 2.
Miami MI2 – MI64222341For testing methodology, see footnote 2.
Miami MI3 – MI613991320
Montreal MT1 – MT25171005
New York NY11 – NY2/4/5/6425655
New York NY13 – NY2/4/5/6902TBCSee footnote 6; 1G packet-based Metro Connect recommended for long path.
New York NY13 – NY9591N/AFabric is recommended for long path.
New York NY1 – NY11323N/AFabric is recommended for long path.
New York NY1 – NY2/4/5/6211400
New York NY1 – NY7442632
New York NY1 – NY9241871
New York NY2/4/5/6 – NY7269550
New York NY2/4/5/6 – NY9159660
New York NY7 – NY9391429
Rio de Janeiro RJ1 – RJ2155235
Seattle SE2/3 – SE415264728
São Paulo SP1 – SP22232872019 latency data; current data +/- 20%
São Paulo SP1 – SP32352752019 latency data; current data +/- 20%
São Paulo SP1 – SP41773332019 latency data; current data +/- 20%
São Paulo SP2 – SP3734372019 latency data; current data +/- 20%
São Paulo SP2 – SP41323792019 latency data; current data +/- 20%
São Paulo SP3 – SP4794312019 latency data; current data +/- 20%
Santiago ST1/2 – ST3576636
Silicon Valley SV1/5/10/11 – SV2 (SV14/15/16/17)234868See footnote 5.
Silicon Valley SV1/5/10/11 – SV3167935
Silicon Valley SV1/5/10/11 – SV4383747
Silicon Valley SV1/5/10/11 – SV6480796
Silicon Valley SV1/5/10/11 – SV8383602
Silicon Valley SV2 – SV3172701
Silicon Valley SV2 – SV4383422
Silicon Valley SV2 – SV6441928
Silicon Valley SV2 – SV8368734
Silicon Valley SV3 – SV4188914
Silicon Valley SV3 – SV6469963
Silicon Valley SV3 – SV8375769
Silicon Valley SV4 – SV63591151
Silicon Valley SV4 – SV8145883
Silicon Valley SV6 – SV8194208
Toronto TR1/2 – TR41221113See footnote 4.
Toronto TR1/2 – TR54931321See footnote 4.
Toronto TR1/2 – TR6/77041087See footnote 4.
Toronto TR4 – TR6/76601131
Toronto TR5 – TR6/7N/AN/AFabric 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 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 – TR4, 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).