Live Domain Check

Is Netlify Down? Check netlify.com Status and Outages

Run a live reachability check for netlify.com. Compare the regional responses with the problem you see in Netlify.

Find Netlify 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 Netlify 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 Netlify connection and service problems

The Netlify dashboard, a deployment build and the delivered site can fail separately.

The checker above requests netlify.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Netlify action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

Looking for another service? Browse developer service checks.

Netlify status information and official help

Netlify service status

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

Netlify help and reporting

Platform deployment errors and application build errors need different evidence.

Open netlify.com

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

Where to report problems with Netlify

Open Netlify 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

Site/deploy ID, commit, custom-domain result, failing build/function step and time.

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

What to check when Netlify is not working

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

Start with the action that failed

Compare the site's Netlify deployment address with its custom domain and inspect the latest build state.

Narrow down the affected service

Identify whether the failure is compilation, deployment publication, functions or serving before triggering another deploy.

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 Netlify is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the netlify.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 Netlify 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 Netlify Is Not Working Only For You, Start Here

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

1. Compare browser sessions

Open netlify.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 Netlify 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 Netlify support.

Frequently asked questions about Netlify problems

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

Run the netlify.com check and compare its original timestamps and responses with your actual error. The Netlify dashboard, a deployment build and the delivered site can fail separately.

Where can I report a problem with Netlify?

Use the community buttons on this page to share whether the service works for you. For help from Netlify, use the official help/reporting resource linked above. Platform deployment errors and application build errors need different evidence.

What should I check first when Netlify is not working?

Compare the site's Netlify deployment address with its custom domain and inspect the latest build state. Identify whether the failure is compilation, deployment publication, functions or serving before triggering another deploy.

What information helps Netlify support investigate?