Is Fastly Down?
Reachable from all 8 checked regions
Average response time: 286ms
Last checked · checks run every 6 hours
Official status page: https://www.fastlystatus.com
Fastly uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
19-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Fastly does
Fastly is an edge cloud platform that caches and delivers websites, APIs and video from points of presence close to the user, with a programmable configuration layer and edge compute. Large publishers, retailers and software companies put it in front of their origin servers, so a Fastly problem shows up as the site itself failing rather than as a third-party feature breaking.
What an outage looks like
Sites behind Fastly return errors or time out while the origin server is healthy, and the failure often tracks geography rather than account. Fastly reports individual points of presence by city, so users routed through one location see errors while everyone else is unaffected. Configuration pushes and the control panel are reported separately, so deploys can fail while delivery is normal.
What to do about it
Read www.fastlystatus.com and check the specific point of presence your traffic uses rather than the headline. Fastly marks a component Degraded when traffic is still served at reduced capacity and Unavailable when it is not, so the wording tells you whether to wait or fail over. Fastly reroutes traffic away from a failed location, so many incidents resolve without any change from you.
Is it down for everyone, or just you?
If this page says Fastly is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
Fastly outage FAQ
My site is down but my origin server is fine. Is Fastly the cause?
A colleague says the site works for them. Does that rule out a Fastly outage?
What do Fastly's status labels actually mean?
Can I still push configuration changes during a Fastly incident?
How we measure this
- We request Fastly's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Fastly publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Fastly goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring