Infra

Beyond the pages themselves, Ben runs his own corner of the internet's plumbing — an independent autonomous system: a registered slice of the global routing table, run rather than rented. As of August 2026 it is on the air: the IPv6 block is announced from two places, signed, and reverse-DNS delegated. The routing and DNS story will keep growing here.

Where it lives

Three of the four are WireGuard tunnels to a friendly upstream; the Manchester box is a native session. Fremont is the preferred door for the Americas, the two iFog sessions announce with a longer path and take over if it drops. The two routers that announce the block also talk to each other over a private link, so the whole /48 stays reachable no matter which door traffic comes in. A /56 of it is routed home over WireGuard, so the LAN has real addresses too.

Running on it

• Anycast: 2a06:9801:f11::a is served from Frankfurt and Los Angeles at once; the first thing on it is a mirror of this site ↗ (IPv6 only).

Hygiene

• RPKI: the prefix has a valid ROA for AS219158 (max length /48) — anything else claiming it is invalid.
• IRR: route6 and as-set AS219158:AS-ALL in the RIPE database.
• Reverse DNS: the block's ip6.arpa zone is delegated and answers for the routers.
• PeeringDB: AS219158 ↗, open peering policy.
• Looking glass: see the /48 from hundreds of vantage points on the NLNOG RING looking glass ↗, or the origin's own view on bgp.tools ↗.

What's next

• IPv4: a small legacy block, so the network is reachable from everywhere, not just the IPv6 internet.
• DNS: self-hosted authoritative name service on the allocation, starting with the reverse zone.

Numbers on this page are checkable: the RIPE and bgp.tools links above read the live routing table, not this site.