- Service Status
- /
- RubyGems
Is RubyGems Down?
Reachable from all 8 checked regions
Average response time: 517ms
Last checked · checks run every 6 hours
Official status page: https://status.rubygems.org
A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw RubyGems fail from enough regions to rule out probe noise.
RubyGems uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 27 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
27-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What RubyGems does
RubyGems.org is the public package registry for Ruby. Nearly every Ruby application resolves and downloads its dependencies from it through Bundler, and a Rails application pulls dozens of gems on a clean install. It is infrastructure rather than a product: almost nobody visits the website, and almost every Ruby build depends on it answering.
What an outage looks like
Builds fail rather than websites. Running bundle install hangs or errors while fetching the gem index, Docker builds fail at the dependency step, and CI pipelines go red across every Ruby project at once. Deploys that need a clean bundle stop working while already-running applications carry on untouched, because they resolved their dependencies long ago.
What to do about it
Check status.rubygems.org, which reports Gem Downloads, Application, Dependency API and Gem Index API separately and also tracks its upstream providers: Fastly, AWS and DNSimple name servers. Fastly is broken out by individual point of presence, so a failure in one city affects some developers and not others. If a build has to ship, a vendored bundle or an internal gem mirror gets you through.
Is it down for everyone, or just you?
If this page says RubyGems is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
RubyGems outage FAQ
Why did my build fail if my application is fine?
Is RubyGems down for everyone?
Can I keep deploying during an outage?
Why does RubyGems track AWS and DNSimple on its status page?
How we measure this
- We request RubyGems's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where RubyGems publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when RubyGems goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring
