Netlify statusLiveFetched seconds agoSource: netlifystatus.com
Is Netlify down?
Live status check · All systems operational
Live status pulled from netlifystatus.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Netlify status
Netlify ships static frontends, Edge Functions, Scheduled Functions, and Forms behind a single CDN. The Edge Network is the most user-visible component; outages there make your site look fully down even when builds and APIs are healthy.
Components and surfaces that can break
- Surface 01
Edge Network (the CDN serving *.netlify.app and custom domains).
- Surface 02
Builds, Deploys, and Forms.
- Surface 03
Functions, Edge Functions, and Scheduled Functions.
Recent Netlify incidents
Netlify maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Netlify is actually down
Compare against the Netlify Edge Network indicator
The Edge Network component on the status page is the one that maps to 'visitors see an error'. A red on Builds while Edge Network is green means your site is serving fine; you just can't ship a new deploy.
Re-fire missed Scheduled Functions manually
Netlify Scheduled Functions don't retry. If a run was skipped during the outage, call the function URL once from your terminal (or from an external cron) to bring state up to date.
Switch DNS only as a last resort
Netlify's CDN has good geographic spread. Moving DNS away mid-incident usually causes more problems than it solves; budget at least 30 minutes of monitoring before you start a migration.
Keep firing through the incident
Schedule your own Netlify health check with Crontap
Netlify Scheduled Functions max out at a 30-second execution cap and don't retry on failure. Crontap calls the same function URL on a cron you control, retries 5xx, and stores the response — useful both during outages and for any job that exceeds Netlify's limits.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Netlify status: FAQ
- Is Netlify down for everyone or just my site?
- Open netlifystatus.com and check the Edge Network component. If it's green and your site is broken, the issue is more likely a bad deploy, a misconfigured redirect, or a custom-domain DNS problem. Roll back to the previous deploy from the Netlify dashboard to test that theory quickly.
- Why did my Netlify Scheduled Function not run?
- Scheduled Functions can be skipped during platform incidents and they do not auto-retry. Netlify also caps execution at 30 seconds, so a long job can be killed even when the platform is healthy. External cron with retries solves both cases.
- How do I get an alert when a Netlify endpoint goes down?
- Schedule a Crontap probe against your function URL or homepage on a 1-minute cadence. Crontap emails you on the first failed run, so you usually hear about the issue before the official status page is updated.