Edge delivery and automatic rollback

Every published site is served through a global content delivery network whenever possible, so a visitor's browser talks to the server closest to them rather than a single, far-away location. This happens automatically - there is nothing to turn on.

How it works

A site becomes eligible for edge delivery the moment it is published (or re-published, if it was created before this feature existed). Once eligible, both the pages and every asset (images, scripts, styles) are answered directly at the edge, with the same caching rules as before: pages refresh within about a minute of a new publish, while unchanged assets stay cached far longer.

A site stays on the regular delivery path instead of the edge when:

• It hasn't been published since edge delivery became available - the very next publish switches it over.
• It uses the zero-setup development storage backend rather than the production file store.
• It's reached through a verified custom domain rather than the default addresses.

None of this changes how a site behaves - forms, page views, contact forms and everything else work identically either way. You can check a site's current delivery mode in Settings › Sites, under Edge delivery.

Automatic rollback

If a fresh publish starts producing a burst of errors - well beyond what the site normally sees - the previous, working version is restored automatically within minutes, before most visitors ever notice. The site's owner is notified when this happens, and the affected version is flagged so it's easy to tell it caused trouble the next time you look at it.

This only kicks in for a version published in roughly the last half hour, requires a meaningful number of real errors (not just one or two), and won't flip a site back and forth more than once an hour. It requires the SRE Agent add-on, which is what detects the errors in the first place.

Automatic rollback is on by default for every site and can be turned off per site in Settings › Sites, under Edge delivery, where you'll also find a short history of any rollbacks that have happened.

Status badge

Every site's public status badge (/status.svg under the site's own address) now also shows its typical response time alongside its up/down status, so you can embed a quick health indicator anywhere.