- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 9h 47m it lasted.
Anything that failed between 2016-09-12 03:17 UTC and 2016-09-12 13:05 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 are receiving reports of DNS problems. We are investigating.
provider
- identified
We have identified and fixed the problem. Service will be restored as soon as DNS propagates.
provider
- monitoring
We are continuing to monitor the DNS propagation.
provider
- resolved
This incident has been resolved.
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-34ebacdace
Is RubyGems.org still down?
No, this incident was resolved 2016-09-12 13:05 UTC. For RubyGems.org's live state, see https://down.guide/rubygems.
How long did it last?
9h 47m, from 2016-09-12 03:17 UTC to 2016-09-12 13:05 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.