Peering

AS401066 operates an open peering policy. If we share an exchange, you can request a session directly through the form below.

For bilateral peering, a private interconnect, or a tunnel session, include your ASN, preferred method, and any technical details. We typically respond within 48 hours.

How to Peer

1

IXP Session

If we are present at the same exchange, request a BGP session through the form below. At most exchanges, route server peering is available.

2

Private Interconnect

For direct peering via cross-connect or fiber, contact us with your location and ASN.

3

Tunnel Session

If there is no shared physical presence, we can set up BGP over GRE or WireGuard.

Peering Policy

General PolicyOpen
Location RequiredNo
Traffic Ratio EnforcedNo
Contracts RequiredNo
IPv6 SupportYes
Route Server PeeringYes (at most IXes)

Request Peering

Fill in the form below or reach out via PeeringDB or [email protected].

Your details are only used to follow up on your peering request.

Technical Requirements

  • ✓Valid IRR route objects for all announced prefixes
  • ✓RPKI-valid or at least RPKI-not-invalid prefixes preferred
  • ✓No default route announcements
  • ✓No bogon prefixes (RFC 1918, RFC 4193, etc.)
  • ✓Max prefix limit: 500 (IPv4), 1000 (IPv6)
  • ✓BGP communities honored where possible
  • ✓MD5 authentication available on request

Exchange Presence

Peering is possible at any of these internet exchanges.

ExchangeIPv4IPv6Speed
nine185.1.14.2062001:7f8:12e::40:1066:110G