Peering Policy

We do open, settlement-free bilateral peering — each side announces only its own prefixes. Transit is available on request. If you operate a network and want to exchange routes, reach out and we'll most likely say yes.

Prefixes

Everything we announce and how it's split up inside. You'll only see the covering prefixes in the routing table.

2a06:9801:15b2::/48IPv63 subnets

2a06:9801:15b2::/64: Anycast services
2a06:9801:15b2:100::/56: ams-1 — Amsterdam
2a06:9801:15b2:200::/56: waw-1 — Warsaw

Locations / PoPs

Amsterdam and Warsaw are virtual PoPs, so we peer over a tunnel or an exchange.

Amsterdam: Virtual PoP — LowPing NL — Nikhef — 1 Gbps
Warsaw: Virtual PoP — MatHost.eu — Atman WAW-1 — 2 Gbps

Internet exchanges

Where to find us on a peering LAN.

Piter-IX Frankfurt: 31.44.187.143

Upstreams

LowPing NL: AS215296
MatHost.eu: AS214762

Services

ns1.as210880.net DNS: 2a06:9801:15b2::53
ns2.as210880.net DNS: 2a06:9801:15b2::54
ntp.as210880.net NTP: 2a06:9801:15b2::123
ip.as210880.net Your IP address: 2a06:9801:15b2::80
as210880.net This website: 2a06:9801:15b2::443
AS112 node Reverse DNS sink for private address space: 2620:4f:8000::/48

Connection methods

GRE tunnel — for remote peering.
WireGuard tunnel — for remote peering.

Requirements

A public ASN and at least one globally routable prefix.
Registered route / route6 objects in a recognised IRR database.
Valid ROAs — RPKI-invalid routes are dropped.
Announce only your own prefixes (and your downstreams') — no bogons, no default routes, no full table.
BFD is appreciated and supported on most sessions.
Keep your PeeringDB entry up to date.

Routing policy

We validate RPKI and reject invalids.
We filter bogon ASNs and bogon / martian prefixes.
IPv6 prefixes accepted between /32 and /48, within 2000::/3.
Traffic engineering is available via BGP large communities — see the communities page.

Example configuration

A bare-minimum IPv6 session to start from. AS64500, the 2001:db8::1 address and the 2001:db8:100::/48 prefix are made up, so swap in your own, plus the session addresses we settle on.

protocol bgp as210880 {
    local 2001:db8::2 as 64500;
    neighbor 2001:db8::1 as 210880;

    ipv6 {
        import where net ~ [ 2a06:9801:15b2::/48 ];
        export where net ~ [ 2001:db8:100::/48 ];
    };
}

Request peering

Fill this in and we'll get back to you by email.

Contact

General / Peering: [email protected]
NOC: [email protected]
Abuse: [email protected]

Network details