Live Domain Check

Is Cloudflare Pages Down? Check pages.cloudflare.com Status and Outages

Run a live reachability check for pages.cloudflare.com. Compare the regional responses with the problem you see in Cloudflare Pages.

Find Cloudflare Pages 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.

Is Cloudflare Pages working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

Understanding Cloudflare Pages connection and service problems

The pages.cloudflare.com product site does not test your deployed Pages project or custom domain.

The checker above requests pages.cloudflare.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Cloudflare Pages 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 Radar status check, Cloudflare status check, Cloudflare Dashboard status check. Compare results separately; these links do not establish a shared outage.

Looking for another service? Browse developer service checks.

Cloudflare Pages status information and official help

Cloudflare Pages service status

Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.

Cloudflare Pages help and reporting

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

Open pages.cloudflare.com

Open the website in your browser and compare it with the result above.

Where to report problems with Cloudflare Pages

Open Cloudflare Pages 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.

Details to include in your report

Project, deployment/commit ID, custom-domain result, build phase and first relevant error.

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 Pages.

What to check when Cloudflare Pages is not working

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

Start with the action that failed

Compare the project's deployment URL with its custom domain and note whether build, deploy or serving fails.

Narrow down the affected service

Inspect the build log and deployed commit; a framework compilation error is different from a provider-side deployment delay.

Read the actual checker response

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.

How to check if Cloudflare Pages is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the pages.cloudflare.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open Cloudflare Pages status and check whether the named service and incident time fit your error.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

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

Use these local troubleshooting steps after the down-check workflow when Cloudflare Pages seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open pages.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 Pages issue.

3. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

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 Pages support.

Frequently asked questions about Cloudflare Pages problems

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

Run the pages.cloudflare.com check and compare its original timestamps and responses with your actual error. The pages.cloudflare.com product site does not test your deployed Pages project or custom domain.

Where can I report a problem with Cloudflare Pages?

Use the community buttons on this page to share whether the service works for you. For help from Cloudflare Pages, 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 Pages is not working?

Compare the project's deployment URL with its custom domain and note whether build, deploy or serving fails. Inspect the build log and deployed commit; a framework compilation error is different from a provider-side deployment delay.

What information helps Cloudflare Pages support investigate?