Machine room
The infrastructure map
The whole site, as it answers right now. Measured, not drawn.
The map and the diagram are drawn by your browser from four calls made while you look at the page: the edge tells which data centre answered you, the machine Worker tells which bindings are on, a measurement shows where the D1 database and the archive cabinet’s Durable Object live, and the counting works show where today’s guests came in. No IP address, city or cookie is stored.
The edge
The page is built in whichever Cloudflare data centre is closest to you. The same data centre runs both Workers; the call between them is a service binding that never touches the internet.
D1
The database has one primary copy in a particular place. The answer shows the region (e.g. WEUR, western Europe) and, when Cloudflare reports it, the data centre and whether it was the primary or a replica.
Durable Objects
The archive cabinet is one object that lives in one place: a data centre in the EU, because it is fetched with the eu jurisdiction. The object finds its own data centre by asking Cloudflare where its own call left the network.
What is not measured
Workflows, Browser Run, Analytics Engine and Rate Limiting are not called by the map, because they cost money or take time. They show as on when the binding exists in the machine Worker right now.
The family: The defences·The crawlers·The speed·Denmark right now·The archive cabinet·The door·The infrastructure map·The audit·Back to the machine room
Have a useful idea?
Feature requests, bug reports and questions are welcome. Every message gets a personal reply.