Loading status…
RubyGems status · Developer Tools · checked (1m ago)
Also searched as RubyGems.org.
No — RubyGems is not down. All RubyGems systems are reported operational.
According to RubyGems's official status page, RubyGems was reporting “Service Under Maintenance” when isuptime last checked at . Over the last 30 days, RubyGems's feed reported no outage in 100.00% of our checks.
Everything above is read from RubyGems's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported RubyGems in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
RubyGems.org is the package registry for Ruby: the host that `gem install` and `bundle install` fetch from, and where gem authors publish. Every Ruby build in the world depends on it unless it has been pointed at a mirror.
The status page separates the website from the gem-serving CDN and the API. That split is the useful one, because gem downloads are served through a CDN and usually survive problems with the site itself — the API and the search page can be down while `bundle install` keeps working. Planned maintenance is posted here and does register as a non-operational state.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where RubyGems's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days RubyGems was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of RubyGems's status endpoint.
RubyGems has published 7 incidents in the last 12 months, newest first. Only what RubyGems posted itself — not every problem users hit.
resolved · Aug 19, 04:30 AM (32d ago)
resolved · Jul 24, 11:29 AM (57d ago)
resolved · May 12, 08:54 AM (130d ago)
resolved · Apr 6, 08:33 PM (166d ago)
resolved · Mar 31, 09:58 AM (172d ago)
resolved · Feb 12, 08:21 PM (219d ago)
resolved · Oct 15, 06:56 AM (339d ago)
A failing `bundle install` is more often a version conflict, a yanked gem or a private source needing credentials than a registry outage. Bundler falls back and retries, so intermittent timeouts frequently resolve on a rerun. If a gem was recently published, index propagation through the CDN takes a few minutes and the gem genuinely does not exist yet from your location.
