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 September 2026 it is on the air and dual-stack: an IPv6 block and an IPv4 block, both announced, signed where the registry allows it, and reverse-DNS delegated for IPv6. The routing and DNS story will keep growing here.

Autonomous System AS219158 stat.ripe.net ↗

IPv6 allocation 2a06:9801:f11::/48 65,536 × /64

IPv4 allocation 44.30.210.0/24 256 addresses · 44Net · bgp.tools ↗

Registry RIPE NCC IPv4 via ARDC (44Net)

Status Announced since 2026-08-16 · bgp.tools ↗

Where it lives

Fremont upstream AS212895 Route64 · live

Frankfurt upstream AS209533 iFog · standby

Kansas City upstream AS209533 iFog · live

Manchester upstream AS209735 Lagrange · live

Three of the four are WireGuard tunnels to a friendly upstream; the Manchester box is a native session. Los Angeles is the preferred door, through Fremont; the other sites announce with a longer path so they take over rather than compete. Manchester carries what it announces over a private link back to Los Angeles — a site that announces a block has to be able to forward traffic for it, or it becomes a hole rather than a door. Frankfurt is on standby while its host is unwell. A /56 of the IPv6 block is routed home over WireGuard, so the LAN has real addresses too.

Running on it

IPv4: 44.30.210.0/24 from ARDC ↗, the amateur-radio 44Net space, announced from the same AS — so the network answers on the old internet as well as the new one.
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.
RPKI, IPv4: none, and none is possible — 44Net is ARIN legacy space, which the registry does not issue RPKI certificates for. The IRR route object is the only origin proof, so some networks accept it and some do not.
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

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.