UptimeProject

RubyGems.org

Operational
Official site Provider status

Ruby Central · Dev Infrastructure

Updated

24h availability

100.00%

0 min down

7d availability

100.00%

0 min down

30d availability

100.00%

0 min down

90d availability

100.00%

0 min down

Period:
Avg response time 299ms
0% 50% 100% 2026-10-23 00:00 UTC Status: up Availability: 100.00% p50 latency: 334ms 2026-10-24 00:00 UTC Status: up Availability: 100.00% p50 latency: 254ms 2026-10-25 00:00 UTC Status: up Availability: 100.00% p50 latency: 256ms 2026-10-26 00:00 UTC Status: up Availability: 100.00% p50 latency: 251ms 2026-10-27 00:00 UTC Status: up Availability: 100.00% p50 latency: 242ms 2026-10-28 00:00 UTC Status: up Availability: 100.00% p50 latency: 236ms 2026-10-29 00:00 UTC Status: up Availability: 100.00% p50 latency: 328ms 2026-10-30 00:00 UTC Status: up Availability: 100.00% p50 latency: 337ms 2026-10-31 00:00 UTC Status: up Availability: 100.00% p50 latency: 350ms 2026-11-01 00:00 UTC Status: up Availability: 100.00% p50 latency: 353ms 2026-11-02 00:00 UTC Status: up Availability: 100.00% p50 latency: 341ms 2026-11-03 00:00 UTC Status: up Availability: 100.00% p50 latency: 350ms 2026-11-04 00:00 UTC Status: up Availability: 100.00% p50 latency: 353ms 2026-11-05 00:00 UTC Status: up Availability: 100.00% p50 latency: 254ms 2026-11-06 00:00 UTC Status: up Availability: 100.00% p50 latency: 250ms 371ms 218ms 23 Oct 06 Nov 90d availability · latency (p50)

90d: 0 min down, 0 min degraded, 2 min unmeasured

Recent incidents

All incidents Atom feed

No incidents recorded in the lookback window.

Vantage points

Falkenstein, DE Hetzner
731ms Operational
Roubaix, FR OVH
198ms Operational
New York, US DigitalOcean
258ms Operational
Seattle, US Vultr
126ms Operational
Singapore Vultr
213ms Operational

What we monitor

2 active checks

Each row below is one probe-side measurement we run from every vantage point. The availability number on this page is the consensus across these checks, not a single endpoint hit.

  • HTTP https://rubygems.org/api/v1/gems every minute
  • TLS rubygems.org:443 every hour

About this data

Availability is measured independently by probes in five locations. Each probe runs the appropriate mix of HTTP, DNS, TLS, and storage checks at per-check cadences and records timing, status code, and any error. A probe votes "up" for a given minute if any of its checks for this service succeeded; the minute is then counted as "up" on the leaderboard only when a strict majority of reporting probes voted up. Minutes where fewer than three probes reported are excluded from the denominator. Full methodology

Embed a badge

Markdown for a README. The image is served by the public API and links back to this page. 

          [![RubyGems.org uptime](https://api.uptimeproject.org/v1/services/rubygems/badge.svg)](https://uptimeproject.org/service/rubygems/)
Back to Dev Infrastructure leaderboard