There were 22 Netlify outages since February 6, 2026 totaling 16h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some customers may have seen delayed credit usage updates and related notifications between 00:14–01:37 UTC on May 3. The issue has been resolved, and usage information is now up to date.
We experienced an elevated rate of errors on the Image CDN across Standard as well as High Performance Edge Networks. The errors started around 03:55 UTC. The recovery began around 04:55 UTC.
We are currently experiencing an elevated error rate for Image CDN requests, starting at 13:35 UTC. We are investigating this issue.
We've confirmed that Image CDN errors have decreased, and we are continuing to monitor this issue.
This incident has been resolved.
We're experiencing an increased rate of build failures beginning around 16:00 UTC, caused by a GitHub issue: https://www.githubstatus.com/incidents/myrbk7jvvs6p. We're currently investigating this issue.
We've confirmed a decrease in the rate of build failures, which coincides with GitHub's restoration of impacted services. We are continuing to monitor this issue.
This incident has been resolved.
Investigating an issue affecting Scheduled Functions auto-triggering. Manual “Run now” executions are succeeding, but some scheduled functions are not automatically invoking at their expected times.Beginning around April 12, 2026 at 1:00 AM UTC and are actively investigating.
We implemented a fix for the issue affecting Scheduled Functions auto-triggering and are seeing signs of recovery. Manual executions were unaffected during the incident, and scheduled invocations now appear to be resuming. We are continuing to monitor closely
This incident has been resolved. A fix was deployed for the issue affecting Scheduled Functions auto-triggering, and scheduled invocations have recovered. During the incident, manual executions continued to work, but some scheduled runs did not trigger automatically as expected.
between 17:40 UTC and 18:10 UTC, some customers may have experienced failures when purchasing credits or updating auto top-ups. This issue has been resolved.
Between 08:50 UTC and 09:41 UTC, Agent Runner experienced an outage caused by an issue with a third-party dependency. Customers may have experienced failures or degraded performance when running agents during this period. The issue has been resolved.
We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be unaffected.
We're also experiencing errors on the High Performance Edge Network. We're investigating the issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue where environment variables were not being read at runtime for some sites. We will provide an update shortly.
The issue has been identified and a fix is being implemented.
We've identified the issue and applied a fix. No new sites are affected by the issue and we are applying a fix for previously affected customers.
We’ve identified the root cause of the environment variables issue affecting some sites and have deployed a fix. The fix is now live, and impacted sites should have automatically received it. Customers do not need to take any further action. We’ll keep monitoring our channels for any additional reports. If you continue to experience issues, please contact support.
We’ve deployed a fix for the environment variables issue affecting some sites, and this all sites have received this fix as of 4:45pm UTC 3-31.
From 16:30 UTC, we observed increased errors for Edge Function invocations on the Standard Edge Network. This includes framework generated Edge Functions like Next.js Middleware. The issue has been resolved as of 16:52 UTC.
We experienced an increased number of delayed cache purges on both the Standard and HP Edge Networks between 22:30 and 0:10 UTC. We have deployed a fix and are currently monitoring the results.
This incident has been resolved.
Between 21:08 and 21:22 UTC, there was an increase in errors and latency on the Standard Edge Network.
We are currently experiencing elevated rates of Edge Function errors on the Standard Edge Network since 13:38-14:07 UTC. We are investigating the cause.
A fix has been implemented and we will continue to monitor the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're investigating an increase in errors on the High Performance Edge Network in Mumbai (BOM) region since 3 AM UTC.
This incident has been resolved.
We are experiencing high latencies in our origin. This may cause high error rates and elevated response times, as well as build failures. We are currently investigating.
The issue has been identified and we are working on a resolution.
A fix has been implemented and we are monitoring the results.
We continue to investigate this rise in latencies creating high error rates.
We are continuing to investigate this issue
We are continuing to investigate this issue.
The cause of the issue was identified, and we are monitoring the fix that was applied.
We are continuing to monitor for any further issues.
This incident has been resolved.
Between February 25 until March 4, we saw an increased number of edge function errors related to requests with larger payloads on some sites on the standard network. This has been resolved.
Beginning at 23:58 UTC, we began seeing an increased rate of delayed builds for plans on the Free tier. We are currently investigating this issue.
A fix has been implemented, and we are monitoring the results.
This incident has been resolved.
We experienced increased latency on app.netlify.com between 20:04 and 20:40 UTC. This incident is resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
Between 12:00 UTC and 12:28 UTC our Origin showed query contention that caused higher latencies and elevated error rates impacting different components like Origin Servers, Build Pipleine, API and UI utilization.
We're currently investigating an issue with Live Tunnel.
This incident has been resolved.
We're currently experiencing an elevated rate of deploy failures. We are investigating this issue.
We are seeing some improvement, and we're continuing to monitor this issue.
This incident has been resolved.
We're currently investigating an issue where users may see a 404 error when accessing the Netlify App at app.netlify.com Our team is actively working to identify the root cause and restore access as quickly as possible
We've resolved the issue that was causing 404 errors when accessing app.netlify.com The Netlify App is now fully operational. All services are functioning normally
Pingoru polls Netlify's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required