CompaniesRubyGems.orgIncidents
RubyGems.org: Degraded Performance on Dependency API
Timeline of updates
- investigating
We're aware of intermittent errors on the dependency api. We saw an increase in traffic yesterday and the API was having trouble responding in a timely manner. We've made several changes to the service in the last 24 hours to reduce the error rates. Our failures are down but we are still seeing some requests fail with HTTP 500 errors. We're working to fix the remaining errors, but in the meantime you can work around this by running: `bundle install --full-index`.
- monitoring
Service has been restored. After many infrastructure, configuration, and code changes today we have found the problem. The dependency API should be returning results in a reasonable time with no errors now. We're continuing to monitor things.
- resolved
The dependency API has been stable, answering all requests, for about two hours. We'll keep an eye on it, but everything seems resolved for now.
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 stspg.io (opens in new tab).
RubyGems.org profileRecent RubyGems.org incidentsMarkdownJSON