CheckUpstream measured Netlify at 100.000% availability across 2819 independent checks (global · api). 31 incidents were recorded in the past 12 months; the most recent resolved earlier today after 2 hours. Status signals are polled from Netlify's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2819 · p95 965ms (30d)
Share of our own checks against Netlify endpoints that returned Netlify's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 4 incidents · 29 of 30 days with none posted · 36m of declared impact
Fewer incidents in the last 30 days than 21% of 232 tracked services.
Share of each window with no impact declared by Netlify
7d
99.732%
30d
99.914%
90d
99.971%
180d
99.720%
1y
99.862%
Downtime like this can be refundable
If you're a paying Netlify customer, outages in these windows may count against Netlify's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Netlify entitlement →Does Netlify actually matter to you?
A Netlify outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 31, 20:40 UTC · resolved in 1h 30m · Resolved
Aug 31, 20:40 UTC · resolved in 10m · Resolved
Aug 3, 09:31 UTC · resolved in 39m · Resolved
Aug 3, 09:31 UTC
Live Netlify status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/netlify)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Netlify is currently Operational. CheckUpstream tracks Netlify in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Netlify's last resolved incident started earlier today and lasted 1h 30m (degraded performance).
Looking for the live "is Netlify down" view? See the Netlify Live status page.
May 26, 13:14 UTC · resolved in 35m · Resolved
May 25, 15:31 UTC · resolved in 2h 4m · Resolved
May 23, 14:52 UTC · resolved in 4h 47m · Resolved
May 19, 21:08 UTC · resolved in 2h 1m · Resolved
May 19, 18:18 UTC · resolved in 2h 31m · Resolved
May 19, 14:26 UTC · resolved in 28m · Resolved
May 15, 16:23 UTC · resolved in 2h 37m · Resolved
May 12, 14:30 UTC · resolved in 1h 9m · Resolved
May 11, 14:31 UTC · resolved in 59m · Resolved
May 11, 13:36 UTC · resolved in 1h 54m · Resolved
Netlify's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Netlify endpoints. It is the share of checks that returned the expected response, not a figure taken from Netlify's status page.
Sign up to CheckUpstream and add Netlify to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Netlify's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.