May <var data-var='date'>23</var>, <var data-var='time'>14:52</var> UTC Investigating - 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 Build Failures

May <var data-var='date'>19</var>, <var data-var='time'>23:04</var> UTC Resolved - 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 May <var data-var='date'>19</var>, <var data-var='time'>22:14</var> UTC Monitoring - 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 May <var data-var='date'>19</var>, <var data-var='time'>21:52</var> UTC Update - 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 May <var data-var='date'>19</var>, <var data-var='time'>21:45</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'>19</var>, <var data-var='time'>21:33</var> UTC Update - 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. May <var data-var='date'>19</var>, <var data-var='time'>21:08</var> UTC Investigating - 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.

Elevated response times affecting origin services

May <var data-var='date'>19</var>, <var data-var='time'>20:41</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>20:23</var> UTC Monitoring - We have resolved the issue causing elevated error rates in the Create API. Systems are now recovering, and we are monitoring closely. May <var data-var='date'>19</var>, <var data-var='time'>18:18</var> UTC Investigating - 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

Degraded performance with Create API

May <var data-var='date'>19</var>, <var data-var='time'>17:30</var> UTC Resolved - 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

Elevated Build and Functions Deployment Errors

May <var data-var='date'>19</var>, <var data-var='time'>14:52</var> UTC Resolved - The incident with performance degradation for create.netlify.com has be resolved. May <var data-var='date'>19</var>, <var data-var='time'>14:37</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>19</var>, <var data-var='time'>14:31</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>19</var>, <var data-var='time'>14:26</var> UTC 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.

May <var data-var='date'>15</var>, <var data-var='time'>18:58</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>15</var>, <var data-var='time'>17:44</var> UTC Monitoring - A fix has been implemented, and we are monitoring the results. May <var data-var='date'>15</var>, <var data-var='time'>16:23</var> UTC Identified - 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.

Purges are Delayed on Primary Load Balancer

May <var data-var='date'>12</var>, <var data-var='time'>15:38</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>12</var>, <var data-var='time'>15:20</var> UTC Monitoring - We have implemented a fix and are monitoring system performance to ensure services continue to recover as expected. May <var data-var='date'>12</var>, <var data-var='time'>14:30</var> UTC Investigating - 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.

Increased Latency in API & Builds

May <var data-var='date'>11</var>, <var data-var='time'>15:27</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>11</var>, <var data-var='time'>15:19</var> UTC Update - We are continuing to monitor for any further issues. May <var data-var='date'>11</var>, <var data-var='time'>14:47</var> UTC Monitoring - We are monitoring the results of our fix. May <var data-var='date'>11</var>, <var data-var='time'>14:10</var> UTC Identified - We have identified other causes of this latency, and are continuing to work on resolutions. May <var data-var='date'>11</var>, <var data-var='time'>13:47</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>11</var>, <var data-var='time'>13:36</var> UTC Investigating - We are currently experiencing increased latency in our API and builds. We are investigating the source.

Latency in API & Builds

May <var data-var='date'>11</var>, <var data-var='time'>15:27</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>11</var>, <var data-var='time'>15:20</var> UTC Update - We are continuing to monitor for any further issues. May <var data-var='date'>11</var>, <var data-var='time'>14:47</var> UTC Monitoring - We are monitoring improvements. May <var data-var='date'>11</var>, <var data-var='time'>14:35</var> UTC Identified - The issue has been identified and posted on Github's status page. May <var data-var='date'>11</var>, <var data-var='time'>14:31</var> UTC Investigating - We are experiencing issues with our build pipeline due to degraded performance in Github

Build Issues due to Github Outage

May <var data-var='date'>10</var>, <var data-var='time'>16:33</var> UTC Resolved - Our network experienced degraded service in the IAD region between 12:53 UTC and 13:53 UTC. This issue is now resolved.

Degraded Service in IAD Region

May <var data-var='date'>10</var>, <var data-var='time'>08:56</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>10</var>, <var data-var='time'>08:55</var> UTC Update - We are continuing to monitor for any further issues. May <var data-var='date'>10</var>, <var data-var='time'>08:32</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>10</var>, <var data-var='time'>08:07</var> UTC Identified - 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 DNS Resolution Errors

May <var data-var='date'>10</var>, <var data-var='time'>08:21</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>10</var>, <var data-var='time'>07:15</var> UTC Investigating - We are seeing an increase in Agent Runner failures for both initial and follow-up prompts. We are currently investigating this issue.

Increase in Agent Runner Errors

May <var data-var='date'> 9</var>, <var data-var='time'>00:58</var> UTC Resolved - 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.

Issues Processing Account Changes

