Jupyter (Anaconda) change history

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.

Anaconda reported a major backend outage affecting APIs, authentication, repositories, EduBlocks and Pyscript, involving an inability to spawn new compute nodes. The recorded start was 2026-08-25 17:10 UTC, though reported impacts began at 15:45 UTC. A fix was implemented; resolution was recorded at 2026-08-25 18:52 UTC, with a computed duration of 1 h 41 min.

Anaconda.org’s front-end web service experienced increased errors with major impact, starting 2026-03-02 15:46 UTC and lasting 41 min. A fix was implemented by 2026-03-02 16:18 UTC, and the incident was resolved at 2026-03-02 16:28 UTC.

Anaconda.org experienced a major performance degradation affecting its database, front-end web service and conda.anaconda.org repository service, from 2026-02-03 13:45 UTC to 2026-02-03 15:05 UTC, lasting 1 h 19 min. A fix was implemented by 14:40 UTC; the incident was resolved, with no cause stated.

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.

Major conda-forge CDN cloning delays affected conda.anaconda.org; the incident ran from 2025-10-29 16:37 UTC to 2025-10-29 18:03 UTC (1 h 25 min), with delays reported since 09:34 UTC. Longer channel cloning jobs were terminated prematurely; increasing the time limit resolved the issue.

Anaconda reported a major AWS-related outage causing degraded performance or unavailability across services, including authentication, repositories, notebooks and AI Platform. The incident ran from 2025-10-20 10:05 UTC to 2025-10-21 07:24 UTC (21 h 18 min); Anaconda reported services operational at 10-20 14:16 UTC before marking it resolved.

The community channels page showed a "no items found" error in an incident rated major, with the AI Platform Application and Premium Package Repository listed as affected components. It started at 2025-09-15 17:21 UTC and lasted 3 h 4 min, resolving at 2025-09-15 20:25 UTC after a fix was implemented.

A major networking performance issue affecting data centers in Ashburn, Virginia caused slowness or timeouts for Anaconda services starting 2025-08-21 18:00 UTC. The CDN provider rerouted traffic at 19:07 UTC; Anaconda marked the incident resolved at 2025-08-21 20:22 UTC, after 2 h 22 min.

A critical outage at repo.anaconda.com/pkgs prevented package installations from 2025-07-23 10:30 UTC to 2025-07-23 15:00 UTC, lasting 4 h 30 min. Anaconda restored access by reverting a configuration change it said occurred at 10:36 UTC.

A major Cloudflare outage caused increased error rates, affecting SSO authentication to all Anaconda services and repo.anaconda.cloud. The incident started at 2025-06-12 18:40 UTC and was resolved at 2025-06-12 20:57 UTC, lasting 2 h 16 min; services were reported as beginning to recover at 06-12 20:22 UTC.