Degraded Performance on Dependency API

What to do

• Check whether your product depends on RubyGems.org. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 6h 4m it lasted.

  Anything that failed between 2016-03-22 15:58 UTC and 2016-03-22 22:03 UTC may need a replay.

• Subscribe to RubyGems.org's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=rubygems works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RubyGems.org 3

1. investigatingMar 22, 2016, 3:58 PM UTC

   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`.

   provider

2. monitoringMar 22, 2016, 8:12 PM UTC

   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.

   provider

3. resolvedMar 22, 2016, 10:03 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.