Netlify: Third party incident affecting builds
Cloudflare outage, Jul 2, 2019 · 16 vendors, 16 incidents
Netlify’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +1 h 23 min vs the first vendor naming Cloudflare)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>1 vendor, 1 blamed Cloudflare<br/>Wise"]:::blames
root --> h1
h4["1 to 4 hours later<br/>3 vendors, 3 blamed Cloudflare<br/>Optimizely, Discord, Pendo"]:::blames
root --> h4
me["Netlify (this incident)<br/>posted +1 h 23 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
The issue with the third party has been resolved.
From Netlify’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.netlifystatus.com (opens in new tab).