Jun 4, 20:59 UTC
Resolved - This incident has been resolved. Between approximately 17:00 and 20:30 UTC, a subset of sites using Edge Functions experienced elevated 504 error rates. We applied a mitigation and error rates have remained at normal levels since. We apologize for  the impact to your sites and visitors.

Jun 4, 20:42 UTC
Monitoring - We have applied a mitigation and error rates for affected sites have returned to normal levels as of approximately 20:30 UTC. We are continuing to monitor the situation and will provide a final update once we have confirmed full recovery

Jun 4, 20:34 UTC
Identified - We have identified an issue with a subset of our Edge Functions infrastructure causing elevated 504 errors for some sites beginning at approximately 17:00 UTC. We are applying mitigations and error rates are improving. Customers do not need to take any action. We will continue to provide updates here.

Jun 4, 20:24 UTC
Investigating - Our team is investigating an increase in observed error rates affecting a subset of sites that use Edge Functions. Affected sites may see elevated 504 responses or slow page loads beginning at approximately 17:00 UTC. We are actively working to  identify the cause and will provide updates here.

May 29, 15:30 UTC
Resolved - Between May 29th at 15:30 UTC till June 2 6:08 UTC, we experienced sporadic issues with Blobs in our Sydney region, affecting any Function using Blobs, including the ones that are generated by the framework runtimes. Our team has deployed a fix and the errors have subsided.

May 27, 14:17 UTC
Resolved - This incident has been resolved, and builds have returned to functioning normally.

May 27, 12:58 UTC
Identified - In addition to delayed builds, we are also experiencing build failures due to the current incident at Github.

May 27, 12:13 UTC
Investigating - We are currently experiencing delays in our build pipeline due to a current incident at Github.

May 26, 13:44 UTC
Resolved - This incident has been resolved.

May 26, 13:23 UTC
Monitoring - 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.

May 26, 13:14 UTC
Investigating - 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.

May 25, 17:32 UTC
Resolved - This incident has been resolved.

May 25, 15:53 UTC
Monitoring - 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

May 25, 15:31 UTC
Identified - 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

May 23, 19:40 UTC
Resolved - This incident has been resolved.

May 23, 14:52 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.

May 19, 23:04 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 19, 22:14 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 19, 21:52 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 19, 21:45 UTC
Update - We are continuing to investigate this issue.

May 19, 21:33 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 19, 21:08 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.

May 19, 20:41 UTC
Resolved - This incident has been resolved.

May 19, 20:23 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 19, 18:18 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

May 19, 17:30 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

May 19, 14:52 UTC
Resolved - The incident with performance degradation for create.netlify.com has be resolved.

May 19, 14:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

May 19, 14:31 UTC
Identified - The issue has been identified and a fix is being implemented.

May 19, 14:26 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.