Cloudflare Workers service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for workers.cloudflare.com. Compare the regional responses with the problem you see in Cloudflare Workers.
Find Cloudflare Workers help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
A Workers product-site check does not execute your Worker or validate a route on your custom domain.
The checker above requests workers.cloudflare.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Cloudflare Workers action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Separate a Cloudflare dashboard issue from a developer-product entrypoint using these related checks: Cloudflare Pages status check, Cloudflare Radar status check, Cloudflare status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse developer service checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Select the affected Cloudflare product; account support options depend on role and plan.
Open the website in your browser and compare it with the result above.
Open Cloudflare Workers help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Worker/service name, deployment version, route, request time, error and available Ray/request ID.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Cloudflare Workers.
These are troubleshooting comparisons, not claims that Cloudflare Workers is currently experiencing a particular incident.
Compare the deployment endpoint with the custom-domain route and inspect a failing request in your Worker logs.
Separate deployment rejection, runtime exception and upstream fetch failure before rolling back code.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Cloudflare Workers seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open workers.cloudflare.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Cloudflare Workers issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Cloudflare Workers support.
Run the workers.cloudflare.com check and compare its original timestamps and responses with your actual error. A Workers product-site check does not execute your Worker or validate a route on your custom domain.
Use the community buttons on this page to share whether the service works for you. For help from Cloudflare Workers, use the official help/reporting resource linked above. Select the affected Cloudflare product; account support options depend on role and plan.
Compare the deployment endpoint with the custom-domain route and inspect a failing request in your Worker logs. Separate deployment rejection, runtime exception and upstream fetch failure before rolling back code.
Worker/service name, deployment version, route, request time, error and available Ray/request ID.