Skip to main content

Is RubyGems Down?

No — RubyGems is up

Reachable from all 8 checked regions

Average response time: 578ms

Last checked · checks run every 6 hours

Official status page: https://status.rubygems.org

Components the vendor reports as affected: Fastly London (LCY) Under Maintenance

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

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
498ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 46 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

46-day clean streak
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 36 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability 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.

fra
51ms
DNS 43ms TCP 1ms TLS 3ms TTFB 49ms
gru
1027ms
DNS 134ms TCP 1ms TLS 4ms TTFB 1025ms
iad
504ms
DNS 299ms TCP 7ms TLS 14ms TTFB 496ms
jnb
1821ms
DNS 263ms TCP 0ms TLS 3ms TTFB 1821ms
lax
267ms
DNS 63ms TCP 2ms TLS 5ms TTFB 265ms
lhr
294ms
DNS 283ms TCP 1ms TLS 4ms TTFB 292ms
nrt
414ms
DNS 404ms TCP 1ms TLS 4ms TTFB 413ms
ord
246ms
DNS 234ms TCP 1ms TLS 6ms TTFB 245ms

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

RubyGems outage FAQ

Why did my build fail if my application is fine?
Because they need different things. A running Ruby application already has its gems on disk and never contacts RubyGems.org again. A build resolves and downloads dependencies fresh, so it depends on the registry answering at that moment. This is why a RubyGems incident shows up as a wall of red CI with no user-visible impact at all.
Is RubyGems down for everyone?
Not always. RubyGems serves gems through Fastly and reports roughly two dozen Fastly points of presence as individual components, from Ashburn and Frankfurt to Sydney and Osaka. A problem at one of them affects developers routed through that location while everyone else builds normally, which is exactly the case a single-location check cannot see.
Can I keep deploying during an outage?
Only if you prepared for it. Vendoring gems into the repository, caching the bundle in CI, or running an internal gem mirror all take RubyGems.org out of the deploy path. Without one of those a clean build has no fallback. Retrying in a tight loop makes things worse for everyone and is rarely faster than waiting for the status page to clear.
Why does RubyGems track AWS and DNSimple on its status page?
Because it depends on them and says so publicly. The status page lists Upstream Provider: AWS, Upstream Provider: Fastly and Upstream Provider: DNSimple Name Servers as components alongside its own services. A DNS or CDN failure at one of those breaks gem downloads without anything being wrong inside RubyGems itself.

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 403 or 429 means 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 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required