Is Netlify down?

Understanding Netlify availability

Netlify is a cloud platform for deploying and serving websites and web applications. Its dashboard, account actions, builds, deployments, site delivery, custom domains, and application features can fail independently.

A site that does not load does not automatically mean Netlify is down. A failed build, incorrect publish settings, application error, DNS or nameserver problem, certificate mismatch, redirect loop, or local connectivity issue can affect one site while the wider platform remains available.

Check the official Netlify status page for current incidents and maintenance notices. Then compare the status information with the scope of the problem:

• Dashboard or deployment failures: Check for a platform incident, then review build output, repository settings, environment variables, account access, and project configuration.
• One site failing while other sites work: Start with that project’s latest deploy, runtime behavior, domain configuration, DNS, and application responses.
• Several sites or dashboard functions failing: Check the official status page and test from another device or network to distinguish a broader incident from local connectivity trouble.
• A custom domain failing while the dashboard works: Investigate DNS, TLS, redirects, hostname configuration, and the application separately from Netlify’s general availability.

The most useful first distinction is whether the failure affects Netlify itself, one project, one domain, one account, or only your current browser or network.

Troubleshooting Netlify problems

1. Check for a wider Netlify incident

Open the official Netlify status page and look for an incident or maintenance notice matching the symptom and time. If a matching incident is active, avoid repeated deploys and unrelated configuration changes. Save the error details and retry after the reported issue is resolved.

If no matching incident is listed, continue with project, account, browser, and network checks. A normal status page does not rule out a project-specific failure.

2. Dashboard or deployment failures

• Refresh the dashboard, then try a private window or another browser to rule out stale session data and extensions.
• Check whether the failure affects one site or multiple sites in the same account.
• Review the latest build and deploy output. Start with the first source, dependency, environment-variable, command, or configuration error rather than only the final summary.
• Confirm the intended repository revision, branch, build command, publish directory, and environment settings.
• If a deploy succeeded but old content is still visible, verify the selected deploy, branch, and domain before rebuilding. Caching or opening a different site address can make a successful deploy appear ineffective.

3. Deployed-site HTTP errors

• 500 Internal Server Error: Investigate the site or application response and the latest deployment. A 500 from one project does not by itself show that Netlify is down. See [HTTP 500 Internal Server Error](/guide/http-500-internal-server-error).
• 502 Bad Gateway: Check whether a function, upstream server, proxy, or application dependency is responding correctly. Compare results from another network and review relevant deploy or runtime logs. See [HTTP 502 Bad Gateway](/guide/http-502-bad-gateway).
• 503 Service Unavailable: Check the official status page, then determine whether the error affects one site, endpoint, or several Netlify functions. See [HTTP 503 Service Unavailable](/guide/http-503-service-unavailable).
• 504 Gateway Timeout: Investigate a slow or unreachable upstream dependency. A timeout can occur even when Netlify is operating normally. See [HTTP 504 Gateway Timeout](/guide/http-504-gateway-timeout).

4. Custom domain, DNS, or certificate problems

First determine whether the deployed site fails everywhere or only through the custom domain. Check the hostname spelling, DNS records, nameservers, certificate warning, and redirect destination. Record existing DNS values before changing them; repeated edits can make propagation and cached results harder to interpret.

• DNS_PROBE_FINISHED_NXDOMAIN or a similar name-resolution error usually points to DNS delegation or missing records. See [DNS_PROBE_FINISHED_NXDOMAIN](/guide/dns-probe-finished-nxdomain).
• DNS_PROBE_FINISHED_BAD_CONFIG points toward resolver or DNS configuration. See [DNS_PROBE_FINISHED_BAD_CONFIG](/guide/dns-probe-finished-bad-config).
• A certificate or hostname warning requires checking whether the requested hostname matches the configured domain and certificate. See [ERR_CERT_COMMON_NAME_INVALID](/guide/err-cert-common-name-invalid).
• Repeated HTTP or HTTPS redirects require checking redirect rules and whether multiple layers are forcing different schemes or destinations. See [ERR_TOO_MANY_REDIRECTS](/guide/err-too-many-redirects).

5. Browser, local network, and account scope

• Try a private window or second browser. If the problem disappears, clear site data and disable extensions in the affected browser.
• Test the same dashboard or site from mobile data or another trusted network. If only one connection fails, investigate local DNS, VPN, proxy, firewall, or router settings.
• If multiple unrelated websites fail on the same connection, troubleshoot that network before changing the Netlify project.
• If public visitors can load the site but you cannot open the dashboard or deploy, check the intended account, authentication state, permissions, and project selection. This pattern is more consistent with account or project access than public site delivery.

6. API and automation failures

The service record does not provide a separate Netlify API domain, so do not assume that a dashboard issue and an API issue are the same incident. For an automation failure, record the endpoint used by the integration, response status, authentication result, request time, and whether a manual dashboard action works. Never include access tokens or other credentials in a report.