CheckWebsiteNow

Live status check

Is Netlify down right now?

We check netlify.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of netlify.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About Netlify problems

Netlify problems can concern deploys that fail, builds that stop, serverless functions or custom domains and DNS. Check the Netlify status page first, then read the deploy log of the affected site in the Netlify dashboard. If only one site fails, its build settings, redirect rules or domain configuration are the likely cause.

Official information

Netlify official status page (verified )

Our check and Netlify's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

Netlify help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical Netlify problems

An editorial list of typical problems, not based on live user reports.

  • Deploys fail A failed Netlify deploy can stop at a build command, a missing dependency or an environment variable, so the deploy log shows the first real error.
  • Page not found A Netlify 404 on a single-page app can mean the fallback rule that sends all paths to index.html is missing, so check the _redirects file or netlify.toml. Guide: 404 Not Found
  • Site redirects in a loop Conflicting Netlify redirect rules, or rules that fight with another service in front of the site, can make it redirect forever, so review the rules and HTTPS settings. Guide: ERR_TOO_MANY_REDIRECTS
  • Custom domain cannot be found A domain that cannot be found may have DNS records or name servers that do not yet point to Netlify, so compare them with the Netlify domain settings. Guide: DNS_PROBE_FINISHED_NXDOMAIN
  • HTTPS certificate is not ready Netlify can only provision the HTTPS certificate once the domain resolves to Netlify, so a certificate name warning points to an unfinished domain setup. Guide: NET::ERR_CERT_COMMON_NAME_INVALID
  • Functions fail or time out If a Netlify function fails, its logs in the Netlify dashboard show whether the code threw an error or ran too long.

General fixes: Cloud and hosting

  1. Read the logs first Cloud dashboards keep logs for each deploy, function or sync. The first error in the log is a good place to start looking for the cause.
  2. Verify the DNS records If a custom domain fails, compare its DNS records with the values the provider shows. DNS changes can take time to reach every network.
  3. Check storage and quotas A full storage plan or a used-up quota stops syncs, uploads and deploys even when the service itself works.
  4. Separate one site from the provider If a single website shows an error page from its hosting or CDN provider, the cause can be that website's own server rather than a problem with the provider for everyone.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.