Peering Policy

We maintain an open and collaborative peering approach to ensure optimal network performance

Open Peering Policy

AS50124 operates an open peering policy. We believe in fostering strong interconnection relationships with networks of all sizes. Whether you're a content provider, eyeball network, or fellow transit operator, we welcome peering discussions.

Network Information

ASN Details

Autonomous System:
AS50124
IRR Object:
Loading...
PeeringDB:
View Profile

IP Resources

IPv4 Max Prefixes:
Loading...
IPv6 Max Prefixes:
Loading...

Peering Requirements

Technical Requirements

  • • Valid AS number registered with a RIR
  • • Publicly routable IPv4 and/or IPv6 address space
  • • Up-to-date PeeringDB record
  • • 24/7 NOC reachable via email and phone

Security & Routing

  • • RPKI ROA validation enabled
  • • IRR objects properly maintained (RADB, RIPE, etc.)
  • • BGP session protection (MD5 authentication recommended)
  • • Maximum prefix limits enforced

Operational Standards

  • • Minimum traffic exchange of 100 Mbps
  • • Mutual benefit and fair traffic ratio
  • • Participation in relevant IXP communities
  • • Prompt response to operational issues

Where We Peer

Internet Exchange Points

Loading IXP data...

Private Network Interconnects

We offer PNI peering for networks with significant traffic volumes (>3 Gbps) at our datacenter locations:

  • Digital Realty PAR5 Paris
  • Equinix PA6 Paris

Routing Policy

We Announce

Our own prefixes and customer routes. We do not announce transit provider routes or other upstream networks.

We Accept

Your prefixes and customer routes. We filter based on IRR/RPKI and enforce minimum prefix lengths (/24 for IPv4, /48 for IPv6).

We Filter

Default routes, bogons, private address space, and invalid RPKI routes. We also implement max-prefix limits.

Ready to Peer?

Contact our peering team to discuss establishing a BGP session. We typically respond within 24 hours.