Jupyter (Anaconda): Degraded database write performance

MinorStatus: resolvedStarted 2023-08-17 21:05 UTCResolved 2023-08-17 22:03 UTC (58 min)1 updateanaconda.statuspage.io

Timeline of updates

resolved2023-08-17 22:03 UTC
We've identified the source of the database latency, which was hundreds of short duration queries being sent to the database by a specific job, removed it, and prevented it from running in the future.

From Jupyter (Anaconda)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on anaconda.statuspage.io (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Jupyter (Anaconda), started 2023-08-17 21:05 UTC, resolved after 58 min, 1 update(s).

Title: Degraded database write performance
Vendor: Jupyter (Anaconda)
Date: 2023-08-17 21:05 UTC
URL: https://rewindex.com/company/jupyter-anaconda/incidents/7qg49cqqg5ww

Jupyter (Anaconda) profile Recent Jupyter (Anaconda) incidents All outages on August 17, 2023 Jupyter (Anaconda) in August 2023 Markdown JSON