Is Netlify Down Right Now? Check if there is a current outage ongoing.

We're currently investigating reports of sites being unresponsive/down in AU region. Sites on our Standard Edge Network are affected, High Performance Edge does not seem to be impacted.

We're currently experiencing an increase in 502 errors and issues accessing app.netlify.com. We're currently investigating this issue.

We are currently investigating reports of issues with our ImageCDN.

Starting at 17:00 UTC, customers using extensions in the UI may see errors or be unable to load extensions or their configuration pages. We are currently investigating this issue.

We're investigating issues authenticating with our build API

After monitoring the applied fix, we can confirm this issue resolved.

A fix has been implemented, this is now resolved. We will continue to monitor.

We are working with our backend provider we have identified the issue and are rolling out a fix.

We are continuing to investigate the issue with adding new cards in the UI.

We are currently experiencing difficulties with adding new credit cards in the UI.

We are currently experiencing difficulties with adding new credit cards in the UI.

This incident has been resolved.

Customers may sporadically encounter "Error enqueueing build" messages for GitHub-triggered builds due to an intermittent GitHub issue; please retry your build if you see this error.

Customers may sporadically encounter "Error enqueueing build" messages for GitHub-triggered builds due to an intermittent GitHub issue; please retry your build if you see this error.

The incident is resolved.

The root cause has been identified and a solution has been implemented. We are monitoring to confirm the resolution.

The app.netlify.com site is down. Hosted sites are not impacted. We are working to identify the cause now.

The app.netlify.com site is down. Hosted sites are not impacted. We are working to identify the cause now.

The incident is resolved.

We have a solution for this issue and a new deploy is required to enable it. If you are seeing function errors, please make a new deployment of your site.

We're seeing increased function invocation errors beginning at ~13:45 UTC. We've identified the likely cause and are implementing a fix.

We're seeing increased function invocation errors beginning at ~13:45 UTC. We've identified the likely cause and are implementing a fix.

The incident is resolved.

We have applied a solution for the function invocation issue in the southeast-2 region and we are monitoring to confirm the resolution.

We have identified an issue starting at 20:38 UTC which is preventing invocations for functions deployed to the ap-southeast-2 region for the High-Performance Edge Network only. We are working on a solution now.

We have identified an issue starting at 20:38 UTC which is preventing invocations for functions deployed to the ap-southeast-2 region for the High-Performance Edge Network only. We are working on a solution now.

Domain purchasing has been restored.

We have identified the issue and are implemented a fix.

We are currently experiencing issues with the purchasing of new domain names. Domain renewals are unaffected.

We are currently experiencing issues with the purchasing of new domain names. Domain renewals are unaffected.

This has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

Starting 11:27 UTC our API started to experience high latency and elevated error rates. We are investigating the issue.

Starting 11:27 UTC our API started to experience high latency and elevated error rates. We are investigating the issue.

This incident has been resolved.

We have identified the cause and implemented a fix. We will continue to actively monitor the results.

We are continuing to investigate these function errors on our Standard Edge and High-Performance Edge network.

We see an increased number of errors when running Functions on the Standard Edge network. High-Performance Edge is not affected. Our team is investigating

We see an increased number of errors when running Functions on the Standard Edge network. High-Performance Edge is not affected. Our team is investigating

We see an increased number of errors when running Functions on the Standard Edge network. High-Performance Edge is not affected. Our team is investigating

This issue has been resolved.

A fix has been implemented and we're currently monitoring the results.

We’re seeing an increase in errors deploying GitHub repos with Deploy with Netlify as well as deploying sites from a template. We're currently investigating this issue.

We’re seeing an increase in errors deploying GitHub repos with Deploy with Netlify as well as deploying sites from a template. We're currently investigating this issue.

The incident has been resolved and no further issues are observed. Thank you for your patience

We've implemented a rollback and are seeing successful recovery of build logs access. We are currently monitoring the situation

