TWDX IP

Settlement-Free Interconnection Policy — AS27552

Peering requests should be sent to TWDX IP via email to peering@twdx.net.  Members of our peering review team will endeavor to review requests within 14 business days.  Requests for peering with AS27552 are reviewed in accordance to the below policy.  The below policy serves as a general guideline to reviewing peering requests.  TWDX IP reserves the right to accept or reject requests at its sole discretion.

General Requirements

  • A publicly routable and unique ASN visible on the global routing table.
  • Operate a professionally managed 24x7 NOC or equivalent with a knowledgeable contact who is readily available.
  • Fully and correctly updated PeeringDB profile.  Peering requests will be rejected for networks not having up-to-date PeeringDB entries—please note that we rely on this information to generate prefix filters and limits.
  • Peers must only advertise their own internal and customer routes (do not send us transit or peering routes), and will not send routes with private ASN in the advertisement.
  • Peers are required to advertise consistent routes at all common peering points, except for networks where explicit exemptions have been made (for CDNs and mutually agreed traffic engineering purposes).
  • TWDX IP requires bilateral sessions at IXPs—we generally do not peer through route servers.
  • TWDX IP does not peer with direct customers.
  • TWDX IP does not peer with indirect customers (applicant's routes are reachable through a customer).
  • TWDX IP generally does not peer with downstream customer of an existing peer.  Exemptions are made for certain peers based on traffic engineering reasons.
  • Each party shall bear its own expenses related to establishment of peering.
  • TWDX IP reserves the right to terminate peering at any time with reasonable notice, but will endeavor to work with our peering partners to remediate any issues prior to such termination.  For operational issues, TWDX IP reserves the right to temporarily suspend peering immediately, where notice may be given after such suspension is made.

Public Interconnection Requirements

  • There are no requirements for traffic levels at this time, however, TWDX IP generally looks for meaningful benefit before approving new peers.  Examples of meaningful benefit include:  traffic volume, critical infrastructure (e.g. anycast instance for root/gtld-servers) or request from one of our customers that we consider peering with you, etc.
  • Peers must maintain sufficient capacity into the IX fabric to pass all traffic sent and received without queueing or loss. 
  • Sessions between TWDX IP and peer network must exist in all common markets where both networks serve customers.

Private Interconnection (PX) Requirements

  • Interconnection bandwidth must be at least 10 Gbps at every interconnection point.
  • TWDX IP generally prefers PX over public IX sessions, where traffic exchanged is at minimum of 5 Gbps.
  • Cross connect costs for PX should be equally shared by both networks.

TWDX IP Peering Locations and AS-SET Information