pingoru pingoru Anaconda had 30 outages in the last 2 years totaling 196h 49m of downtime, averaging 1.2 incidents per month.
There were 30 Anaconda outages since November 1, 2024 totaling 196h 49m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Anaconda.com/app it's down. We are investigating the issue; we're working on the fix
A fix has been implemented and we're monitoring the results.
This incident has been resolved. !
We have noticed an elevated number of 503 status codes to anaconda.org and are investigating.
We are continuing to investigate this issue.
We have identified the issue and rolled out a fix. We will continue to monitor the system.
This incident has been resolved.
An issue involving an inability to spawn new compute nodes is impacting many of Anaconda's backend services starting at 15:45 UTC. The root cause has been identified and we are working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There is an active incident with the authentication platform used for anaconda.com/app and anaconda.org, which is already being worked on. Login, signup, and password resets might fail. We will update you once we have new information.
We are continuing to monitor this incident.
The incident with the authentication platform has been resolved.
We are observing an increased error rate for anaconda.org. We are investigating the issue and will update the incident status as soon as we have additional information. We apologize for the disruption.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing impacted performance for anaconda.org. We are investigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We see an elevated high error rate for multiple regions. Our CDN provider has issued an incident, see https://www.cloudflarestatus.com/
The CDN provider implemented a fix and we are seeing better connectivity again.
This incident has been resolved.
Between 2025-12-01 21:58 UTC and 2025-12-02 03:35 UTC, users running conda commands from servers located near San Jose, California (such as Github Actions runners) would see the message "CondaHTTPError: HTTP 000 CONNECTION FAILED for url " or 503 errors. The issue was caused by a spike of connections to a single data center in that region, which overloaded its capacity. We are working with our networking vendor to implement a more permanent solution. We apologize for the disruption.
We are currently investigating this issue.
We have performed a temporary mitigation that has reduced the rate of errors and timeouts. We are continuing to work on more permanent fixes as we continue to work with our cloud provider contacts.
The issue has been identified and a fix is being implemented.
The issue has been traced to errors and network timeouts from a vendor. We are engaging our contacts with that vendor to resolve the issue.
This incident has been resolved.
We are investigating an outage affecting our services due to an ongoing issue with AWS. Users may experience degraded performance or unavailability. See https://health.aws.amazon.com/health/status for more details.
We are continuing to monitor for any further issues.
Anaconda's services are now operational. We are continuing to monitor the situation.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A spike in usage overloaded the web server that handles auth and user creation for the notebooks service. We've increased those resources and are continuing to monitor.
This incident has been resolved.
Due to a networking performance issue affecting data centers in Ashburn, Virginia, users accessing Anaconda services may experience slowness or timeouts. We're working with our support contacts and will provide updates as we receive them.
A fix has been implemented and we are monitoring the results.
Our CDN provider has rerouted traffic at 19:07 UTC and marked the incident as resolved. We are continuing to monitor to ensure full resolution.
This incident has been resolved.
The public repository at repo.anaconda.com/pkgs is returning errors, preventing installing packages. We have identified the issue and are working on resolution. We apologize for the disruption.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
Access to repo.anaconda.com/pkgs has now been restored. The incident was caused by a recent configuration change at 10:36 UTC which we reverted. We will continue to monitor and perform an analysis of this incident. We apologize for the disruption.
We are aware of an issue with the Anaconda Terms of Service acceptance being prompted for in some continuous integration (CI) environments. This behavior is not intended. We are sorry for the issues this is causing in the affected environments, and are actively working on a resolution. You can alternatively set the CONDA_PLUGINS_AUTO_ACCEPT_TOS environment variable to "yes" to accept the Terms of Service automatically. You can find the full Terms of Service at https://www.anaconda.com/legal and the conda-anaconda-tos plugin documentation at https://github.com/anaconda/conda-anaconda-tos. If you want to contact us directly about this, please write an email to [email protected].
We are continuing to work on a fix for this issue.
We are implementing a fix to expand the types of CI environments detected. We will update the status when the fix is available. For Docker or OCI containers in CI/CD environments, please refer to the documentation in https://github.com/anaconda/conda-anaconda-tos#docker-in-cicd-environments for how to accept the terms of service in a container. As previously mentioned, the CONDA_PLUGINS_AUTO_ACCEPT_TOS environment variable can be set to "yes" in any environment to accept the Terms of Service, which are available at https://www.anaconda.com/legal.
We have implemented a fix to expand the types of CI environments detected by the plugin. This fix is included in conda-anaconda-tos 0.2.1 which has been included in Anaconda Distribution 2025.06-1 and Miniconda 25.5.1-1 For Docker or OCI containers in CI/CD environments, please refer to the documentation in https://github.com/anaconda/conda-anaconda-tos#docker-in-cicd-environments for how to accept the terms of service in a container. To automatically accept the Terms of Service (https://www.anaconda.com/legal) in any environment, set the environment variable CONDA_PLUGINS_AUTO_ACCEPT_TOS=yes.
This incident has been resolved.
We are seeing an elevated error rate for anaconda.com.
We are continuing to investigate this issue.
We've rolled out a fix for the errors on nb.anaconda.com and are monitoring the rollout.
The error rates on nb.anaconda.com are still elevated. We are continuing to investigate.
The error rates on nb.anaconda.com appear to be caused by people with inactive browser tabs, due to a recent update to the Notebooks service. Reloading the tab or clicking on the "Restart server" button should fix any remaining errors.
A Cloudflare outage is causing increased error rates for some Anaconda services. We're monitoring for updates. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp
We are continuing to investigate this issue.
We have identified that the outage affected SSO authentication to all services, as well as repo.anaconda.cloud. The services are beginning to recover now. We will continue to monitor.
We are continuing to monitor for any further issues.
This incident has been resolved. We apologize to all who are affected by the disruption.
After the migration of nb.anaconda.cloud to nb.anaconda.com at 7AM UTC, users may have seen 403 errors when saving files in their jupyter notebooks. This was due to a misconfiguration of our web application firewall on the new domain. This issue has now been resolved. If you continue to see errors, please contact support.
Since 7AM UTC, users attempting to publish panel apps from the Notebooks service would have seen 526 errors when trying to access the panel app. This was due to a certificate misconfiguration that has now been fixed as of 1:46PM UTC.
We have noticed that downloads from conda-forge are experiencing a major disruption and are investigating the issue.
A subset of conda-forge packages built within the last few days are not being copied to the CDN. Anaconda is still working on fixing that but rest assured the packages do exist in our backend. In the meantime, please bump build numbers and/or versions for any packages you absolutely need to get published.
This incident has been resolved.
Updates to subscriptions on anaconda.cloud are currently processed with a delay. If you have updated your subscription and this is not reflected yet, please follow this status entry. We will keep you up to date with our investigation and resolution of the issue here.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A breaking change was introduced and subsequently deployed to production. Shortly after deployment, it was reported that users were experiencing a blank page when accessing anaconda.cloud. This issue was identified as a critical UI failure impacting production. Immediate investigation was initiated to determine the root cause and mitigate the impact on users.
Maintenance on our load balancers resulted in an increase of "403 Forbidden" errors on repo.anaconda.cloud from 16:04-16:24 UTC. The change has been reverted and the site is operating normally now.
We are aware of elevated error rates for anaconda.org and are investigating the issue.
We have identified the issue and implemented a fix for it.
Monitoring anaconda.org shows that the issue has been fixed successfully.