We are currently investigating an issue where users may experience errors or lack of access when viewing build logs

We are currently investigating an issue where users may experience errors or lack of access when viewing build logs

From 17:10 UTC to 17:40 UTC, we saw a an increase in error rates for Edge Functions across the Standard Edge Network. The issue is now resolved.

From 17:10 UTC to 17:40 UTC, we saw a an increase in error rates for Edge Functions across the Standard Edge Network. The issue is now resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We've identified the issue and are working on a fix.

We are investigating an issue that is causing SSL/TLS certificates errors for some sites using subdomains of windsurf.build.

We are investigating an issue that is causing SSL/TLS certificates errors for some sites using subdomains of windsurf.build.

Between 8:27 UTC and 8:31 UTC our Build system experienced performance degradation that impacted our customers. Customers may have experienced builds that were in progress or newly started to fail.

Between 8:27 UTC and 8:31 UTC our Build system experienced performance degradation that impacted our customers. Customers may have experienced builds that were in progress or newly started to fail.

This incident has been resolved.

A fix has been implemented and we're monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are experiencing degraded performance across several Netlify services. We are working on identifying and resolving this issue.

This incident has been resolved.

A fix has been implemented and we're monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are experiencing degraded performance across several Netlify services. We are working on identifying and resolving this issue.

This incident has been resolved.

Our team has identified the root cause and deployed a fix.

Starting at approximately 11:18 UTC, we began observing an increase in error rates when serving requests via the Netlify Standard Edge. Our engineering team is actively investigating the issue.

This incident has been resolved.

Our team has identified the root cause and deployed a fix.

Starting at approximately 11:18 UTC, we began observing an increase in error rates when serving requests via the Netlify Standard Edge. Our engineering team is actively investigating the issue.

This incident has been resolved.

The team has restored the service and is monitoring the situation

We're currently looking into elevated error rates, and latency on our standard, and high-performance networks.

We are continuing to investigate this issue.

We're currently looking into elevated error rates, and latency on our standard, and high-performance networks.

This incident has been resolved.

The team has restored the service and is monitoring the situation

We're currently looking into elevated error rates, and latency on our standard, and high-performance networks.

We are continuing to investigate this issue.

We're currently looking into elevated error rates, and latency on our standard, and high-performance networks.

This incident has been resolved.

We have released a fix and are monitoring this issue.

We are continuing to investigate this issue.

We are currently experiencing elevated latency to our API and app

This incident has been resolved.

We've rolled back the change that led to these errors and we're continuing to monitor the results.

We are continuing to investigate this issue.

We are experiencing elevated rates of API errors. We are investigating the cause now.

This issue has been resolved.

A fix has been implemented and we're currently monitoring the results.

We are continuing to investigate this issue.

We are currently investigating increased latency with the Visual Editor and Create API.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Starting at 12:29 UTC, we started seeing an increase in average duration for requests on to the Standard Edge network. Our team is investigating.

This incident has been resolved.

We have rolled out a fix and have observed successful deploys.

The issue has been identified and we are working on a fix

We see an elevated number of builds failing for sites that use Functions configured in regions other than us-east-2. Our team has been alerted and is working on a fix

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Around 08:00am UTC Create started experiencing DNS issues which is impacting origin requests to the API and access to the visual editor in the Netlify app.

A fix has been deployed. We continue to monitor the system for any issues.

We are continuing to monitor for any further issues.

We've deployed improvements to address caching inconsistencies and are rolling out fixes to affected customers. Monitoring continues

We have implemented a more comprehensive fix for the caching issues and are rolling the HP Edge customers into it. We have narrowed down the root cause and are working on addressing it

We are continuing to monitor to ensure this issue is mitigated while we work on identifying and implementing a fix for the root cause.

We are actively monitoring to ensure this issue is mitigated while we work on identifying and implementing a fix for the root cause.

We have implemented a solution to mitigate this issue across our CDN. We are continuing to investigate the root cause.

