Telnyx Peering and Interconnection

linkTelnyx Peering Guidelines

Telnyx is a real-time communications company that delivers a la carte communication services via an e-commerce and API-based experience. The company currently provides telecom to high-volume businesses like call centers and enterprise service providers over a geographically distributed network.

linkGeneral Information
ASN63440
Peering PolicyOpen
AS-MACROAS-TELNYX
Peering DBhttps://as63440.peeringdb.com
Prefix Details
64.16.224.0/19
192.76.120.0/24
Potential /24 prefixes will be announced for site specific routing on occasion.
General Peering Inquirespeering@telnyx.com
Technical Inquiresnetwork@telnyx.com
linkPeering Policy

Telnyx operates an Open peering policy. This policy is subject to review based on technical, operational, and legal requirements.

linkGeneral Peering and Interconnection Requirements
  • Telnyx requires peering to be implemented over an Internet Exchange Point (IXP) or private cross connection (XC).
  • At each IXP, Telnyx will have two peer addresses for BGP sessions. This design is for redundancy and no routing priority will be given on either peer via configuration. We prefer sessions be established with both peers.
  • IXP peering sessions must be implemented across all available exchanges. Example: If we are members of multiple IXPs, then we require sessions to be established on all IXPs.
linkTechnical Requirements
  • Peers must have a public, verifiable ASN
  • Prefixes must be maintained in a public IRR
  • Prefixes that will be announced must also be seen in the DFZ (Default Free Zone)
  • Prefixes must not exceed a /24 in mask size
  • Communities will be sent by Telnyx
  • An accurate PeeringDB profile must be maintained
  • Do not announce a default route toward Telnyx
  • Peers may use the AS-TELNYX macro list with RADB for Telnyx prefix lists
  • Currently our platform is implemented with IPv4 address space, but we also peer with IPv6 and announce our assigned blocks.
linkOperational Requirements
  • Please have a support 24x7 NOC contact that includes escalation details for troubleshooting connectivity and traffic issues.
  • The Telnyx network team will respond and complete implementation within 48 hours. Once the peering sessions have been established, we will accept and announce prefixes within 24 hours.
  • Sessions that have not completed the initial implementation will be torn down within 5 business days.
  • Sessions that are seen as down for a period of 5 business days will be torn down unless an ongoing maintenance window has been reported by the peering NOC.
  • Telnyx will issue maintenance updates within 48 hours of planned work on our IXP or XC nodes.
linkTelnyx IXP and XC Points of Presence

Telnyx POPs are available below and at PeeringDB (https://as63440.peeringdb.com)

Public Peering Exchange Points (IXPs)
LocationPeer IPsPort Speed
Equinix Ashburn
206.126.237.147
2001:504:0:2:0:6:3440:1
1gb
Equinix Chicago
206.223.119.50
2001:504:0:4:0:6:3440:1
1gb
Equinix San Jose
206.223.116.110
2001:504:0:1:0:6:3440:1
1gb
VANIX
206.41.104.83
206.41.104.84

2001:504:39::83
2001:504:39::84
1gb
AMS-IXPending1gb
LINXPending1gb
TorIXPending1gb
Private Peering Facilities
LocationPort Speed
Equinix Ashburn10gb
Equinix Chicago10gb
Equinix San Jose10gb
Cologix VAN210gb
Equinix Toronto10gb
Equinix London10gb
linkContact us

Don’t hesitate to reach out if you have any questions!