Netlify incident history

Right now: clear, by Netlify's own status page, mirrored every five minutes.

50
incidents kept since 11 Mar 2026
7
in the last 30 days
37m
median time to resolve, once posted
60%
resolved within an hour

How far back this goes: Netlify's feed exposed its 50 most recent incidents when we began mirroring on 25 September 2026, so this page covers 198 days so far and grows from here. Impact labels (13 major or critical) are Netlify's own. We don't compare providers on this page; the windows aren't equal yet.

What our probes saw

No monitor that declares Netlify as a dependency was evaluated during these incidents, so there's nothing to add from our side yet. This fills in as more sites behind Netlify are watched.

Which parts of Netlify the incidents touched

Standard Edge Network
14
Build Pipeline
12
High-Performance Edge Network
12
Agent Runners
7
Edge Functions
6
Netlify Image CDN
6

Every incident we hold, newest first

24 Sept 2026
major
23m 50s
23 Sept 2026
minor
34m 13s
16 Sept 2026
minor
50m 39s
3 Aug 2026
major
24m 44s
1 Jul 2026
minor
24m 53s
26 May 2026
minor
30m
23 May 2026
minor
4h 47m
11 May 2026
minor
56m 9s
11 May 2026
major
1h 51m
10 May 2026
minor
48m 45s
10 May 2026
minor
1h 6m
8 May 2026
minor
1h 6m
6 May 2026
minor
1h 19m
24 Apr 2026
minor
46m 56s
6 Apr 2026
none
—
2 Apr 2026
minor
5h 32m
30 Mar 2026
major
—
24 Mar 2026
minor
1h 2m

Source: Netlify's public status page at www.netlifystatus.com, mirrored every five minutes. Data as JSON: /upstream/netlify/incidents.json. CC BY 4.0.

If your site depends on Netlify, Repose holds the page when the cause is upstream. How the hold decision works →