Fastly statusManual checkVerified May 24, 2026Source: fastlystatus.com
Is Fastly down?
Live status check · No widespread incident reported.
Most recent manual verification mirrored from fastlystatus.com. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Fastly status
Fastly runs one of the major performance CDNs, plus Compute@Edge (its WebAssembly runtime) and a WAF / bot management layer. Most incidents are scoped to a single POP or a single product, but the 2021 global Fastly outage that took down a large chunk of the web is a reminder that the edge layer can still fail wide.
Components and surfaces that can break
- Surface 01
Per-POP CDN availability across 200+ points of presence worldwide.
- Surface 02
Compute@Edge (the WebAssembly runtime) and Image Optimizer.
- Surface 03
Management plane: the API, the Dashboard, and Fastly Real-Time Stats.
Recent Fastly incidents
Fastly maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Fastly is actually down
Confirm which POPs and products are affected
Fastly's status page splits by POP and by product (Delivery, Compute@Edge, Image Optimizer, API). Run curl -sI against your Fastly-hosted domain and read the x-served-by header to see which POP code your request lands on, then check that row before assuming the whole network is down.
Do not reach for DNS failover unless it's widespread and prolonged
Most Fastly incidents are POP-scoped and resolve inside 30 minutes, while DNS TTL propagation takes longer than that. Switching to a backup origin or another CDN mid-incident usually causes more pain than it saves. Budget at least 30 minutes of monitoring before triggering a migration.
Management-plane outages do not stop your traffic
If the Fastly API or Dashboard is degraded but Delivery is green, your existing config keeps serving from the POPs. You just cannot ship a new VCL or Compute@Edge deploy. Defer config changes instead of fighting the control plane.
Keep firing through the incident
Schedule your own Fastly health check with Crontap
Scheduled cache purge (PURGE all on deploy via the Fastly API), scheduled origin shield warmup, hourly POP health probe via the Fastly Real-Time Stats API. Crontap fires the endpoint that calls Fastly's API on the cadence you set.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Fastly status: FAQ
- Where can I see the official Fastly status?
- fastlystatus.com publishes component status for Delivery, Compute@Edge, Image Optimizer, the API, and the Dashboard, plus per-POP indicators for 200+ sites worldwide. The /incidents page lists open and recent events.
- How do I know which Fastly POPs my traffic actually hits?
- Run curl -sI against your Fastly-hosted domain and read the x-served-by response header. It includes the POP code (for example BWI for Washington, FRA for Frankfurt, LHR for London). Match that POP against the per-POP grid on fastlystatus.com to see whether the current incident is one you actually care about.
- Should I move DNS away during a Fastly incident?
- Almost never. Most Fastly incidents resolve in under an hour, and DNS TTL propagation typically takes longer than the recovery window. Unless the incident is global and prolonged (the 2021-style scenario), waiting it out is faster and less risky than a mid-incident failover.