summary
Nightcoil Networks (AS218652) operates an open peering policy. We'll peer with any operator that meets the requirements below. No ratio requirement, no contract, no location minimum.
The network is dual-stack: both IPv6 and IPv4 are carried over peering sessions.
network
- AS number
- AS218652
- Address space
- 2a06:9801:1561::/48 (IPv6, RIPE)
201.7.23.0/24 (IPv4, leased via IPbnb / BR RIPE) - IRR as-set
- RIPE::AS218652:AS-NIGHTCOIL
- PeeringDB
- peeringdb.com/asn/218652
- RIPE handle
- ORG-NNL52-RIPE
- Transit
- AS209735 (Lagrange), Manchester
AS52025 (Paradox / GetVPS), Frankfurt
AS34927 (iFog), Amsterdam - Exchanges
- FogIXP main fabric + FogIXP AMS (v6-only, RS-transparent) at edge-ams-1
- Geographic scope
- Europe
requirements
- Register your prefixes in an IRR database (RIPE, RADB, or equivalent).
- Sign your routes with RPKI ROAs where the RIR supports it.
- Announce only prefixes covered by your IRR as-set or ROAs.
- Set reasonable max-prefix limits and honour ours in return.
- Maintain a functional NOC contact reachable by email.
- Provide a 24×7 emergency contact for outages that affect the shared session.
technical
- Protocol
- BGP-4 (RFC 4271) with multiprotocol extensions (RFC 4760) for IPv4 and IPv6
- Address family
- IPv4 unicast + IPv6 unicast
- MD5 / TCP-AO
- Optional; supported on request
- Max prefixes
- Negotiated per peer; sensible defaults on request
- Communities
- Documented on request; BLACKHOLE (RFC 7999) honoured
- Route servers
- Peering via route servers is welcome where available
contact
- Peering
- [email protected]
- Abuse
- [email protected]
- General
- [email protected]
Include your ASN, IRR as-set, expected prefix count, and preferred peering locations in the first message. Sessions are typically configured within one working day.