Netlify not working

Updated 11 October 2026

Short answer

First check Netlify's status page for incidents. Then check your site's deploys: if the latest one failed, your site is still on the previous version, or nothing if it never deployed. A very common Netlify problem is a single-page app (React, Vue) that works from the homepage but shows "Page not found" when you refresh another page: Netlify needs a rewrite rule that sends every route to index.html. If your custom domain doesn't load but the .netlify.app address does, it's DNS.

What's the problem

Your Netlify site won't load, shows "Page not found", shows an old version, or works on .netlify.app but not your domain.

Why it happens

  • A Netlify incident.
  • The latest deploy failed, so changes aren't live. See Netlify build failed.
  • No rewrite rule for a single-page app, so routes other than / return 404 on refresh.
  • Your domain's DNS doesn't point to Netlify, or the domain expired.
  • Serverless functions failing or timing out.

How to fix it

  1. Check Netlify's status page.
  2. Check the deploys list for a failed latest deploy.
  3. For single-page apps, add a rewrite in _redirects: /* /index.html 200.
  4. If .netlify.app works but your domain doesn't, check the domain's DNS records. See domain not working.
  5. For function errors, check the function logs in Netlify.

What Preventionlabs checks

One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; uptime checked every 5 minutes, with an email when the site goes down and when it is back; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them; your DNS: nameservers, addresses, DNSSEC, and records pointing at services that no longer exist; your domain's registration and expiry date. It has no connection to your host, so check the host's status page and logs as well.

Run your free report

Your first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.

Sources

  1. Netlify: Netlify Statusstatus pageGet email notifications whenever Netlify creates , updates or resolves an incident.
  2. Netlify: Rewrites and proxiesofficial docsThis can be useful for single page apps, proxying to other services, proxying to other Netlify sites (internal rewrites), or transitioning for legacy content.
  3. Netlify: Rewrites and proxiesofficial docsThis will effectively serve the index.html instead of giving a 404 no matter what URL the browser requests.

Related

Netlify build failed Read the deploy log from the first error. Usual causes: the build command, a missing environment variable, a different Node version, or the repo link. 404 Not Found The page doesn't exist at that address. Usually a deleted or moved page, a typo in a link, or a site migration that broke URLs. Fix the link or add a redirect. Domain not working Check three things in order: the domain hasn't expired, its nameservers are the ones you expect, and its DNS records point at your current host. Vercel error Vercel's error page shows a code like FUNCTION_INVOCATION_FAILED or DEPLOYMENT_NOT_FOUND. It says whether your function crashed, timed out, or is missing.

Preventionlabs is independent and not affiliated with Netlify. Product names are used only to describe the problem.

← All of Hosting