# Network Infrastructure

DIDWW operates a globally distributed voice network designed for high availability, low latency, and geographic
redundancy. Our Points of Presence (PoPs) are strategically located in major interconnection hubs worldwide to ensure
optimal routing and service quality.

## Points of Presence (PoPs)

### North America

🇺🇸 **New York, USA**

**Location:** 111 8th Avenue, Digital Realty
**Region:** North America

🇺🇸 **Los Angeles, USA**

**Location:** One Wilshire, CoreSite
**Region:** North America

🇺🇸 **Miami, USA**

**Location:** 50 NE 9th Street, Equinix MI1
**Region:** North America

### Europe

🇩🇪 **Frankfurt, Germany**

**Location:** Kleyerstraße 90, ITENOS
**Region:** Europe

🇳🇱 **Amsterdam, Netherlands**

**Location:** Kuiperbergweg 13, Equinix AM7
**Region:** Europe

### Asia-Pacific

🇸🇬 **Singapore**

**Location:** 26A Ayer Rajah Crescent, Equinix SG3
**Region:** Asia-Pacific

🇭🇰 **Hong Kong**

**Location:** 17/F Global Gateway, Equinix HK1
**Region:** Asia-Pacific

Note

For IP configuration details, refer to the [Inbound Trunks SIP
Information](../voice/inbound-trunks/sip-trunks/sip-connectivity-reference.html#service-did-sip) and [Outbound Trunks
Signaling Endpoints](../voice/outbound-trunks/outbound-sip-information.html#voice-out-signaling-endpoints).

## Interconnections

DIDWW supports several methods of interconnecting with its global voice infrastructure to enhance call quality,
reliability, and security. These include private physical connections, public Internet Exchange peering, and encrypted
VPN tunnels.

Note

For a full overview of our network footprint, visit our [PeeringDB profile](https://www.peeringdb.com/org/26616).
 To discuss interconnection options, please contact your account manager or email
[sales@didww.com](mailto:sales%40didww.com).

### Private Interconnection

Connect directly to DIDWW's infrastructure at one or more global Points of Presence (PoPs). This is the most secure and
performance-optimized interconnection method. Physical connectivity requires coordination and infrastructure setup at
the selected PoP.

[![Private physical interconnection scheme](../_images/Private_Interconnection_v2.svg)](../_images/Private_Interconnection_v2.svg)


**Fig. 1.** Private physical interconnection scheme

### Public Peering Facilities

DIDWW supports peering via major Internet Exchange platforms. This allows for flexible and scalable interconnection
across multiple geographic locations using public VLANs or virtual private interconnects.

> - **DE-CIX** - Present at New York and Frankfurt. Peering via [DE-CIX](https://www.de-cix.net), or use [Virtual PNI](https://www.de-cix.net/en/services/virtualpni).
> - **AMS-IX** - Connected in Amsterdam via [AMS-IX](https://www.ams-ix.net/ams). Supports [AMS-IX Private Interconnect](https://www.ams-ix.net/ams/service/private-interconnect).
> - **Equinix IX** - Available in Amsterdam via [Equinix IX](https://ix.equinix.com/home/).
> - **Equinix Fabric** - Supported in Frankfurt and Amsterdam via [Equinix Fabric](https://www.equinix.com/products/digital-infrastructure-services/equinix-fabric).
> - **PCCW Console Connect** - Accessible through [Console Connect](https://www.consoleconnect.com) SDN platform in Hong Kong.

[![Peering scheme](../_images/Public_Peering_Facilities_v2.svg)](../_images/Public_Peering_Facilities_v2.svg)


**Fig. 2.** Peering interconnection scheme

### IPSec VPN

DIDWW offers encrypted interconnection over IPSec VPN, allowing secure voice traffic routing over public infrastructure.
While this option does not impact pathing, it provides strong encryption and supports private IP addressing for SIP
endpoints.

Supported PoPs for IPSec VPN:

> - USA, New York
> - Germany, Frankfurt

Multiple VPN tunnels are recommended for failover and redundancy.

[![VPN interconnection scheme](../_images/IPSec_VPN_v2.svg)](../_images/IPSec_VPN_v2.svg)


**Fig. 3.** IPSec VPN interconnection scheme

### Machine-readable network data

A machine-readable version of DIDWW's voice signaling and media network data is available as JSON:

[voice.json](/voice.json)

Use it to programmatically configure and monitor firewall or SBC allowlists,
instead of parsing documentation pages.

On this page