CheckUpstream does not yet run an independent probe against RubyGems.org, so no availability figure is published for it — only RubyGems.org's own disclosure record below. 5 incidents were recorded in the past 12 months; the most recent resolved 38 days ago after 26 days. Status signals are polled from RubyGems.org's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against RubyGems.org yet, so we publish no availability figure for it. What follows is RubyGems.org's own disclosure record, which is a different thing.
Vendor disclosed: 1 incident · 16 of 30 days with none posted · 9d 4h of declared impact
Fewer incidents in the last 30 days than 44% of 232 tracked services.
Share of each window with no impact declared by RubyGems.org
7d
100.000%
30d
69.442%
90d
89.814%
180d
92.049%
1y
96.079%
Downtime like this can be refundable
If you're a paying RubyGems.org customer, outages in these windows may count against RubyGems.org's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your RubyGems.org entitlement →Does RubyGems.org actually matter to you?
A RubyGems.org outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
low data · n=4~23149m (p25 8609m – p75 54085m)
Based on 4 historical Major incidents · currently 18859m elapsed.
Live RubyGems.org status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/rubygems-org)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
RubyGems.org is currently Degraded. CheckUpstream tracks RubyGems.org in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is RubyGems.org down" view? See the RubyGems.org Live status page.
Mar 31, 09:58 UTC · resolved in 6d 10h · Resolved
RubyGems.org's last resolved incident started 38 days ago and lasted 25d 17h (a partial outage).
We don't publish one. CheckUpstream runs no independent probe against RubyGems.org yet, and the only other figure available would be derived from RubyGems.org's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add RubyGems.org to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll RubyGems.org's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.