Netlify UI unavailable in FRA
Timeline · 1 update
- resolved Jan 19, 2026, 12:24 PM UTC
From 08:54 UTC to 09:12 UTC, app.netlify.com was unavailable to users in FRA.
Netlify had 72 outages in the last 2 years totaling 388h 7m of downtime — averaging 3 incidents per month.
There were 72 Netlify outages since October 8, 2025 totaling 388h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
From 08:54 UTC to 09:12 UTC, app.netlify.com was unavailable to users in FRA.
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.
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're observing Ai gateway errors due to issues with an upstream provider.
This incident has been resolved.
Starting around 17:00 UTC we're seeing an increase in errors on Netlify Image CDN. We're investing the issue.
We've identified the cause of the elevated error rates affecting our image CDN. Mitigation efforts are underway, and we're monitoring for improvements. We’ll continue to provide updates as we make progress.
A fix has been implemented, and we are seeing signs of recovery, performance is improving. We are continuing to monitor closely and will provide further updates as needed
Image delivery performance has stabilized, and performance has returned to normal levels. We are no longer observing elevated error rates.
Log Drains is experiencing issues when exporting to New Relic. The team is currently investigating.
The issue was caused by errors when pushing logs to an upstream provider. Those errors have cleared, and log delivery is resuming. We’re continuing to monitor our systems to ensure full recovery.
This incident has been resolved.
We're seeing an increase in errors and latencies on the Standard Edge Network.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Since 10:27am UTC we are seeing ingesting issues with observability data.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Starting 06:28 UTC, we're investigating increased errors with Netlify Image CDN. We're currently investigating the issue.
We're experiencing issues with the entire Netlify CDN and are investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We see an increased latency and errors invoking in Edge Functions on HP Edge starting at 12:38 UTC. This has recovered by 12:44 UTC. Our team is monitoring.
This incident has been resolved.
We experience delays in delivering Function logs through Log Drains, starting at 13:53 UTC. Our team is investigating.
The issue has been identified and a fix is being implemented.
We are no longer experiencing delays, we are continuing to monitor.
This incident has been resolved.
We're seeing failures to deploy sites (sites what have functions) due to a failure to upload functions. Our team has identified the issue and is working on a fix.
The issue has been identified and a fix is being implemented.
We have deployed a fix to our functions deployment pipeline and are currently monitoring the results.
Between 15:20 UTC and 16:30 UTC we saw build failures for builds with functions. The incident has been resolved, and we are no longer observing any issues. Thank you for your patience.
From 08:48 UTC to 09:11 UTC today, we experienced an increased error rate invoking edge functions.
Starting 17:54 UTC we see increased latency for traffic on the High Performance Edge in the São Paulo region. We're currently investigating this issue.
The latencies should be back to normal as of 18:10 UTC.
As of 12:04 UTC, we are experiencing issues and latency serving traffic from the High Powered Edge Network.
We are continuing to investigate this issue
We have applied a mitigation and are seeing recovery.
We are continuing to see recovery across the network
We are continuing to monitor the recovery results across the network.
We are continuing to monitor our mitigations and for any further issues.
This incident has been resolved.
Purchasing of extra credits is currently unavailable. Auto-recharge is still available at this time.
The purchasing of extra credits for credit-based plans is available again. The incident is resolved.
Since 11:30pm UTC on 11/13, domains have been experiencing issues in completing registration. As of 7:15am UTC, domain purchasing is unavailable while a solution is put in place.
We have identified the issue, and are working on putting a fix in place. Domain purchasing is still disabled while we resolve.
We are continuing to work on a fix for this issue.
A fix has been implemented and domain purchasing is available again. We will actively monitor.
This incident has been resolved, and domain purchasing is fully restored.
Between 10:27 UTC and 10:31 UTC our Origin and API experienced increased latencies and elevated error rates. Our Build system experienced build failures. Content may have failed to load from different edge CDN locations and TLS connection establishments may have suffer failures.
Since 13:00 UTC, agent runners have been unavailable. Users trying to use it could see a stuck message saying "configuring environment" in the UI. We are working on a fix right now.
A fix has been rolled out at 17:15 UTC and the issue appears to be resolved.
From 10:06 to 10:25 am UTC, builds experienced a high rate of errors. We have mitigated the issue and put a fix in place, and will continue to monitor the result.
The build issues have been resolved.
Between 17:09 UTC and 17:38 UTC, logs for Netlify Edge Functions and Netlify Functions were not recorded. Logging is now fully restored.
We’re investigating an issue causing errors or missing data when accessing deploy, function, and Edge function logs.
We’ve implemented a fix and are observing recovery in log access. Our team is continuing to monitor the situation to ensure stability.
The incident has been resolved, and we are no longer observing any issues. Thank you for your patience.