policy
Open peering. AS215932 is happy to peer with anyone meeting the requirements below, at any IXP where we are present or via private interconnection if that is more convenient.
requirements
- Valid, maintained entry in PeeringDB
- IRR objects registered (any recognized IRR)
- RPKI ROAs published for all announced prefixes
- Reachable 24/7 NOC contact
- No default route, no transit leak, no bogons
session defaults
| parameter | value |
|---|---|
| address family | IPv6 unicast (inet6) |
| MD5 / TCP-AO | optional; supported on request |
| max-prefix (v6) | 1000 (soft), warning at 800 |
| BFD | on request |
| multihop | no (direct only) |
| graceful restart | enabled |
ixp presence
Active IXP presences are tracked on PeeringDB — see peeringdb.com/asn/215932 for the authoritative, up-to-date list, including peering LAN addresses and the route-server status.
| IXP | site | IPv6 | route server |
|---|---|---|---|
| SBIX | Zurich | 2001:7f8:d9:1::3:4b7c:2/64 | active |
transit
Current upstreams visible in our configuration:
- AS34872 (Servperso Networks) — NL and DE
- AS210233 — DE
- AS58057 (Securebit) — CH
contact
| NOC email | noc@as215932.net |
|---|---|
| PeeringDB | peeringdb.com/asn/215932 |
| Issues / requests | GitHub issues (label: peering) |
what to send
When you reach out, please include:
- Your ASN and a link to your PeeringDB record
- IXP(s) or private location where you want to peer
- Expected prefix count and whether you want a max-prefix bump
- Any non-default knobs you want (MD5, BFD, extended communities)