Changes / Jupyter (Anaconda) / Dot-org network interruption
Jupyter (Anaconda): Critical incident: Dot-org network interruption
Summary
Anaconda reported a critical network interruption affecting the anaconda.org front-end and conda.anaconda.org repository services, with elevated 503 errors on anaconda.org. It started at 2026-09-01 17:46 UTC and was resolved at 2026-09-01 19:05 UTC, lasting 1 h 18 min. A fix was rolled out at 18:53 UTC; no cause was stated.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Dot-org network interruption
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-09-01 17:46 UTC
Before: not present
After: 2026-09-01 19:05 UTC
Before: not present
After: Anaconda.org - Front End Web Service - anaconda.org, Anaconda.org - Repository Service - conda.anaconda.org, Front End Web Service - anaconda.org, Repository Service - conda.anaconda.org
Before: not present
After: We have noticed an elevated number of 503 status codes to anaconda.org and are investigating.
Before: not present
After: We are continuing to investigate this issue.
Before: not present
After: We have identified the issue and rolled out a fix. We will continue to monitor the system.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Dot-org network interruption (this change) Anaconda reported a critical network interruption affecting the anaconda.org front-end and conda.anaconda.org repository services, with elevated 503 errors on anaconda.org. It started at 2026-09-01 17:46 UTC and was resolved at 2026-09-01 19:05 UTC, lasting 1 h 18 min. A fix was rolled out at 18:53 UTC; no cause was stated. | Major incident |
All Jupyter (Anaconda) changes → · Jupyter (Anaconda) profile · Markdown · JSON