Skip to main content

Cloud Connection Site List

Location List (Japan Area > Tokyo Region)

[Name]
AWS Hosted VIF (Equinix TY2, Tokyo)
AWS Hosted VIF (AT-Tokyo CC1, Tokyo)
AWS Hosted Connection (Equinix TY2, Tokyo)
AWS Hosted Connection (AT-Tokyo CC1, Tokyo)
AWS Hosted Connection (NEC Inzai, Inzai)
Google Cloud (Equinix TY4 "nrt-zone1-1893", Tokyo)
Google Cloud (AT-Tokyo CC2 "nrt-zone2-738", Tokyo)
Azure (Primary, Equinix TY4 "Tokyo", Japan East)
Azure (Secondary, Equinix TY4 "Tokyo", Japan East)
Azure (Primary, AT-Tokyo "Tokyo2", Japan East)
Azure (Secondary, AT-Tokyo "Tokyo2", Japan East)
Azure (Primary, NEC "Tokyo3", Japan East)
Azure (Secondary, NEC "Tokyo3", Japan East)
Sakura Cloud (Primary, Equinix TY4, Tokyo)
Sakura Cloud (Secondary, KDDI-Otemachi-Bldg, Tokyo)
Oracle Cloud (Equinix TY4 node1, Tokyo)
Oracle Cloud (Equinix TY4 node2, Tokyo)
Oracle Cloud (NEC Inzai Data Center SI3 node1, Tokyo)
IBM Cloud (Equinix TY4 "Tokyo3", Japan East)
IBM Cloud (Equinix TY2 "Tokyo1", Japan East)
Alibaba Cloud (Equinix TY4, Tokyo)
Alibaba Cloud (Equinix TY10, Tokyo)

Location List (Japan Area > Osaka Region)

[Name]
AWS Hosted Connection (Equinix OS1 node1, Osaka)
AWS Hosted Connection (Equinix OS1 node2, Osaka)
Google Cloud (Equinix OS1 "kix-zone1-1791", Osaka)
Google Cloud (Equinix OS1 "kix-zone2-1791", Osaka)
Azure (Primary, Equinix OS1 "Osaka", Japan West)
Azure (Secondary, Equinix OS1 "Osaka", Japan West)
Oracle Cloud (NTT-DATA Dojima Bldg 4 node1, Osaka)
Oracle Cloud (NTT-DATA Dojima Bldg 4 node2, Osaka)
IBM Cloud (Equinix OS1 "Osaka1" node1, Japan West)
IBM Cloud (Equinix OS1 "Osaka1" node2, Japan West)

Location List (Singapore Area > Singapore Region)

[Name]
AWS Hosted Connection (Equinix SG2, Singapore)
AWS Hosted Connection (Global Switch, Singapore)
Oracle Cloud (Equinix SG1 node1, Singapore)
Oracle Cloud (Equinix SG1 node2, Singapore)

Removal of Primary/Secondary

For specific cloud environments, the Primary/Secondary designations have been discontinued in the interconnection information due to the following reasons:

  • To avoid inconsistency, the potential confusion of using a "Secondary" label for a non-redundant Cloud Connection is addressed.
  • To ensure flexibility, Primary and Secondary roles can now be freely defined, reflecting the fact that no fundamental hierarchy exists between locations.