Live Domain Check

Is Cloudflare Workers Down? Check workers.cloudflare.com Status and Outages

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.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

Understanding Cloudflare Workers connection and service problems

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.

Cloudflare Workers status information and official help

Cloudflare Workers service status

Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.

Cloudflare Workers help and reporting

Select the affected Cloudflare product; account support options depend on role and plan.

Open workers.cloudflare.com

Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.

Where to report problems with Cloudflare Workers

Select the affected Cloudflare product; account support options depend on role and plan.

Open Cloudflare Workers help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.

Details to include in your report

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.

What to check when Cloudflare Workers is not working

These are troubleshooting comparisons, not claims that Cloudflare Workers is currently experiencing a particular incident.

Start with the action that failed

Compare the deployment endpoint with the custom-domain route and inspect a failing request in your Worker logs.

Narrow down the affected service

Separate deployment rejection, runtime exception and upstream fetch failure before rolling back code.

Read the actual checker response

A 403 or 429 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.

How to check if Cloudflare Workers is down

Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
Run the workers.cloudflare.com check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
Compare the relevant provider information. Open Cloudflare Workers status and check whether the named service and incident time fit your error.
Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.

If Cloudflare Workers Is Not Working Only For You, Start Here

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.

1. Compare browser sessions

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.

2. Preserve a working account session

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.

3. Compare permitted network paths

Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Cloudflare Workers support.

Frequently asked questions about Cloudflare Workers problems

Is Cloudflare Workers down, or is the problem limited to one feature?

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.

Where can I report a problem with Cloudflare Workers?

Use the official help/reporting resource linked above. Select the affected Cloudflare product; account support options depend on role and plan.

What should I check first when Cloudflare Workers is not working?

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.

What information helps Cloudflare Workers support investigate?

Worker/service name, deployment version, route, request time, error and available Ray/request ID.