Is Fastly Down?

No — Fastly is up

Fastly's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 236 ms

Right now

We could not read Fastly's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

fastly.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 236 ms
Checked: 2 hours ago

By region

Ashburn reachable, 98 ms
Frankfurt reachable, 98 ms
Johannesburg reachable, 260 ms
London reachable, 82 ms
Los Angeles reachable, 241 ms
Newark reachable, 90 ms
São Paulo reachable, 329 ms
Tokyo reachable, 694 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	41 ms	6 ms	13 ms	76 ms
Frankfurt	78 ms	1 ms	4 ms	93 ms
Johannesburg	248 ms	1 ms	4 ms	256 ms
London	54 ms	2 ms	5 ms	73 ms
Los Angeles	218 ms	2 ms	5 ms	233 ms
Newark	66 ms	3 ms	4 ms	82 ms
São Paulo	316 ms	0 ms	4 ms	324 ms
Tokyo	290 ms	71 ms	73 ms	508 ms

We check that fastly.com loads, not every feature behind it. Test it yourself

History

Fastly website availability

Measured by FlareWarden · fastly.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 806ms

Last 30 days

65-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of fastly.com from multiple regions every 6 hours. Fastly's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 65 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Cloudflare

Akamai

AWS

Bunny.net

Fastly outage FAQ

My site is down but my origin server is fine. Is Fastly the cause?

That combination points at the delivery layer. Fastly sits in front of your origin, so an edge failure produces errors for visitors while your servers report normal health and see reduced traffic. Check www.fastlystatus.com for the point of presence serving your visitors, and compare against a request that bypasses the cache.

A colleague says the site works for them. Does that rule out a Fastly outage?

No, and this is the most common misreading. Fastly publishes status per point of presence, so an incident in one city affects only visitors routed there. Someone in another region reaches a different location entirely and sees a healthy site. Ask where the person testing from is located before concluding the problem is local to you.

What do Fastly's status labels actually mean?

Fastly uses its own vocabulary rather than the common one. Degraded means the network or a component is delivering customer traffic at reduced capacity, and Unavailable means a portion is not operational. Informational means something is posted for awareness with no components affected. Reading Degraded as a full outage will make you fail over when you did not need to.

Can I still push configuration changes during a Fastly incident?

Not always, and it is reported separately. Fastly lists the control panel and its configuration management API apart from delivery, so pushing a new service version can fail while traffic is being served normally. If that is the affected row, avoid repeated deploy attempts and wait, since a partially applied configuration is harder to reason about than a delayed one.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Fastly itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Fastly goes down

We check Fastly every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required