We've identified caching inconsistencies with several sites across our HP Edge Network. We are implementing a fix to resolve this issue.

This is now resolved.

We're still monitoring, however this should now be resolved.

During testing we noticed that a small percentage of HP edge customers are impacted as well. We've started a rollback, and are monitoring the situation.

We've started a rollback and are monitoring the situation

We are seeing sporadic instances of 502 Bad Gateway responses for requests to the Standard Edge, HP Edge is not affected. Our team is investigating.

This incident has been resolved.

We have deployed a fix to our functions deployment pipeline and are currently monitoring the results.

We're seeing failures to deploy sites due to a failure to upload functions. Our team has identified the issue and is working on a fix.

This incident has been resolved. If you're still seeing issues, please redeploy the site.

A fix has been implemented to address this issue. We're still monitoring the fix.

A fix has been implemented to address this issue. Affected sites need to be redeployed to see those changes take effect.

We've identified the cause of this issue and are currently working on a fix.

Our team is currently investigating the root cause.

Between 15:13 UTC and 16:05 UTC, Connect experienced an issue due to an expired domain certificate. The issue has been fully resolved, and services are operating normally.

The issue has been identified and a fix has been implemented.

Our team is actively working to resolve the issue.

Connect domain certificates have expired, affecting origin requests to the Connect API and accessing the Connect dashboard in the Netlify app.

This incident is now resolved.

We are continuing to monitor for any other issues

create.netlify.com , and create API's temporarily were not loading for customers It has since recovered on its own. It was caused by a large uptick in traffic.

create.netlify.com is back up, we're currently working on identifying the cause of the issue

We are continuing to investigate this issue.

We are currently investigating an issue with Create API's returning 500 errors, and create.netlify.com not loading

On January 12, 2025, from 15:35 UTC to 16:11 UTC, the Netlify High Performance Edge Network suffered increased latencies and errors. This should now be resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The mitigation is currently in the process of rolling out.

We are continuing to roll out a mitigation across the network.

We have identified the issue and are rolling out a mitigation

We are investigating problems with cache purges on the Standard Edge network. High Powered Edge network is unaffected.

This incident has been resolved.

We are continuing to monitor for any further issues.

We have identified the cause and have re-enabled domain purchasing in the UI. We will continue to monitor.

We are currently investigating an issue with domain name purchasing. We have disabled it in the UI for the time being.

We’ve fixed an issue that was affecting some form submissions with CAPTCHA. To apply these updates, please redeploy your site.

We’ve resolved an issue affecting some form submissions with reCAPTCHA. Please redeploy your site to ensure updates take effect.

We are currently investigating an issue impacting the functionality of reCAPTCHA for Netlify Forms.

Our monitors and logging point to our Image CDN no longer responding with 502s.

A fix has been made to address the issue causing the 502 response and are monitoring to make sure the change has resolved the issue completely.

We have identified the cause of the 502s and are working towards a fix.

We are currently investigating reports of issues with our ImageCDN.

All affected customers should no longer have issues creating new deploys or network issues related to this issue.

Increased errors across the network and builds from 15:29 UTC to 15:36 UTC. An issue with pulling latest environment variables for sites in networks and builds was detected

This incident has been resolved.

The fix has been implemented

The issue has been identified and a fix is being implemented.

We are seeing increased latency and errors with edge functiosns in Europe and the US and are currently investigating.

Between 7:55 UTC and 8:55 UTC there was increased latency and there were errors on the Standard Edge Network. The issue is now resolved.

The issue is now solved

We've applied a fix, and the issue appears to be resolved. We're continuing to monitor it.

The team is still investigating the issue,

We believe this is related to our Edge Functions layer alone. We're still investigating.

The team continues to investigate the issue. We started seeing the errors happening around 1AM UTC.

We are seeing increased latency and errors on the High-Performance Edge Network. The team is investigating

This incident has been resolved.

