Companies / Jupyter (Anaconda) / incidents

Jupyter (Anaconda): anaconda.cloud - Some channels degraded

Impact: majorStatus: resolvedStarted 2023-09-20 20:41 UTCResolved 2023-09-21 02:11 UTC (5.5 h)5 updatesSource: stspg.io

Summary

Several anaconda.cloud channels returned 500 errors in a major-impact incident starting 2023-09-20 20:41 UTC and lasting 5 h 30 min, resolved at 2023-09-21 02:11 UTC. CLI calls were working while UI issues remained under investigation; Anaconda rolled out a fix and reported the platform fully operational after mitigation.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Anaconda.cloud - Commercial Package Repository Service - repo.anaconda.cloud

Timeline of updates

investigating2023-09-20 20:41 UTC
We are currently investigating an issue involving several channels in anaconda.cloud returning 500 errors
investigating2023-09-20 21:14 UTC
We are triaging the issue and have isolated one of the possible components that are causing the issue. We will provide another update in 30 minutes.
investigating2023-09-20 22:22 UTC
Calls from the CLI are working, we are still investigating an issue on the UI of anaconda.cloud. We will provide another update shortly or once we have identified the root cause, whatever comes next.
identified2023-09-21 00:22 UTC
We have identified the issue and we are rolling out a fix. All systems should be back to normal operation within a few minutes.
resolved2023-09-21 02:11 UTC
We have implemented mitigation measurements and the platform is fully operational again. Sorry for any inconvenience.

Rewindex changes for this incident

Major incident: anaconda.cloud - Some channels degraded 2023-09-20 20:41 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Jupyter (Anaconda) profile · Recent Jupyter (Anaconda) incidents · Markdown · JSON