Netlify status: is it down right now?
Our own check of netlify.com from Europe and the US, every 3 minutes, with recent history.
netlify.com responded. The page answered normally in 1462 ms.
netlify.com responded.
The page answered normally in 1462 ms.
Checked (2 minutes ago) from Europe and the US, automatic every 3 minutes.
Run a website? Hear about it before your visitors do.
Netlify is up right now. Visual Sentinel watches your own site the same way and alerts you when a check fails or the page looks broken. Add your address and we'll check it now. No account needed.
This checks the response from netlify.com. It does not test playback, login or every Netlify feature.
Netlify status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 12. A problem has to fail two checks in a row before we record it.
Watch your own site
This page is for their outage. Your own site can fail the same way. See its first check free, then try a paid plan for 7 days (card required).
Monitor my siteabout this service
About Netlify
Netlify is a JAMstack hosting platform with features for static-site deploys, Netlify Functions (serverless), Netlify Edge Functions, Forms (form submissions), Identity (auth), Analytics, and DNS. The platform is popular among Next.js, Gatsby, Eleventy and Hugo users. Outages typically affect build/deploy (deploys queue or fail), the edge network (user-facing latency spikes or 5xx), Functions (API routes fail), or the dashboard. Build-system outages are the most common incident class, and during high-traffic release windows (marketing campaigns, product launches) the deploy queue can be critical. Netlify DNS incidents are more severe because they break domain resolution entirely.
The official Netlify status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours.
outage patterns
How Netlify outages affect production workloads
Developer-platform outages have outsized impact because they cascade. When Netlify is degraded, every customer's build pipeline, deploy hook, or webhook delivery can stall, and the failure mode often looks like a customer problem before engineers realize the dependency is the cause. CI runs hang, status checks never report, and queued jobs pile up silently.
The live check above provides independent public-endpoint evidence from EU and US, including status and response timing. That helps separate a broad reachability problem from a local client issue, but it does not execute your private API call, build, webhook, or deploy. Test the exact dependency path before attributing the incident to Netlify.
Common signs Netlify is having issues
- API rate limits returning earlier than the documented thresholds
- Webhook deliveries showing 5xx errors or unusual latency tail
- Deploy or build hooks accepted by Netlify but never firing downstream
- OAuth or token endpoints failing intermittently for the same client credentials
What to do when Netlify is degraded
When Netlify is having trouble, the fastest mitigation is usually feature-flagging the dependency off if your application can degrade gracefully. Check the multi-region results on this page first; if both regions report healthy but your application still sees failures, the issue is likely your network path or DNS, not Netlify itself.
monitor 24/7
Monitor Netlify automatically.
Get independent alerts when the public Netlify endpoint fails a confirmed check. Solo and Starter check every 5 minutes; Business and Agency check every 60 seconds.
5-minute checks from Solo
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Alerts where you work
Email and push on every plan, plus team and incident channels by plan.
free first check · 7-day trial, card required · from $15/month
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Netlify on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Netlify uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Netlify down right now?
See the latest check of netlify.com and its timestamp at the top of this page. If Netlify is down, you can also check the official status page for extra context.
How do I check if Netlify is having issues?
This page checks the public Netlify endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Netlify goes down?
Add netlify.com to Visual Sentinel and its first check is free. To keep monitoring, start a 7-day trial (card required) or subscribe now: Solo and Starter check every 5 minutes, Business and Agency every 60 seconds, with email, push and chat alerts.
Where can I find Netlify outage context?
The official Netlify status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Visual Sentinel checks the public Netlify endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Will existing Netlify sites stay up during a deploy outage?
Yes. Existing deployments are served from the edge network, which is independent of the build system. A build outage queues new deploys but does not affect production traffic on the last-good build.
Does a Netlify Functions outage break the whole site?
Only if the site depends on Functions for core features (API routes, auth, dynamic content). Purely static sites continue to work. Sites mixing static content with server-side Functions see partial degradation.
Often checked together with Netlify
Development tools depend on each other. A failing build or editor plugin is not always the tool you opened.