- Level
- confirmed
- Worst impact
- Degraded
- Components
- Gem Index API
- Down Index
- 15of 100
What to do
Check whether you use RubyGems.org Gem Index API. 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 24m it lasted.
Anything that failed between 2019-01-01 14:02 UTC and 2019-01-01 14:26 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
- identified
We have received reports of some gems not being able to be installed. We have identified the issue and we are working on resolving it. Gems published before 2015-08-23 may be unlisted on the versions API.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved. All gems should be included in the versions API again.
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-84d896499a
Is RubyGems.org still down?
No, this incident was resolved 2019-01-01 14:26 UTC. For RubyGems.org's live state, see https://down.guide/rubygems.
How long did it last?
24m, from 2019-01-01 14:02 UTC to 2019-01-01 14:26 UTC, by the times RubyGems.org posted.
What was affected?
RubyGems.org named Gem Index API.
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.