Infrastructure
Edge map
Nine sites carry this shelf. Bars show each site’s share of shelf traffic over the last thirty days; the figure on the right is its median time to first byte.
Measured from our own probes inside each site’s metro, not from your machine. Treat them as a comparison between sites rather than a promise about your connection.
How a request finds a site
Plain anycast on the front door, then a short internal hop if the nearest site does not have the artifact hot. That second hop is why a cold-storage release feels slow exactly once and fine afterwards.
- Routing
- Anycast. No GeoDNS, no client-side site selection, nothing for you to configure.
- Hot set
- Every release from 5.8.2 up, on local SSD at all nine sites. About 2.4 GiB of the shelf’s 3.1 GiB.
- Cold set
- Older releases, on object storage in Frankfurt and Toronto. First request promotes them to the local hot set for seven days.
- Failover
- A site that fails its own health probe withdraws its announcement; traffic lands on the next one. Nothing is manual.
- TLS
- TLS 1.2 and 1.3 only, terminated at the edge site. Certificates renew on a sixty-day cycle.
Thirty-day record
Known rough edge. Singapore still fetches cold artifacts across the ocean from Frankfurt rather than Toronto, which is the wrong choice for roughly half of its misses. A second cold tier in Asia-Pacific is planned; there is no date on it yet.
We publish the bad numbers alongside the good ones. A status page that is always green is a status page nobody is reading.