Netlify Outage History
Past incidents and downtime events
Complete history of Netlify outages, incidents, and service disruptions. Showing 50 most recent incidents.
May 2026(19 incidents)
Image Delivery Issues
3 updates
This incident has been resolved.
We have implemented a fix and are monitoring results. Some customers may have experienced slow or failed image requests. We will continue to monitor image delivery and provide an update once the issue is fully resolved.
We are continuing to investigate issues affecting image delivery. Some customers may continue to see slow or failed image requests. We are working to identify the cause and will share more information when available.
Support Communication Delivery Issues
3 updates
This incident has been resolved.
outbound email delivery has been restored and emails are now processing successfully. Some delays may continue while queued messages are delivered. We are continuing to monitor the recovery closely
We are currently investigating an issue affecting outbound email delivery for some Netlify services, including support-related communications. Our team is working with our email provider to restore service as quickly as possible
Elevated Build Failures
2 updates
This incident has been resolved.
We are currently experiencing an increased level of build failures related to downstream issues with GitHub beginning at 06:00 UTC. Any impacted users can attempt to retry their deploys as a workaround while we continue to investigate this issue.
Elevated response times affecting origin services
6 updates
This incident has been resolved. The issue that was causing elevated errors, increased latency, and intermittent site availability across Netlify services has been mitigated. All services, including site delivery and the build pipeline, are now operating normally. We monitored system stability following recovery and are no longer observing elevated error rates or degraded performance
We have implemented mitigation steps for the issue that was causing elevated errors, increased latency, and intermittent site availability issues across Netlify services. Service health has significantly improved, and core functionality such as site loading and build processing is operating normally for most customers. However, we are continuing to monitor closely to ensure full stability and to catch any residual impact
We are continuing to investigate an ongoing incident causing elevated latency, errors, and intermittent failures across multiple Netlify services. Impact remains broad and includes intermittent site availability issues where some customer sites may be unavailable or returning errors, as well as disruptions to the build pipeline where builds may fail to start or be delayed
We are continuing to investigate this issue.
We are continuing to investigate an ongoing incident causing elevated latency, errors, and intermittent failures across multiple Netlify services. In addition to earlier impact, we are now observing issues with the build pipeline where new builds are not starting for some customers. This may result in delayed or failed deploys, in addition to degraded site performance and intermittent timeouts.
We are investigating elevated latency and errors affecting origin services. This is currently impacting request performance and may result in degraded experience or failures for some users.
Degraded performance with Create API
3 updates
This incident has been resolved.
We have resolved the issue causing elevated error rates in the Create API. Systems are now recovering, and we are monitoring closely.
Investigating: We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com
Elevated Build and Functions Deployment Errors
1 update
Between 17:38 and 17:57 UTC, we experienced elevated error rates affecting the Build Pipeline. Some customers may have encountered failed deploys or HTTP 500/503 errors during deployment processing. The systems are recovering and we're continuing to investigate the root cause
Degraded performance with Create API
4 updates
The incident with performance degradation for create.netlify.com has be resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com.
Purges are Delayed on Primary Load Balancer
3 updates
This incident has been resolved.
A fix has been implemented, and we are monitoring the results.
We are currently experiencing a delay in cache purges, and some sites on our Standard Edge Network may be serving stale content. The issue has been identified and a fix is being implemented.
Increased Latency in API & Builds
3 updates
This incident has been resolved.
We have implemented a fix and are monitoring system performance to ensure services continue to recover as expected.
We are currently investigating increased latency affecting our API and build systems. Some users may experience slower-than-normal response times for API requests and builds while we work to identify the source of the issue.
Latency in API & Builds
6 updates
This incident has been resolved.
We are continuing to monitor for any further issues.
We are monitoring the results of our fix.
We have identified other causes of this latency, and are continuing to work on resolutions.
A fix has been implemented and we are monitoring the results.
We are currently experiencing increased latency in our API and builds. We are investigating the source.
Build Issues due to Github Outage
5 updates
This incident has been resolved.
We are continuing to monitor for any further issues.
We are monitoring improvements.
The issue has been identified and posted on Github's status page.
We are experiencing issues with our build pipeline due to degraded performance in Github
Degraded Service in IAD Region
1 update
Our network experienced degraded service in the IAD region between 12:53 UTC and 13:53 UTC. This issue is now resolved.
Increase in DNS Resolution Errors
4 updates
This incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
We're experiencing an increase in DNS resolution errors impacting domains on our Standard Edge Network. A fix has been deployed, and we're monitoring the results.
Increase in Agent Runner Errors
2 updates
This incident has been resolved.
We are seeing an increase in Agent Runner failures for both initial and follow-up prompts. We are currently investigating this issue.
Issues Processing Account Changes
1 update
We experienced issues processing account changes between 19:09 and 19:33 UTC. Users may have encountered issues when attempting to use Agent Runners, purchase credits, view credit usage, or complete account transactions. This issue is now resolved.
Elevated Errors in IAD region
2 updates
This incident has been resolved.
We're seeing an increased level of errors in the IAD region starting around 02:10 UTC for both our Standard and HP Edge Networks due to an upstream issue at AWS: https://health.aws.amazon.com/health/status.
Elevated Errors and Latency
3 updates
This incident has been resolved.
We've implemented a fix and have begun to see improvement starting at 15:15 UTC. We're continuing to monitor the results.
We're experiencing elevated errors and latency starting at 15:00 UTC. We are currently investigating this issue.
Agent Runner failures on new projects
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating increased Agent Runner failures affecting builds for some newly created projects. We will share updates as we learn more.
Delayed Credit Usage Updates
1 update
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.
April 2026(7 incidents)
Increased errors on Image CDN
1 update
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.
Increased Errors on Image CDN
3 updates
This incident has been resolved.
We've confirmed that Image CDN errors have decreased, and we are continuing to monitor this issue.
We are currently experiencing an elevated error rate for Image CDN requests, starting at 13:35 UTC. We are investigating this issue.
Elevated Rate of Build Failures
3 updates
This incident has been resolved.
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.
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.
Scheduled Functions Auto-Triggering Not Executing
3 updates
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.
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
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.
Issues with credit purchases and auto top-ups
1 update
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.
Agent Runners Outage
1 update
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.
Increased errors on the CDN
5 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate this issue.
We're also experiencing errors on the High Performance Edge Network. We're investigating the issue.
We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be unaffected.
March 2026(10 incidents)
Environment Variables Issues
5 updates
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.
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 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.
The issue has been identified and a fix is being implemented.
We are investigating an issue where environment variables were not being read at runtime for some sites. We will provide an update shortly.
Increased errors for Edge Functions on Standard Edge Network
1 update
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.
Delayed Cache Purges
2 updates
This incident has been resolved.
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.
Increased errors and latency on the Standard Edge Network
1 update
Between 21:08 and 21:22 UTC, there was an increase in errors and latency on the Standard Edge Network.
Elevated Edge Function errors on Standard Edge Network
4 updates
This incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we will continue to monitor the results.
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.
Increased errors on High Performance Edge in Mumbai region
2 updates
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.
Service disruption for Netlify application, sites, builds & API
9 updates
This incident has been resolved.
We are continuing to monitor for any further issues.
The cause of the issue was identified, and we are monitoring the fix that was applied.
We are continuing to investigate this issue.
We are continuing to investigate this issue
We continue to investigate this rise in latencies creating high error rates.
A fix has been implemented and we are monitoring the results.
The issue has been identified and we are working on a resolution.
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.
Increased errors for Edge Functions on Standard Edge Network
1 update
From 16:43 UTC to 16:58 UTC, we served HTTP 500 for paths invoking Edge Functions (including framework-generated ones like Next.js Middleware/Proxy). This affected the Free/Starter as well as some part of the Pro tier users on the Standard Edge Network. The issue has since been resolved.
Increased edge function errors errors on Standard Edge Network
1 update
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.
Delayed Builds on Free Accounts
3 updates
This incident has been resolved.
A fix has been implemented, and we are monitoring the results.
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.
February 2026(6 incidents)
Increased Latency on app.netlify.com
1 update
We experienced increased latency on app.netlify.com between 20:04 and 20:40 UTC. This incident is resolved.
Service Disruption
4 updates
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 are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Downtime for Live Tunnel
2 updates
This incident has been resolved.
We're currently investigating an issue with Live Tunnel.
Increase in Deploy Failures
3 updates
This incident has been resolved.
We are seeing some improvement, and we're continuing to monitor this issue.
We're currently experiencing an elevated rate of deploy failures. We are investigating this issue.
Increase in Deploy Failures
4 updates
This incident has been resolved.
We are continuing to monitor this issue.
We are continuing to investigate this issue.
We're currently experiencing an increase in deploy failures due to an issue affecting an upstream provider.
Netlify App (app.netlify.com) Returning 404 Errors
2 updates
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
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
January 2026(8 incidents)
Rendering issues for app.netlify.com
3 updates
The issue was caused by errors relating to a service worker. The solution for the blank page issue is to clear the browser cache on the system where the issue is occurring. This incident is now resolved.
We continue to investigate the issue which appears to be related to a service worker the website uses. If you are seeing a blank page for app.netlify.com clearing the browser cache will resolve the issue.
We are investigating an issue that is causing app.netlify.com to show a blank page for some users.
Increased function Latency
1 update
Between 16:51 UTC and 17:05 UTC we saw increased Function latency on both the High Performance Edge Network and the Standard Edge Network. The issue has been resolved.
Increased errors and latencies in Netlify UI
3 updates
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We're currently experiencing increased errors and latencies in the Netlify UI. We are investigating the problem.
Increased error rates in builds due to issues with upstream provider
2 updates
This incident has been resolved.
We're experiecing increased build failures due to an issue with GitHub: https://www.githubstatus.com/incidents/cqb5hcy0gx18
Service Disruption for Sites using the Standard Edge Network
1 update
Sites using our Standard Edge Network experienced outages on us-east-1 region between 10:42 and 10:52 UTC today. We have identified the source of the issue and it has since been resolved.
Netlify UI unavailable in FRA
1 update
From 08:54 UTC to 09:12 UTC, app.netlify.com was unavailable to users in FRA.
Issue with domain registration renewals
2 updates
We have identified an issue affecting domain renewals for some accounts where payment methods need to be updated. Affected customers have been notified via email with instructions to update their payment information
We are currently investigating an issue that is preventing the renewal of some domains for accounts with payment methods that have not been updated recently.
AI Gateway Experiencing Errors from Upstream Dependency
2 updates
This incident has been resolved.
We're observing Ai gateway errors due to issues with an upstream provider.
📡 Tired of checking Netlify status manually?
Better Stack monitors uptime every 30 seconds and alerts you instantly when Netlify goes down.