Cloud & hosting
Is Netlify down?
Live Netlify status, measured independently. We probe 5 Netlify endpoints from monitoring regions on every continent and record every outage we detect.
Netlify is up
Our probes are reaching Netlify normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website100% uptime, 30 days6 regions, 57 to 366 msUnknownp50median response168 msp95slowest 5% of checks330 ms500 ms250024 h ago12 h agonow
- Edge network (docs.netlify.com)99.99% uptime, 30 days6 regions, 76 to 359 msUnknownp50median response190 msp95slowest 5% of checks384 ms500 ms250024 h ago12 h agonow
- App dashboard100% uptime, 30 days6 regions, 63 to 313 msUnknownp50median response163 msp95slowest 5% of checks332 ms500 ms250024 h ago12 h agonow
- API99.99% uptime, 30 days6 regions, 268 to 1288 msUnknownp50median response821 msp95slowest 5% of checks1085 ms2000 ms1000024 h ago12 h agonow
- Official status feed83.24% uptime, 30 days6 regions, 198 to 476 msUnknownp50median response298 msp95slowest 5% of checks493 ms500 ms250024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when Netlify goes down
Follow these 5 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Netlify goes down. They don't count against your monitor quota. Free plan, no card required.
About Netlify outages
Netlify hosts static sites and Jamstack apps with continuous deployment from Git, serverless functions, forms, and identity. Netlify incidents most often affect builds and deploys first, with the CDN staying up, but function and edge incidents hit live traffic directly.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website netlify.com is unreachable. | httpwww.netlify.com | HTTP 200 | 1 min |
Edge network (docs.netlify.com) A site served from Netlify's edge is failing, which points at the hosting network rather than the dashboard. | httpdocs.netlify.com | HTTP 200 | 1 min |
App dashboard The Netlify dashboard is failing. Manual deploys and configuration changes are blocked. | httpapp.netlify.com | HTTP 200 | 1 min |
API The Netlify API is not answering. CLI deploys and build hooks fail. | httpapi.netlify.com/api/v1/sites | HTTP 401 | 2 min |
Official status feed Netlify's status page is unreachable. | httpwww.netlifystatus.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Netlify's official status page.
Recent Netlify outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Netlify is up. Is your Netlify integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Netlify and fail quietly. Here is what teams that rely on Netlify monitor on their side.
Your Netlify-hosted site
Netlify's CDN and your build pipeline fail independently. Probe your production hostname from several regions so a CDN incident is visible immediately.
Uptime monitoringScheduled functions
Netlify scheduled functions have no alerting when they do not run. A heartbeat per schedule closes that gap.
Heartbeat monitoringNetlify status: frequently asked questions
It can be. Netlify's build system is a separate component from its CDN, and incidents that only affect builds are common. Your live site stays served from the last good deploy while new deploys fail.
Look at the per-region results above. If our probes fail from every region, Netlify has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Netlify may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Netlify" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Netlify: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
upti.my is not affiliated with Netlify. Netlify and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.