- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
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 1h 26m it lasted.
Anything that failed between 2015-12-31 22:16 UTC and 2015-12-31 23:42 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
Our CDN provider is experiencing an outage right now. Gem installs might not be working in some regions. We'll update when we know more.
provider
- monitoring
Our provider is reporting that service is returning to normal. We're still seeing higher than normal error rates so we are continuing to monitor closely.
provider
- resolved
Error rates have returned to normal. Everything should be working now.
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-8928304dd6
Is RubyGems.org still down?
No, this incident was resolved 2015-12-31 23:42 UTC. For RubyGems.org's live state, see https://down.guide/rubygems.
How long did it last?
1h 26m, from 2015-12-31 22:16 UTC to 2015-12-31 23:42 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.