DoubleZero Atlas

Where multicast feeds enter the network, and how far they reach · Independent, not affiliated with DoubleZero

Reading the globeWhat the dots, rings, lines, labels and times mean

Each glowing dot is a metro where a feed’s publishers attach to DoubleZero and report BGP Up. Each ring is a metro where its receivers attach, and a dashed ring means accounts are registered there but none report Up. A reach line joins every ingress metro to every receiver metro in the same family. Multicast carries every publisher’s packets to every subscriber, so each line is a real reach. The ledger holds no per-feed path, though, so a line is a great circle lifted off the surface, not a fiber route.

The labels beside the globe name each metro with its counts: IN for publishers and OUT for receivers reporting Up. In Wavefront, a receiver’s label adds the time light in fiber needs to reach it from the nearest ingress metro. Select a label or a dot to pick out that metro’s lines and open its sites and devices in the Metros panel.

Farthest receiver is the receiver metro that sits farthest from its nearest ingress metro, measured along the great circle. The time after it is how long light in fiber needs over that distance, about 204 km per millisecond. Real paths are longer, so read it as a lower bound. It doesn’t mean that receiver gets its data from that ingress. The ledger doesn’t record which publisher wins.

Race against compares DoubleZero with other ways to get the same feed, using DoubleZero’s public scoreboards: the venue’s own feed and, for Hyperliquid, three competitors the scoreboard leaves unnamed. At each receiver site with results, a hollow silver ring follows DoubleZero’s tip along a dashed trail and arrives later by the median lead measured there over the last 24 hours. The silver times are the fiber lower bound plus that measured lead, not end-to-end measurements. Win % is the share of races in which DoubleZero delivered first. Only Hyperliquid and Phoenix have results so far.

Locations are DoubleZero attachment metros, not publisher hosts or matching engines. Counts are accounts reporting Up in the snapshot.

MethodHow ledger records become metros
  1. GroupRead every multicast group from the public mainnet-beta ledger, without a wallet or subscription.
  2. AccountMatch each group’s address to the publishers and subscribers lists on user accounts.
  3. DeviceFollow each user to the DoubleZero device it attaches through.
  4. MetroFollow the device to its location and exchange records, which supply the metro name and coordinates.
  5. StatusRead the stored BGP status, and count only accounts reporting Up as live points.

All feedsEvery multicast group, with its publishers and receivers

Up counts, with registered totals after the slash. Select a row to draw its family on the globe. The per-feed atlas draws each group on its own.

SourcesThe ledger snapshot, code and reference data