- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on RubyGems.org. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 59m it lasted.
Anything that failed between 2016-10-03 19:23 UTC and 2016-10-03 22:22 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 4
- investigating
We're aware that new gems published may not be added to the new gem index in a timely manor. Our team is investigating. Running 'bundle install --full-index', as well as 'gem install' are unaffected by this delay.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
All gems should be indexed now. We are monitoring to make sure new gems are added in a timely manor.
provider
- resolved
All gems appear to be installing successfully.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ad0efbf5f6
Is RubyGems.org still down?
No, this incident was resolved 2016-10-03 22:22 UTC. For RubyGems.org's live state, see https://down.guide/providers/rubygems.
How long did it last?
2h 59m, from 2016-10-03 19:23 UTC to 2016-10-03 22:22 UTC, by the times RubyGems.org posted.
What caused it?
RubyGems.org hasn't published a root cause. If it does, it shows here.
Where does this come from?
RubyGems.org's official status page, https://status.rubygems.org, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.