STATUS IS UPDid you know?
Owner workspace
Explore SIU
  1. Status Is UP
  2. Did you know?
  3. No. 15

Did you know? · No. 15 · Fun fact ·

A valid CDN change once made 85% of Fastly’s network return errors

Card showing “85%” and “of Fastly’s network returned errors after a valid change.”

On June 8, 2021, a Fastly customer made a valid configuration change. It activated an undiscovered software bug, and 85% of Fastly’s network returned errors. Fastly identified the problem, disabled the configuration, and said 95% of its network was operating normally within 49 minutes.

Fastly’s recovery was quick, but this is a useful reminder: a CDN is part of your delivery path, not a guarantee that every page will stay reachable. If a CDN has a broad disruption, visitors can still meet an error unless your site has another route to the origin. For a store, login, checkout, support page, or status page, that can become a business interruption even when your own server is healthy.

Try this on your site

List the pages that must stay reachable, then document how each can bypass your primary CDN to reach the origin. For the most critical pages, evaluate a tested second-CDN route.

Share this fact

Each fact is checked against the primary sources listed. Spotted an error? Email the Status Is UP team. Status Is UP helps owners improve their sites; it is not an uptime monitor. For live outage status, see Status Is Down.