# Jupyter (Anaconda): Errors downloading repodata.json on conda.anaconda.org

- Impact (vendor’s label): major
- Status: resolved
- Started: 2025-12-01 21:58 UTC · Resolved: 2025-12-01 21:58 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://stspg.io/dp4shkvg887b](https://stspg.io/dp4shkvg887b)
- [Company: Jupyter (Anaconda)](https://rewindex.com/company/jupyter-anaconda.md)

## Summary

A major incident affected conda commands near San Jose, California, including Github Actions runners, with repodata.json connection failures or 503 errors. It started 2025-12-01 21:58 UTC and was marked resolved (computed duration: 0 min), although the update reports impact through 2025-12-02 03:35 UTC. The vendor cited a connection spike at a single regional data center. _(machine-written, sol)_
## Timeline of updates

- **resolved** 2025-12-01 21:58 UTC: 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 \<https://conda.anaconda.org/conda-forge/noarch/repodata.json\>" 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.

## Rewindex changes for this incident

- 2025-12-01 21:58 UTC: [Major incident: Errors downloading repodata.json on conda.anaconda.org](https://rewindex.com/change/ic9b6ce2e7dc07d.md)


---
Canonical: https://rewindex.com/company/jupyter-anaconda/incidents/8ntln142ckd8 · Markdown: https://rewindex.com/company/jupyter-anaconda/incidents/8ntln142ckd8.md · JSON: https://rewindex.com/api/v1/companies/jupyter-anaconda/incidents/8ntln142ckd8 · Generated 2026-10-18T12:43:45.927Z