Peering Policy

WITmind (AS42100) has an open peering policy, and will peer with networks that have a presence on mutual exchange points in accordance with the policies described below. If you operate a peering network, you can contact us at [email protected]

Requirements

WITmind uses PeeringDB as a single authoritative source of truth. This means peering partners must have an up-to-date PeeringDB entry before a bilateral peering session can be established. Both parties should have a well set-up route-set or AS-SET as well as up-to date prefix maximums defined in PeeringDB. Cloudflare will use this data to filter routes received from the network’s BGP sessions. Both parties must have an up-to-date NOC contact email, which is responsive to raised issues and concerns.

Notices

To ensure quality of operations, we reserve the following rights under our Peering Policy:

  • To alter our peering policy and peering requirements at any time.
  • To accept or decline a peering request at any time for any reason.
  • 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.
  • To selectively withdraw prefixes from public IXP fabrics as needed to protect service quality.
  • To terminate any peering connection at any time without notice.

More details on PeeringDB at https://www.peeringdb.com/asn/42100.