stance
Nightcoil Networks runs three live dual-stack points of presence in Europe — Manchester, Frankfurt, Amsterdam — announcing an IPv6 /48 and a leased IPv4 /24, multi-homed across three transit providers plus one public exchange. The ASN, prefixes, routing objects, and peering policy are all published below.
Cross-edge visibility is carried by a full-mesh iBGP over WireGuard overlay. Anycast public services (looking glass, whois, AS info card) are bound to a shared IPv6 /128 that is present on every edge — clients are routed to whichever edge is topologically closest.
The scope is small on purpose.
footprint
- Locations
- 01 — Manchester, GB (edge-mnc-1, live)
02 — Frankfurt, DE (edge-fra-1, live)
03 — Amsterdam, NL (edge-ams-1, live) - Autonomous system
- AS218652
- Address space
- 2a06:9801:1561::/48 (IPv6, RIPE-allocated)
201.7.23.0/24 (IPv4, leased via IPbnb / BR RIPE, current trial term through 2026-10-21) - RIR
- RIPE NCC (ASN and IPv6 prefix); IPv4 originated on lease
- Geographic scope
- Europe
- Public exchanges
- FogIXP main fabric + FogIXP AMS (v6-only, RS-transparent) at edge-ams-1
- Facilities
- None owned — hosted at upstream / provider PoPs
routing
Every announced route walks the same four-step path from origin to edge.
- 01
- Origin Prefixes 2a06:9801:1561::/48 (IPv6) and 201.7.23.0/24 (IPv4) originate from AS218652. Single origin, single maintainer NIGHTCOIL-MNT.
- 02
- Validate RPKI ROAs cover both prefixes at tight max-length (48 for the /48, 24 for the /24, per RFC 9319). IRR route6 and route objects filed under RIPE::AS218652:AS-NIGHTCOIL.
- 03
- Select Upstream applies IRR-filtered import. Prefix accepted only when origin and ROA agree.
- 04
- Deliver Transit via AS209735 (Lagrange, Manchester), AS52025 (Paradox / GetVPS, Frankfurt) and AS34927 (iFog, Amsterdam). Public exchange peering at FogIXP main + FogIXP AMS. Cross-edge visibility via iBGP full mesh over WireGuard.
topology
Logical view. Lines show peering relationships, not physical fibre paths.
verification
Check AS218652 without taking our word for it. Every claim above resolves to a public record.
- Autonomous system — RIPE aut-num AS218652
- IPv6 prefix registration — RIPE inet6num 2a06:9801:1561::/48
- IPv6 route object — RIPE route6 2a06:9801:1561::/48 AS218652
- IPv4 route object — RIPE route 201.7.23.0/24 AS218652
- IRR as-set — RIPE::AS218652:AS-NIGHTCOIL
- Organization — ORG-NNL52-RIPE
- Peering directory — PeeringDB asn/218652
- Route visibility — bgp.tools/as/218652
- RIS routing status — RIPEstat AS218652
- Live BGP state — lg.as218652.net (anycast looking glass)
- Canonical RPSL dump — whois.as218652.net
- AS info card — as218652.net
- Public RPKI validator — rpki.nightcoil.net (Routinator, anycast HTTPS + RTR :3323)
- Public latency grapher — smokeping.nightcoil.net (multi-POP SmokePing, probes from mnc1/fra1/ams1)
- ASN inspector — asn.nightcoil.net (RIPEstat + PeeringDB + local Routinator RPKI)
- TLS inspector — tls.nightcoil.net (handshake, full chain, CT history)
- Peering policy — nightcoil.net/peering
posture
- Addressing
- IPv4 + IPv6 unicast
- Validation
- RPKI ROV signed & monitored (both families)
- Route control
- IRR-filtered import, tight ROAs, BCP38 egress
- Peering
- Open, dual-stack, no ratio, no contract
- Redundancy
- Multi-home across three transit upstreams (AS209735, AS52025, AS34927) + FogIXP main & AMS
- Anycast
- IPv6 /128 anycast ingress on all three edges for public services (looking glass, whois, AS info card, RPKI validator)
contact
Mail lands with the engineer operating the network.
- Peering
- [email protected]
- Abuse
- [email protected]
- General
- [email protected]