Location comparison between Direct Link versions
Review location support for Direct Link on Classic offerings versus Direct Link.
| Location | Dedicated on Classic | Dedicated | Dedicated w/ MACsec | Connect on Classic | Connect |
|---|---|---|---|---|---|
| Atlanta 1 |  |
||||
| Chicago 1 | |
|
|
|
|
| Dallas 3 | |
|
|
|
|
| Dallas 4 | |
|
|
|
|
| Dallas 9 | |
||||
| Dallas 10 | |
|
|||
| Dallas 12 | |
|
|
|
|
| Dallas 13 | |
|
|
|
|
| Dallas 14 | |
|
|
||
| Denver 1 | |
|
|
||
| Los Angeles | |
|
|||
| Miami 1 | |
|
|
||
| Montreal 1 | |
|
|
|
|
| Montreal 2 | |
|
|
|
|
| New York City 2 | |
|
[1] |
||
| San Jose 2 | |
|
|
|
|
| San Jose 3 | |
||||
| San Jose 4 | |
|
|||
| Sao Paulo 1 | |
|
|
|
|
| Sao Paulo 2 | |
|
|
|
|
| Sao Paulo 3 | |
||||
| Sao Paulo 4 | |
||||
| Sao Paulo 5 | |
|
|||
| Seattle 2 | |
|
|||
| Toronto 1 | |
|
|
|
|
| Toronto 2 | |
|
|
|
|
| Toronto 3 | |
|
|||
| Toronto 4 | |
||||
| Toronto 5 | |
||||
| Washington DC 2 | |
|
|
|
|
| Washington DC 4 | |
|
|
|
|
| Washington DC 5 | |
|
|
||
| Washington DC 6 | |
|
|
|
|
| Washington DC 7 | |
|
| Location | Dedicated on Classic | Dedicated | Dedicated w/ MACsec | Connect on Classic | Connect |
|---|---|---|---|---|---|
| Chennai 1 | |
|
|
|
|
| Chennai 4 | |
|
|||
| Hong Kong 1 | |
|
|||
| Hong Kong 3 | |
|
|
|
|
| Melbourne 2 | |
|
|||
| Mumbai 4 | |
||||
| Osaka 1 | |
|
|
|
|
| Osaka 21 | |
|
|
|
|
| Osaka 22 | |
|
|||
| Osaka 23 | |
|
|||
| Singapore 1 | |
|
[2] |
||
| Singapore 2 | |
|
|
||
| Sydney 1 | |
|
|||
| Sydney 2 | |
|
|
|
|
| Sydney 3 | |
|
|
|
|
| Sydney 4 | |
|
|
|
|
| Sydney 5 | |
|
|
|
|
| Taipei 1 | |
|
|
||
| Tokyo 1 | |
|
|||
| Tokyo 2 | |
|
|
|
|
| Tokyo 3 | |
|
|
|
|
| Tokyo 4 | |
|
|
|
|
| Tokyo 5 | |
|
|
|
| Location | Dedicated on Classic | Dedicated | Dedicated w/ MACsec | Connect on Classic | Connect |
|---|---|---|---|---|---|
| Amsterdam 2 | |
|
|
|
|
| Amsterdam 3 | |
||||
| Frankfurt 1 | |
|
|
|
|
| Frankfurt 2 | |
|
|||
| Frankfurt 3 | |
|
|
|
|
| Frankfurt 4 | |
|
|
|
|
| Frankfurt 5 | |
|
|||
| London 1 | |
|
|
|
|
| London 2 | |
|
|||
| London 3 | |
|
|
|
|
| London 4 | |
|
|
|
|
| London 6 | |
|
|
|
|
| Madrid 1 | |
|
|
||
| Madrid 2 | |
|
|
||
| Madrid 3 | |
|
|
||
| Madrid 4 | |
|
|
||
| Madrid 5 | |
|
|
||
| Milan 2 | |
|
|||
| Paris 1 | |
|
|
|
|
| Paris 2 | |
|
|
|
|
| Paris 3 | |
|
|
-
New York City 2 connects to the IBM Cloud backbone through New York City 1. The primary reason for this PoP is to extend connectivity to different site providers from our New York City 1 site. When planning your diversity strategy, keep in mind that traffic for New York City 2 has a single, shared path to the IBM network. ↩︎
-
If you require diversity, you must place a second (backup) connection with Megaport in Hong Kong 3 (HKG03). ↩︎