Is Fastly down right now?

No. Our checks are finding no problems with Fastly right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Fastly continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, DNS / site unreachable, 5xx error pages, high latency, slow or laggy, can't connect, API errors and SSL / certificate errors. Those are the options the report button offers for Fastly, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Fastly specifically, Fastly serves from points of presence worldwide and you hit the nearest, so an unhealthy one affects your city and nobody else's. Their edge also surfaces origin failures as its own errors, so a 503 is frequently the customer's origin rather than Fastly. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Fastly, load the same site from another network and over mobile data. Failing everywhere points at the site or Fastly; failing from one network points at the point of presence serving you, which the response headers normally name. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Fastly's side. Specifically: avoid mass-purging your cache. A full purge sends every request straight to an origin that is already struggling, which turns an edge problem into an origin outage. Serving stale content is the better lever if your configuration allows it. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Fastly does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe fastly.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Fastly says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.fastly.com, and it is linked further up this page. That is Fastly's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Fastly or fastly.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Fastly's own support, not us.