Peering Policy

Peering Information

Panascais relies on industry standard and best common practices, including but not limited to RPKI validation and route filtering.

You can find more information at peeringdb.com/asn/211757

Requirements

• All peers must maintain a 24×7 contactable NOC.
• 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 AS-SET as well as up-to date prefix maximums defined in PeeringDB.
• Both parties must have an up-to-date NOC contact email, which is responsive to raised issues and concerns.

Private Interconnection Requirements

If the network exchanges more than 1Gbit/s of traffic in a specific shared location, either party can request a PNI. We accept single or multiples of 10G, 25G, 100G or 400G connections.

• Both parties agree to review the capacity on a regular basis and to increase it as required.
• Upgrades to this capacity must happen in a timely manner to ensure congestion-free exchange of traffic.
• The peer should use reasonable endeavours to provide us with advance notice of any planned maintenance work that will affect the PNI circuits.

Important Notices

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 IXPs as needed to protect service quality.
• To terminate any peering connection at any time without notice.