Netlify change history
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Error accessing Netlify-hosted sites Errors affected access to Netlify-hosted sites across Edge Functions, High-Performance Edge Network, and Standard Edge Network in a major-impact outage starting 2026-09-24 19:01 UTC. Netlify reported normal operation at 2026-09-24 19:10 UTC and resolved the incident at 2026-09-24 19:25 UTC; the recorded duration was 23 min. | Major incident | |
| Major incident: Errors accessing Netlify-hosted sites Netlify reported a major outage affecting access to Netlify-hosted sites on the High-Performance Edge Network and Standard Edge Network; customers could also experience issues accessing the Netlify application and its features. It started at 2026-09-21 15:12 UTC and was resolved at 2026-09-21 16:37 UTC, lasting 1 h 24 min. Netlify reported implementing a fix. | Major incident | |
| Critical incident: Elevated HTTP 500 errors serving sites and the Netlify UI Netlify recorded a critical incident starting at 2026-08-18 20:00 UTC, with a computed duration of 0 min and status resolved. Its update reports error pages for some Netlify-hosted site visitors and dashboard users between 20:02 and 20:08 UTC, with normal service restored at 20:08 UTC. | Major incident | |
| Major incident: Elevated Build Errors Netlify reported major elevated build errors affecting the Build Pipeline, with errors beginning at 8:58 UTC and the incident recorded from 2026-08-03 09:31 UTC. A fix was implemented, and the incident was resolved at 2026-08-03 09:55 UTC; the recorded duration was 24 min. | Major incident | |
| Major incident: Elevated error rates for a subset of sites using Edge Functions Netlify reported a major Edge Functions incident causing elevated 504 errors and slow page loads for some sites beginning approximately 17:00 UTC. The recorded incident started at 2026-06-04 20:24 UTC, lasted 34 min, and resolved at 2026-06-04 20:59 UTC. Mitigation restored normal error rates around 20:30 UTC; no customer action was required. | Major incident | |
| Major incident: Failed & delayed builds due to Github incident Netlify’s Build Pipeline experienced delayed and failed builds due to a GitHub incident, with impact rated major. The incident ran from 2026-05-27 12:13 UTC to 2026-05-27 14:17 UTC, lasting 2 h 4 min; Netlify reported builds had returned to normal. | Major incident | |
| Major incident: Support Communication Delivery Issues Netlify reported a major outbound email delivery outage affecting some services, including Netlify Helpdesk support communications, from 2026-05-25 15:31 UTC to 2026-05-25 17:32 UTC (2 h 0 min). Delivery was restored at 15:53 UTC, though queued emails could still be delayed; Netlify worked with its email provider during recovery. | Major incident | |
| Critical incident: Elevated response times affecting origin services Netlify reported a critical incident affecting Build Pipeline, Netlify Application UI, and Netlify Functions, with latency, errors, intermittent site unavailability, and builds failing to start or delayed. It started at 2026-05-19 21:08 UTC and was resolved at 2026-05-19 23:04 UTC, lasting 1 h 55 min. Netlify implemented mitigation and confirmed normal operation. | Major incident | |
| Major incident: Latency in API & Builds Netlify reported a major incident causing increased latency in its API and Build Pipeline from 2026-05-11 13:36 UTC to 2026-05-11 15:27 UTC, lasting 1 h 51 min. Fixes were implemented and monitored before resolution; customers could experience slower API responses and builds during this period. | Major incident | |
| Critical incident: Agent Runner failures on new projects Netlify reported a critical Agent Runners outage affecting builds for some newly created projects, starting 2026-05-05 20:53 UTC and lasting 2 h 19 min. A fix was implemented by 2026-05-05 21:58 UTC, and the incident was resolved at 2026-05-05 23:12 UTC. | Major incident | |
| Major incident: Scheduled Functions Auto-Triggering Not Executing Netlify reported a major Netlify Functions outage: some Scheduled Functions did not auto-trigger, while manual “Run now” executions worked. The incident ran from 2026-04-13 00:39 UTC to 2026-04-13 01:16 UTC (37 min), though Netlify said symptoms began around April 12, 2026 at 1:00 AM UTC. A deployed fix restored scheduled invocations. | Major incident | |
| Major incident: Environment Variables Issues Netlify reported a major incident where some sites could not read environment variables at runtime, affecting Build Pipeline, Edge Functions, and Netlify Functions. It was recorded as starting and resolving at 2026-03-30 21:09 UTC (computed duration: 0 min). Netlify deployed a fix automatically to impacted sites; customers did not need to take action. | Major incident |