CompaniesJupyter (Anaconda)Incidents
Jupyter (Anaconda): Incorrect Rate Limits Applied
Affected components: anaconda.com - Repository Service - repo.anaconda.comPublic Repository Service - repo.anaconda.com/pkgs
Timeline of updates
- monitoring
We use a web application firewall to apply rate limits to requests to our software repository service hosted at repo.anaconda.com. Due to a misconfiguration, these rate limits were being applied at too low of a level, which interrupted access to the software repository incorrectly, for some of our users. This condition existed for about 13 hours, from 11pm UTC June 27 to 12pm UTC June 28. We deployed a fix and are monitoring closely.
- resolved
This incident has been resolved.
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
0a2ac5086f9fb740…
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 2024-06-28 12:59 UTC, resolved after 8.2 h, 2 update(s).
- Title
- Incorrect Rate Limits Applied
- Vendor
- Jupyter (Anaconda)
- Date
- URL
- https://rewindex.com/company/jupyter-anaconda/incidents/dd7q4ksyy55n
Jupyter (Anaconda) profileRecent Jupyter (Anaconda) incidentsAll outages on June 28, 2024Jupyter (Anaconda) in June 2024MarkdownJSON