Is RubyGems down?
RubyGems status · Developer Tools · checked (0s 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.
Is RubyGems down for you right now?
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.
What RubyGems is
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.
What RubyGems's status feed covers
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.
RubyGems uptime, last 30 days
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.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 0s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
RubyGems response time trend
Each point is one check of RubyGems's status endpoint.
Which RubyGems features are affected?
- Fastly London (LCY) — under_maintenance
- Upstream Provider: Fastly — under_maintenance
RubyGems outage history
RubyGems has published 6 incidents in the last 12 months, newest first. Only what RubyGems posted itself — not every problem users hit.
- Elevated Errors
resolved · Aug 19, 04:30 AM (77d ago)
- Degraded service on RubyGems.org
resolved · Jul 24, 11:29 AM (102d ago)
- Temporarily disabling new user registrations
resolved · May 12, 08:54 AM (176d ago)
- Rubygems.org is experiencing a partial outage
resolved · Apr 6, 08:33 PM (211d ago)
- Degraded performance
resolved · Mar 31, 09:58 AM (217d ago)
- Search degredation
resolved · Feb 12, 08:21 PM (264d ago)
RubyGems status — frequently asked
- Is RubyGems down right now?
- No — RubyGems is not down. All RubyGems systems are reported operational. Checked (0s ago).
- What is RubyGems's status right now?
- RubyGems is reporting “Service Under Maintenance” on its official status page — Operational — as of . That status feed answered our last check in 326 ms. isuptime reads this from RubyGems's own published feed and does not test RubyGems independently.
- When did RubyGems last go down?
- The most recent incident RubyGems published was “Elevated Errors”, opened Aug 19, 04:30 AM UTC (77d ago) and marked resolved Aug 19, 06:59 AM UTC. That is the latest entry in RubyGems's own incident feed, not every problem users experienced.
- What is RubyGems's uptime?
- isuptime does not measure RubyGems's uptime directly — it reads RubyGems's own published status feed. Over the last 30 days, RubyGems's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is RubyGems down for everyone?
- RubyGems reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
RubyGems says operational but it is not working for me
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.
