summary
Nightcoil Networks (AS218652) operates an open peering policy. Peering is offered on a best-effort basis to any network operator that meets a small set of technical requirements. There is no ratio requirement, no contract, and no minimum number of locations.
The network is currently IPv6-only. IPv4 is not carried and will not be exchanged over peering sessions.
network
- AS number
- AS218652
- Address space
- 2a06:9801:1561::/48
- IRR as-set
- RIPE::AS218652:AS-NIGHTCOIL
- PeeringDB
- peeringdb.com/asn/218652
- RIPE handle
- ORG-NNL52-RIPE
- Transit
- AS209735 (Lagrange), Manchester
- 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 for IPv6
- Address family
- IPv6 unicast only
- MD5 / TCP-AO
- Optional; supported on request
- Max prefixes (v6)
- 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.