RubyGems status history
Current state: maintenance — “Service Under Maintenance” per https://status.rubygems.org (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do RubyGems incidents last?
From 7 incidents with a vendor-posted start and resolve time. Longest on record: Gem pushes with attestation failing — 12.6 days (2025-10-15 06:56 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (7)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-19 04:30 UTC | Elevated Errors | resolved | major | 2 h 28 min |
| 2026-07-24 11:29 UTC | Degraded service on RubyGems.org | resolved | major | 36 min |
| 2026-05-12 08:54 UTC | Temporarily disabling new user registrations | resolved | none | 3 d 20 h |
| 2026-04-06 20:33 UTC | Rubygems.org is experiencing a partial outage | resolved | major | 30 min |
| 2026-03-31 09:58 UTC | Degraded performance | resolved | minor | 1 h 00 min |
| 2026-02-12 20:21 UTC | Search degredation | resolved | major | 2 h 14 min |
| 2025-10-15 06:56 UTC | Gem pushes with attestation failing | resolved | minor | 12 d 14 h |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch RubyGems with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"rubygems"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}