We've applied a fix and the issue appears to be resolved. We're continuing to monitor the issue.

We are continuing to investigate this issue.

We're investigating reports of HTTP 431 on sites using Edge Functions.

This incident has been resolved.

We have mitigated the issue and the team will continue to monitor.

Beginning around 19:20 UTC we saw issues loading source data from Connect. The team has identified the issue are are actively working on a fix.

This incident has been resolved.

Correction on the time span: From 12:20 UTC to 13:20 UTC, there was increased latency and errors on the High-Performance Edge Network in the Frankfurt region. The issue has been mitigated, and our team will continue to monitor the situation.

From 12:20 UTC to 12:50 UTC, there was increased latency and there were errors on the High-Performance Edge Network in the Frankfurt region. We have mitigated the issues, and the team will continue to monitor.

Starting at 12:20 UTC, we are seeing increased latency and errors on the High-Performance Edge Network in the Frankfurt region.

The incident is now resolved.

The issue has been fixed. We're monitoring the traffic.

We are continuing to work on a fix for this issue. This outage impacts no other regions besides Central Canada.

We identified the issue and are working on solving it.

We're investigating increased rates of latencies on the High-Performance Edge Network, in Central Canada, since 4:00 AM UTC

Beginning at 15:25 UTC, we saw some build failures as a result of an active GitHub incident. This affected around 177 sites and around 500 builds. This incident was resolved at 16:03 UTC.

This incident has been resolved.

A fix for this issue has been deployed and we will continue to monitor.

At 8:38am UTC, we observed an outage with our Analytics, RUM, and Billing Overview features. Our engineers have identified the source of this issue and are working to resolve. We have confirmed no data has been lost during this outage.

The network performance should now be back to normal.

We're continuing to ensure the fix is effective.

A fix has been implemented and we are monitoring the results.

We're investigating increased rates of latencies on the High Performance Edge Network in US East region. We're working on this issue.

This incident has been resolved.

From 09:09 UTC to 11:40 UTC, there was increased latency and there were errors on the High-Performance Edge Network. We have mitigated the issues, and the team will continue to monitor.

The team continues to investigate this issue.

Efforts to resolve the issue are ongoing.

The team is still working diligently to resolve the issue.

Our team is actively working to resolve the issue.

We’re seeing a decrease in errors. The team is continuing the investigate this issue.

Starting at 09:09 UTC we are seeing increased latency and errors on the High-Performance Edge Network

The fix has been fully rolled out across the network, and this issue is resolved.

We're actively monitoring this process, and almost all impacted sites have recovered. If you still see issues with your Next.js site, please reach out to our Support team.

We are rolling out a fix across the Standard Edge Network and sites are recovering. This work is still in progress.

We have identified an issue impacting Next.js sites using SSR and the durable cache feature showing a blank page on the Standard Edge Network. The High-Performance Edge Network is not impacted by this issue.

The issue has been resolved. Purging of expired assets has returned to expected levels and is no longer experiencing delays.

Our engineers were able to identify the issue and have remedied the situation. Cache purging is returning to expected levels as we continue to monitor it.

Around 17:00 UTC, we began observing a delay in purging stale cache. As a result, some customers may see stale content unexpectedly. We are working to identify and resolve the issue.

There was an upstream issue at GitHub which prevented builds from runnin between 23:02 UTC and 23:39 UTC on 2024-08-14 for sites with repositories hosted at GitHub.

Network activity has returned to expected levels and the issue is resolved.

A fix for the issue has been deployed. We'll continue to monitor the networks closely.

We've identified the root cause and are working to implement a fix.

At 17:01 UTC we began seeing increased errors and delays across both our High-Performance and Standard Edge Networks. We're working to resolve the issue as quickly as possible.

Increased latencies and errors were observed across the Standard as well as High Performance Edge Network across all regions from 10:26 UTC to 10:31 UTC. This is now resolved and system is back to normal.