CompaniesJupyter (Anaconda)Incidents
Jupyter (Anaconda): 403 errors when accessing Anaconda services
Timeline of updates
- resolved
A bad configuration change caused users accessing sites on anaconda.cloud, anaconda.org, and anaconda.com between 15:50 and 15:55 UTC to receive 403 errors. The configuration change has been reverted.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f41d45582c5b3a43…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Jupyter (Anaconda), started 2025-01-03 16:00 UTC, resolved after 0 min, 1 update(s).
- Title
- 403 errors when accessing Anaconda services
- Vendor
- Jupyter (Anaconda)
- Date
- URL
- https://rewindex.com/company/jupyter-anaconda/incidents/vvdf7mk3njrv
Jupyter (Anaconda) profileRecent Jupyter (Anaconda) incidentsAll outages on January 3, 2025Jupyter (Anaconda) in January 2025MarkdownJSON