top of page

Peering Policy

Open Peering Policy

Word Cloud has an open peering policy, but peers are subject to certain operational, technical, and legal requirements.

Operational Requirements

To maintain optimum service levels for our customers and their clientele, peers shall meet the following set of requirements:

  1. Exchange traffic with Word Cloud at all available IXPs that are shared in common for optimal traffic distribution and redundancy.

  2. Must maintain a Network Operations Center capable of responding operational problems and security incidents 24 hours per day, 7 days per week.

  3. Be responsive to activities considered malicious and/or detrimental to the Internet as a whole, its own network, and to its customers, including but not limited to, sending unsolicited bulk email, hacking, and denial of service. Word Cloud expects peers to provide a qualified engineer to help trace and mitigate attacks in a reasonable amount of time.

  4. Meet all requirements at the time the peering request is made, and must continue to be met for the duration of the peering session.


Technical Requirements

The following technical requirements also apply to peering with Word Cloud. Peers must:

  1. Have a publicly routed ASN.

  2. Not point a default route at Word Cloud or use static routes to send traffic to our AS.

  3. Only send traffic destined for prefixes announced by Word Cloud  .

  4. Register their prefixes with appropriate route/route6 objects at an appropriate IRRDB, and maintain a full and accurate PeeringDB listing. Word Cloud    will use this data to build BGP prefix lists.


Additional Requirements

To ensure the quality of operations, Word Cloud  reserves the following rights under its peering policy:

  1. To alter our peering policy and peering requirements at any time.

  2. To accept or decline a peering request at any time for any reason.

  3. To suspend, without notice, peering connectivity in the event of a severe quality of service issue such as high latency, packet loss, or jitter pattern is detected and to take appropriate traffic engineering steps to maintain service quality.

  4. To terminate any peering connection at any time without notice.

Reliable. Infrastructure-Based. Extraordinary.

bottom of page