[go: up one dir, main page]

Trivox Peering Information

Our public peering policy, contact points and a link to our PeeringDB entry. We welcome peering requests please ensure your PeeringDB and routing registries are up to date.

Learn about peering policies that govern how networks connect and exchange traffic on the internet. Understand the principles, types, and benefits of effective peering.

Peering Policy Summary

General Policy

Open

Multiple Locations

One location is sufficient

Ratio Requirement

No

Contract Requirement

Not Required

Health & Onboarding

Standard operator health checks apply. To simplify onboarding, please ensure your PeeringDB entry, IRR records and ROAs are current before requesting peering.

Definitions

Open Peering

Open Peering means we are willing to peer broadly via IXP route servers or direct sessions, accepting routes from participants as available.

Selective Peering

Selective Peering requires pre-engagement: verified PeeringDB, IRR entries and agreement on technical details before setting up sessions.

For full, live details and peering locations see our PeeringDB profile at peeringdb.com/net/34692.

Interconnect with Trivox AS216078

This document describes how and where to interconnect with Trivox AS216078, including requirements and factors that may affect peering with third parties.

Trivox Peering Overview

Trivox has a selective settlement-free peering policy. Trivox will peer with other organizations based on several factors including current and anticipated traffic levels, number of common sites, mutual benefit, and compliance with technical and legal requirements. Trivox reserves the right to modify this policy periodically.

Public Peering Policy

Trivox maintains active peering sessions with IXP route servers at peering locations. Only local routes are advertised at each IXP due to Trivox’s topology; requests for additional public peering are generally unnecessary.

Public peering requests may be considered if the requesting network does not peer with the relevant IXP RSs, or peers with the RSs but does not announce a complete routing table. Exceptions are at Trivox’s discretion.

Private Peering Policy

Private peering is recommended when traffic between ASNs exceeds ~3 Gbps and peers have at least one site in common. Cross-connect costs are shared equitably. Minimum link speed for private peering is 10Gbps. Private peering facilities are listed in Trivox's PeeringDB entry; bandwidth will be reviewed and upgraded as required.

Trivox Peering Information

  • ASN: 216078
  • RADB AS-SET: AS216078:as-trivox
  • PeeringDB: AS216078 in PeeringDB
  • Looking glass: Trivox - Looking Glass

Peering Process

  1. Review and accept the policy and technical/legal requirements.
  2. Send peering requests to noc@trivox.sh including ASN, proposed locations, and IP addresses for public peering.
  3. Trivox analyzes the request and responds (requests are evaluated monthly).
  4. Trivox may accept or decline requests and may withdraw peering at any time.

Technical Requirements

  • Complete and up-to-date PeeringDB entry.
  • Prefixes registered in a public IRR.
  • Do not advertise Trivox prefixes to transit providers.
  • Advertise only own and customer prefixes.
  • Provide 24x7 NOC contact capable of technical support.
  • Accept that AS216078 may selectively withdraw prefixes to protect service quality.
  • Dual-stack (IPv4 & IPv6) is preferred.
  • Provide maintenance notifications in advance.
  • RPKI invalid prefixes will not be accepted; MANRS encouraged.

Legal Requirements

Trivox does not require contracts for peering sessions and will not enter into one for public peering. Trivox reserves the right to decline or remove peering relationships at its discretion.

Last updated: 20 February, 2026