Anaconda incident

Errors downloading repodata.json on conda.anaconda.org

Resolved after 5 hours 37 minutes, on December 1, 2025.

resolved Dec 02, 2025, 09:10 PM 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 " 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.

Started
Dec 01, 2025, 09:58 PM UTC
Resolved
Dec 02, 2025, 03:35 AM UTC
Duration
5h 37m
Detected by Pingoru
Dec 01, 2025, 09:58 PM UTC

Update timeline

  1. resolved Dec 02, 2025, 09:10 PM 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 " 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.

Your product runs on more than Anaconda

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →