Joyent Global Network Interconnection (“Peering”) Policy and Requirements

Joyent is a global network with POP (point of presence) locations across North America, Europe, and Asia. Joyent peers with other Internet Service Providers (ISPs) and Content Networks with IPv4 and IPv6 connectivity on Autonomous System Number (ASN) 26464 to exchange traffic with those networks to provide faster, higher quality service to its customers. Joyent reserves the right, however, to manage and/or make available other ASNs for peering purposes.

1. Selective Peering Policy

Joyent has a selective but generally open peering policy which is governed by and shall be construed in accordance with the laws of California. Joyent’s peering policy is a set of guidelines used by Joyent to select settlement-free interconnection partners, and this policy should not be considered to be a contract under which Joyent guarantees any interconnection relationship with any other entity. Joyent selects peers based on performance, capability, and where traffic needs to be delivered. Peers are subject to certain operational, technical, and legal requirements to ensure our quality of service.

JOYENT RESERVES THE RIGHT TO UPDATE THIS PEERING POLICY AND TO ENTER INTO AND TERMINATE ANY PEERING RELATIONSHIPS AT ITS SOLE DISCRETION. JOYENT MAY TERMINATE ITS PEERING RELATIONSHIP WITH ANY THIRD PARTY FOR ANY REASON OR NO REASON. JOYENT SHALL INCUR NO LIABILITY WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE THROUGH ITS PEERING RELATIONSHIP WITH ANY THIRD PARTY AND ALL THIRD PARTIES WITH WHICH WE HAVE A PEERING RELATIONSHIP HAVE RELEASED OR SHALL RELEASE JOYENT FROM ANY AND ALL CLAIMS, LIABILITIES, DEMANDS, LOSSES, AND DAMAGES THAT MAY ARISE FROM THEIR PEERING RELATIONSHIP WITH JOYENT.

2. Peering Requirements

To maintain optimum service levels for our customers, Joyent requires its peers to meet the following operational and technical requirements when making a peering request to Joyent, and to maintain these technical and operational requirements at all times during the peering relationship with Joyent. Joyent may request documentation and/or interviews with network engineers to verify these prerequisites prior to establishing peering.

Operational Requirements:

  • Exchange traffic with Joyent at all available Internet exchange providers (“IXPs”) that are shared in common for optimal traffic distribution and redundancy.
  • Maintain a full and accurate PeeringDB listing for their network and point of presence details with its Network Operations Center (“NOC”) and peering administrator contact details.
    • Peers must list their private peering facilities so that Joyent may identify private peering (“PNI”) options.
  • Maintain congestion free interconnection with Joyent. Joyent will, and expects all of its peers to, work quickly and diligently to augment capacity between networks or to the appropriate IXP, as needed.
  • Maintain a NOC that is staffed 24 hours a day, 7 days a week that shall:
    • Be staffed with technically capable network administrators to promptly respond to any operational problems and security incidents whenever they arise;
    • Proactively monitor their network for activities considered malicious and/or detrimental to the Internet as a whole, its own network, or to its customers, including, without limitation, sending unsolicited bulk email, hacking, disseminating harmful code, advertising incorrect routing information, and denial of service attacks;
    • Trace and mitigate attacks promptly; and
    • Have senior engineers and management on call as escalation points for resolving operational problems and/or security incidents in a timely fashion.

Technical Requirements:

Peers must:

  • Maintain a publicly routed ASN.
  • Have at least one common Internet exchange (“IX”) point with Joyent.
  • Agree to peer in all common IX points
  • Not advertise prefixes with a mask longer than /24 for IPv4 and /48 for IPv6
  • Demonstrate that announced publicly routable prefixes and/or aggregates are currently visible in the DFZ
  • Announce a consistent set of prefixes to Joyent at all points of interconnection, unless otherwise agreed upon.
  • Only send traffic destined for prefixes announced by Joyent.
  • Maintain MD5 authentication
  • Not point a default route at Joyent or use static routes to send traffic to our ASN.
  • Set default maximum prefixes per session to 200 prefixes for IPv4 and 20 prefixes for IPv6, or to the currently posted values in https://www.peeringdb.com/net/18863, whichever are larger.
  • Register their prefixes with appropriate route/route6 objects at an appropriate IRRDB. Joyent, will use this data to build BGP prefix lists.
  • Joyent maintains all public IP addressing records with the regional Internet Route Registries and RADB as well as information available on PeeringDB.com.
  • We will work with peers to maintain adequate capacity between our networks under situations of heavy load but may shift to alternate CDN, POPS, links or providers during periods of heavy load.