May <var data-var='date'> 8</var>, <var data-var='time'>04:00</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>02:53</var> UTC Investigating - 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 in IAD region

May <var data-var='date'> 6</var>, <var data-var='time'>16:49</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 6</var>, <var data-var='time'>15:39</var> UTC Monitoring - We've implemented a fix and have begun to see improvement starting at 15:15 UTC. We're continuing to monitor the results. May <var data-var='date'> 6</var>, <var data-var='time'>15:29</var> UTC Investigating - We're experiencing elevated errors and latency starting at 15:00 UTC. We are currently investigating this issue.

Elevated Errors and Latency

May <var data-var='date'> 5</var>, <var data-var='time'>23:12</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>21:58</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 5</var>, <var data-var='time'>20:53</var> UTC Investigating - We are investigating increased Agent Runner failures affecting builds for some newly created projects. We will share updates as we learn more.

Agent Runner failures on new projects

May <var data-var='date'> 3</var>, <var data-var='time'>00:00</var> UTC Resolved - 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.

Delayed Credit Usage Updates

Apr <var data-var='date'>26</var>, <var data-var='time'>03:55</var> UTC Resolved - 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

Apr <var data-var='date'>24</var>, <var data-var='time'>14:57</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>24</var>, <var data-var='time'>14:44</var> UTC Monitoring - We've confirmed that Image CDN errors have decreased, and we are continuing to monitor this issue. Apr <var data-var='date'>24</var>, <var data-var='time'>14:10</var> UTC Investigating - We are currently experiencing an elevated error rate for Image CDN requests, starting at 13:35 UTC. We are investigating this issue.

Increased Errors on Image CDN

Apr <var data-var='date'>23</var>, <var data-var='time'>17:23</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>23</var>, <var data-var='time'>17:13</var> UTC Monitoring - 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. Apr <var data-var='date'>23</var>, <var data-var='time'>16:23</var> UTC Investigating - 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.

Elevated Rate of Build Failures

Apr <var data-var='date'>13</var>, <var data-var='time'>01:16</var> UTC Resolved - 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. Apr <var data-var='date'>13</var>, <var data-var='time'>01:04</var> UTC Monitoring - 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 Apr <var data-var='date'>13</var>, <var data-var='time'>00:39</var> UTC Investigating - 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.

Scheduled Functions Auto-Triggering Not Executing

Apr <var data-var='date'> 9</var>, <var data-var='time'>18:00</var> UTC Resolved - 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.

Issues with credit purchases and auto top-ups

Apr <var data-var='date'> 6</var>, <var data-var='time'>09:30</var> UTC 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.

Agent Runners Outage

Apr <var data-var='date'> 2</var>, <var data-var='time'>17:59</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'> 2</var>, <var data-var='time'>15:34</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'> 2</var>, <var data-var='time'>14:19</var> UTC Update - We are continuing to investigate this issue. Apr <var data-var='date'> 2</var>, <var data-var='time'>14:19</var> UTC Update - We're also experiencing errors on the High Performance Edge Network. We're investigating the issue. Apr <var data-var='date'> 2</var>, <var data-var='time'>12:26</var> UTC Investigating - We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be unaffected.

Increased errors on the CDN

Mar <var data-var='date'>30</var>, <var data-var='time'>21:09</var> UTC Resolved - 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. Mar <var data-var='date'>30</var>, <var data-var='time'>19:38</var> UTC Monitoring - 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. Mar <var data-var='date'>30</var>, <var data-var='time'>12:59</var> UTC Update - 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. Mar <var data-var='date'>30</var>, <var data-var='time'>11:20</var> UTC Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'>30</var>, <var data-var='time'>08:48</var> UTC Investigating - We are investigating an issue where environment variables were not being read at runtime for some sites. We will provide an update shortly.

Is Netlify down?

Netlify status is DEGRADED

Components with issues

Lastest published events

Elevated Build Failures

Elevated response times affecting origin services

Degraded performance with Create API

Netlify Services, Components and Regions

Recent Netlify events

Elevated Build Failures

Elevated response times affecting origin services

Degraded performance with Create API

Elevated Build and Functions Deployment Errors

Degraded performance with Create API

Purges are Delayed on Primary Load Balancer

Get your FREE account now,
5 monitors included!

Is Netlify down?

Netlify status is DEGRADED

Components with issues

Lastest published events

Elevated Build Failures

Elevated response times affecting origin services

Degraded performance with Create API

Netlify Services, Components and Regions

Recent Netlify events

Elevated Build Failures

Elevated response times affecting origin services

Degraded performance with Create API

Elevated Build and Functions Deployment Errors

Degraded performance with Create API

Purges are Delayed on Primary Load Balancer

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!