AS205941

Operations

  • Dashboard
  • Topology
  • Looking Glass
  • NOC

Routing

  • Prefixes
  • Routes
  • Communities
  • Traffic

Network

  • Peering
  • Status
  • API
Status unknown
AS205941/Peering
--:--:-- UTCSite

Peer with AS205941

open policy

We maintain an open peering policy at every exchange where we're present, including via route servers. IPv6-first, RPKI-valid, and MANRS-conformant.

Peering requirements
  • A publicly routable ASN with up-to-date PeeringDB record
  • RPKI-valid announcements (ROAs published)
  • A NOC reachable 24/7 and current IRR objects
  • No point-default routing; consistent announcements across IXes
Where we peer

Frys-IX

RS

Amsterdam, Netherlands · 10G · 9 peers

InterIX

RS

Amsterdam, Netherlands · 10G · 8 peers

KawaiiIX

RS

Amsterdam, Netherlands · 10G · 0 peers

BGPEX

RS

Amsterdam, Netherlands · 10G · 0 peers

NINE

RS

Amsterdam, Netherlands · 10G · 5 peers

PITERIX

RS

Amsterdam, Netherlands · 10G · 4 peers

AMSIX

RS

Amsterdam, Netherlands · 10G · 6 peers

Private peering & transit

We're open to private network interconnects (PNI) at shared facilities where volumes justify it. Reach out with your ASN, traffic profile, and preferred location.

For downstream/transit arrangements, contact .

Request peering

Send a request via the form (pre-filled for peering) or email us directly. We typically respond within two business days.

To: peering@as205941.net
Subject: Peering request — AS<your-asn> <> AS205941

ASN:        AS<your-asn>
Name:       <your network>
Locations:  Frys-IX, InterIX, KawaiiIX, BGPEX, NINE, PITERIX, AMSIX
Max-prefix: v6 <n> / v4 <n>
PeeringDB:  <url>
Open peering formPeeringDB
Peering quick facts
ASN
Policyopen
Max-prefix v65,000
Max-prefix v420,000
MD5Optional
Min speed1G
RPKI validMANRS
View BGP communities