Is Cloudflare Workers down right now?

No. Our checks are finding no problems with Cloudflare Workers right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Cloudflare Workers 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, API errors, 5xx error pages, no response / timing out, high latency, can't connect and webhooks not firing. Those are the options the report button offers for Cloudflare Workers, 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 Cloudflare Workers specifically, the runtime, the deployment API and the storage bindings are separate, and a Worker runs in every Cloudflare location independently. The colocation serving you can be unhealthy while the rest of the network is fine, so your Worker fails for you and succeeds for someone else. 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 Cloudflare Workers, call your Worker from another network or from a machine in a different region. Errors from everywhere point at the Worker or the platform; errors only from where you are point at that colocation or your own network path. 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 Cloudflare Workers's side. Specifically: read the error number before assuming an outage. 1101 is an exception your own code threw and 1102 is your CPU time budget, neither of which is Cloudflare. Workers already deployed keep serving while the deployment API is broken. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Cloudflare Workers publishes a machine-readable status feed, so our first check reads it directly and reports what Cloudflare Workers itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. 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 www.cloudflarestatus.com, and it is linked further up this page. That is Cloudflare Workers'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 Cloudflare Workers or workers.cloudflare.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Cloudflare Workers's own support, not us.