- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Application
- Down Index
- 26of 100
What to do
Check whether you use RubyGems.org Application. 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 37m it lasted.
Anything that failed between 2026-07-24 11:29 UTC and 2026-07-24 12:06 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're currently investigating problems across parts of RubyGems.org. Gem installs and pushes may be slow or failing, and the site itself may not load reliably.
provider
- monitoring
We've traced the problem to one of our upstream providers and are watching closely as service recovers. Installs and pushes should be working again, though you may still see the occasional error while things settle.
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-e6e5753665
Is RubyGems.org still down?
No, this incident was resolved 2026-07-24 12:06 UTC. For RubyGems.org's live state, see https://down.guide/rubygems.
How long did it last?
37m, from 2026-07-24 11:29 UTC to 2026-07-24 12:06 UTC, by the times RubyGems.org posted.
What was affected?
RubyGems.org named Application.
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.