Is Netlify Down? How to Check Netlify Status Right Now

Netlify hosts millions of websites and web apps — from personal projects to production-grade frontends used by enterprise teams. When Netlify goes down, sites stop loading, deploys fail, and serverless functions return errors. Here's how to determine if Netlify is the problem and what to watch for.

Is Netlify Down Right Now?

Check these in order:

1. Statusfield — Netlify status — real-time monitoring updated continuously across all Netlify components.
2. Netlify's official status page — netlifystatus.com publishes active incidents and component-level health.
3. Twitter/X — search netlify down sorted by Latest. Developers report build and deploy failures quickly.
4. Netlify Community — community.netlify.com is active; users frequently report production incidents before official acknowledgment.

Netlify Components That Can Fail Independently

Netlify is a platform with distinct services — each can fail without affecting the others:

Component	What breaks when it fails
CDN / Edge Nodes	Deployed sites fail to load for users; 502/503 errors at the domain
Build System	Deploy builds queue but never start, or builds fail at the infrastructure level
Deploy Previews	PR preview environments don't generate or return errors
Functions (Lambda)	Netlify serverless functions return 502; form submissions and API routes break
Forms	Form submissions fail silently or with network errors
Identity	Netlify Identity login/signup flows break; JWT issuance fails
DNS	Custom domain resolution fails for sites using Netlify DNS
Large Media / Git LFS	Large file transforms fail; image CDN returns errors
API	Netlify CLI operations fail; programmatic deploys break

A build system outage doesn't affect live sites — those are served from CDN. But a CDN outage means every visitor gets an error, even though your latest deploy succeeded hours ago.

Common Errors During a Netlify Outage

Error	Likely cause
502 Bad Gateway at your domain	CDN or origin infrastructure degraded
Deploy failed with no log output	Build system infrastructure down
Failed to fetch in browser (Netlify Function)	Functions runtime degraded
NETLIFY_API_ERROR from CLI	Netlify API degraded
Unable to locate the netlify.toml in build	Build system file access issues (rare, but happens during incidents)
Deploy status stuck at "Building" for 20+ minutes	Build queue backlog during CDN incident — builds queued but workers unavailable
Netlify Identity: Failed to load resource: 429	Identity service rate-limited or degraded

Important: Build failures caused by your code show errors in the build log. Build failures caused by Netlify infrastructure often show no log output at all — the job just sits in the queue or exits with an infrastructure error. That's the signal to check Netlify status first.

Why Build Failures Are the Hardest to Diagnose

When Netlify's build system is degraded, deploys queue up but never run. The symptoms look exactly like a slow build or a hung CI step:

1. You push to main, expecting a deploy
2. Netlify shows "Building..." indefinitely
3. You check the build log — no output
4. You retrigger the deploy — same result
5. You start investigating your netlify.toml or build commands — but the issue isn't your config

This debugging loop can cost 30–60 minutes. Checking Statusfield before investigating your code will tell you immediately if Netlify's build infrastructure is the cause.

Netlify Functions (Serverless) During Outages

Teams using Netlify Functions for API routes, form handling, or backend logic are affected differently depending on which Netlify component fails:

• CDN outage: Functions are unreachable — all requests return 502
• Functions runtime outage: CDN responds, but functions return 502 at execution
• Build system outage: Previously deployed functions still run; only new deploys are blocked

If you're using Netlify Functions as a backend for a React or Next.js app, a functions runtime outage means your frontend loads but API calls fail — which often looks like an app bug rather than a platform issue.

Impact on JAMstack and Static Site Deployments

Netlify's CDN is the critical path for JAMstack sites — there's no fallback origin server. Unlike a traditional web server where you can restart NGINX or Apache, a Netlify CDN outage means your site is completely unavailable until Netlify resolves the incident.

Mitigation options teams use:

• Cloudflare in front of Netlify: Cloudflare can cache and serve responses even during a brief Netlify CDN outage, provided the cache is warm
• Multi-CDN strategy: Some teams maintain a secondary deployment on Vercel or Cloudflare Pages as a failover
• Status page for your users: If you use Netlify for a product, having a separate status page (on a different provider) lets you communicate outages to your users even when Netlify is down

How to Get Instant Netlify Outage Alerts

Don't rely on noticing a deploy failure or a user report. The earlier you know, the faster you can communicate to your team and users.

Monitor Netlify on Statusfield — Statusfield polls Netlify's status page continuously and alerts you the moment any component changes. Route alerts to email, Slack, or a webhook into your incident management system.

For teams with on-call rotations: add Netlify to your monitoring stack alongside your application's own uptime checks. A Netlify incident that takes down your frontend is just as urgent as an application error.

Start monitoring Netlify on Statusfield → — free, no credit card required.

---

Frequently Asked Questions

Is Netlify down for everyone or just me?

Check Statusfield or netlifystatus.com. If both show operational but your site is broken, the issue may be your specific site's configuration, a caching problem, or DNS propagation. Try accessing your site via the .netlify.app domain directly (bypassing your custom domain) to isolate the issue.

My Netlify deploy is stuck at "Building" — is this an outage?

Check Statusfield for the build system component. If it shows degraded, your build is queued and will resume automatically when the incident resolves. If Netlify shows healthy, check your build log for errors — a stuck build with no log output that resolves after a cancel/retry is usually a transient infrastructure blip.

Netlify functions are returning 502 — is this an outage?

Check the Functions component on Netlify's status page. A 502 from a Netlify Function can also mean your function is timing out (max 10 seconds on free, 26 seconds on Pro) or throwing an unhandled error. Use Netlify's function logs in the dashboard to distinguish infrastructure vs. code issues.

How do I check if a specific Netlify edge node is down?

Netlify's CDN has global edge nodes. During a partial CDN outage, some regions may be affected while others work normally. If you see errors from specific geographies but not others, check Netlify's status page for edge/CDN component status. Tools like ping and traceroute won't help — the Netlify CDN uses anycast routing.

Can I deploy to Netlify even during a build system outage?

If the build system is down but the API is healthy, you can still do a manual deploy by dragging a build folder into the Netlify dashboard or using netlify deploy --dir=build via the CLI (if you have a pre-built artifact). This bypasses the build system entirely and deploys directly to the CDN.

How often does Netlify go down?

Netlify publishes full incident history at netlifystatus.com. Netlify generally maintains high availability, but build system and CDN incidents do occur. Given that many teams rely on Netlify as their sole deployment target, even short degradations during business hours have meaningful impact.

Published: April 11, 2026. Check current Netlify status →