Netlify status · Hosting & Platforms · checked (3m ago)
Operational
No — Netlify is not down. All Netlify systems are reported operational.
According to Netlify's official status page, Netlify was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Netlify's feed reported no outage in 100.00% of our checks.
No outage reported (30d)
100.00%
Share of our checks where Netlify's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
1.22 s
How long the last status check took
Reported by
Operational
All Systems Operational
Is Netlify down for you right now?
Everything above is read from Netlify's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Netlify in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Netlify is
Netlify hosts static sites and frontend applications with a global CDN, plus build and deploy automation, serverless functions, edge functions, forms and identity.
What Netlify's status feed covers
Netlify's status page separates the build system, the CDN that serves finished sites, functions and the API. The distinction that matters most: a build outage stops new deployments but leaves already-deployed sites serving normally, so most Netlify incidents are invisible to a site's actual visitors.
One bar per day. Each shows the share of that day's checks where Netlify's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Netlify was down.
2026-08-2530 of 30 days recordedToday
No outage reported (99%+)
95–99%
80–95%
Under 80%
No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 3m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Netlify's status endpoint.
Netlify outage history
Netlify has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Netlify posted itself — not every problem users hit.
No — Netlify is not down. All Netlify systems are reported operational. Checked (3m ago).
What is Netlify's status right now?
Netlify is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 1.22 s. isuptime reads this from Netlify's own published feed and does not test Netlify independently.
When did Netlify last go down?
The most recent incident Netlify published was “Errors accessing Netlify-hosted sites”, opened Sep 21, 03:12 PM UTC (2d ago) and marked resolved Sep 21, 04:37 PM UTC. That is the latest entry in Netlify's own incident feed, not every problem users experienced.
What is Netlify's uptime?
isuptime does not measure Netlify's uptime directly — it reads Netlify's own published status feed. Over the last 30 days, Netlify's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is Netlify down for everyone?
Netlify reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Netlify says operational but it is not working for me
Check the deploy log — a failed build is far more often a dependency, a Node version mismatch or a missing environment variable than a Netlify problem. If the site loads but a route 404s, that is usually a missing redirect rule for client-side routing. Build minutes and bandwidth limits stop things without any incident being posted.
