Netlify Status: How to Check If Netlify Is Down Right Now (2026)
Where to find the official Netlify status page, what each component status means, the build vs. CDN distinction, and how to monitor your Netlify site independently.
Is Netlify Down Right Now?
Check netlifystatus.com for official real-time status. The page covers CDN, Builds, Functions, Edge Functions, API, Forms, and Identity.
Netlify Official Status Page
The official Netlify status page at netlifystatus.com is maintained by Netlify and updated during incidents. It covers all major Netlify services:
Key insight: Netlify's CDN and build pipeline are independent systems. A build outage means deploys are stuck, but your currently-live site continues to serve. A CDN outage is the serious one — that takes your site offline for visitors.
Monitor your Netlify site independently
Better Stack monitors your Netlify site every 30 seconds from multiple global locations. Get instant alerts before visitors report outages, even when netlifystatus.com is delayed.
Try Better Stack Free →Build Pipeline vs CDN: The Critical Difference
The most important Netlify distinction for developers: build failures and CDN failures affect your site very differently.
Build Pipeline Down
- New deploys are stuck or failing
- Your currently-live site continues to work
- Affects: git push deployments, manual deploys, preview URLs
- Urgency: medium — no new code can ship
- Check: Deploys tab in the Netlify dashboard
CDN Down
- Visitors cannot access your site
- Returns 502, 503, or connection timeout
- Affects all sites on Netlify's edge network
- Urgency: critical — user-facing outage
- Check: netlifystatus.com → CDN immediately
Check Netlify Status Programmatically
Netlify's status page is powered by Atlassian Statuspage, which provides a JSON API you can query programmatically:
curl https://netlifystatus.com/api/v2/status.jsoncurl https://netlifystatus.com/api/v2/components.jsoncurl https://netlifystatus.com/api/v2/incidents/unresolved.jsonThe status API returns JSON with indicator values: none (all good), minor, major, or critical. You can poll this API in monitoring scripts or CI/CD pipelines.
How to Check Netlify Status (Step by Step)
Check netlifystatus.com
The official status page. Expand individual components (CDN, Builds, Functions) to see which service is affected — not just the overall indicator.
Go to Netlify Status Page →Check the Netlify Dashboard
Log in to app.netlify.com and check the Deploys tab. Failed or queued builds show up there with detailed error logs. For live site issues, check the Functions logs if using serverless.
Open Netlify Dashboard →Test your .netlify.app URL
Every Netlify site has a .netlify.app subdomain (e.g., yoursite.netlify.app). If your custom domain fails but .netlify.app loads, the issue is DNS, not Netlify CDN.
Check the Netlify Support Forum
Netlify's community forum (answers.netlify.com) is often where users report issues first. Search for recent posts about your specific problem.
Open Netlify Forum →Check Twitter / X for real-time reports
Search "netlify down" on Twitter for real-time user reports. Netlify also posts major incident updates on @Netlify.
Follow @Netlify →What to Do When Netlify Is Down
Immediate Steps
- Check netlifystatus.com to confirm platform-level issue
- Test .netlify.app URL to rule out custom domain DNS issues
- If builds are failing: check build logs for local errors first
- If CDN is down: notify stakeholders, enable maintenance mode
- Subscribe to incident updates on netlifystatus.com
Long-Term Resilience
- Set up independent uptime monitoring (Better Stack)
- Keep build artifacts in CI so you can redeploy to alternatives
- Use a custom domain with fast TTL DNS for easier migration
- Consider multi-cloud: same repo deployable to Vercel as backup
- Set up Slack/email alerts for deploy failures via Netlify notifications
Netlify Uptime — What to Expect
For production sites with real SLA requirements, compare Vercel status guide — Netlify's main competitor for JAMstack hosting. Both offer solid uptime; the CDN architecture is similar.
Monitor your Netlify site availability independently
Better Stack monitors your Netlify site every 30 seconds, independent of Netlify's own status page. Alerts via Slack, email, or PagerDuty when your site goes down.
Try Better Stack Free →Frequently Asked Questions
Where is the official Netlify status page?
Netlify's official status page is at netlifystatus.com. It shows real-time status for all Netlify components including CDN, Builds, API, Netlify Functions, Edge Functions, Forms, Identity, and Large Media. You can subscribe to email or SMS updates directly from the page. For independent monitoring of your deployed site, use apistatuscheck.com or Better Stack.
Why is my Netlify deploy failing?
Netlify deploy failures are usually caused by: (1) A build pipeline incident — check netlifystatus.com for the 'Builds' component, (2) A failing build command in your repo (check build logs in the Netlify dashboard), (3) Missing environment variables — verify them in Site Settings > Environment Variables, (4) A dependency install error — check if package.json changes broke the install step, (5) Build minute limits on free plans. Always check the full build log before assuming a platform issue.
Why are Netlify Functions returning errors?
Netlify Functions (serverless functions) errors are often caused by: (1) A Functions service incident — check netlifystatus.com for 'Netlify Functions', (2) Cold start timeouts — functions time out after 10 seconds (26 seconds on paid plans), (3) Missing environment variables the function depends on, (4) Memory limit exceeded (1 GB max), (5) An error in the function code itself — check function logs in the Netlify dashboard under Functions > Log. Edge Functions and Serverless Functions have separate status components.
What is the difference between Netlify CDN down and builds down?
Netlify CDN down means the static assets of your deployed site aren't being served to visitors — your site is effectively offline. Builds down means new deployments are stuck or failing, but your currently-deployed site on the CDN continues to serve normally. Always check both components on netlifystatus.com: a CDN issue is urgent (users can't reach your site); a build issue is disruptive but your live site remains up.
Why is my Netlify site slow or returning cached old content?
Netlify site slowness is usually CDN propagation or caching behavior. After a successful deploy, new content can take a few minutes to propagate across all CDN edge nodes. If you're seeing old content, try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or test from a different device. For persistent caching issues, check your netlify.toml cache-control headers. A CDN incident on netlifystatus.com would cause widespread slowness across all Netlify sites.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Netlify goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Netlify + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial