RubyGems Outage History

RubyGems is up right now

Pingoru has recorded 35 incidents for RubyGems: 6 in the last 12 months and 1 in the last 90 days.

Source: status.rubygems.org

35incidents recorded
6last 12 months
1last 90 days
17 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking RubyGems in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 2026192 of 744 (12%)
June 202600 of 720 (0%)
July 202611 of 744 (0%)
August 202613 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 526 (0%)

Incidents, newest first

Major August 19, 2026 Elevated Errors 2h 28m Application, Dependency API, Gem Index API

Started Aug 19, 2026, 04:30 AM UTC· resolved Aug 19, 2026, 06:59 AM UTC

  1. investigating Aug 19, 2026, 04:30 AM UTC

    We're experiencing an elevated level of errors and are currently looking into the issue.

  2. identified Aug 19, 2026, 05:06 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 19, 2026, 05:59 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 19, 2026, 06:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 24, 2026 Degraded service on RubyGems.org 36m Application

Started Jul 24, 2026, 11:29 AM UTC· resolved Jul 24, 2026, 12:06 PM UTC

  1. identified Jul 24, 2026, 11:29 AM UTC

    We're currently investigating problems across parts of RubyGems.org. Gem installs and pushes may be slow or failing, and the site itself may not load reliably.

  2. monitoring Jul 24, 2026, 11:57 AM UTC

    We've traced the problem to one of our upstream providers and are watching closely as service recovers. Installs and pushes should be working again, though you may still see the occasional error while things settle.

  3. resolved Jul 24, 2026, 12:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 12, 2026 Temporarily disabling new user registrations 3d 20h

Started May 12, 2026, 08:54 AM UTC· resolved May 16, 2026, 05:12 AM UTC

  1. identified May 12, 2026, 08:54 AM UTC

    Due to an ongoing DDoS attack against rubygems.org, we have temporarily disabled registrations. We'll share an update once we've made changes to protect legitimate users and prevent further abuse.

  2. identified May 13, 2026, 03:17 AM UTC

    The malicious spam activity against rubygems.org has stopped. The bot accounts responsible have been blocked and removed, and the 500+ malicious packages pushed during the attack have been yanked from the registry. Registrations will remain closed while we coordinate with Fastly to enable WAF protection and tighten rate limiting on account creation. We expect this to take two to three days. We'll post another update when we're closer being ready to re-enable user registrations. Gem installs and pushes for existing users are unaffected.

  3. resolved May 16, 2026, 05:12 AM UTC

    This incident has been resolved and we've re-enabled account registrations

Read the full incident report →

Major April 6, 2026 Rubygems.org is experiencing a partial outage 30m Application

Started Apr 06, 2026, 08:33 PM UTC· resolved Apr 06, 2026, 09:04 PM UTC

  1. investigating Apr 06, 2026, 08:33 PM UTC

    We are currently investigating this issue.

  2. identified Apr 06, 2026, 08:51 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 06, 2026, 08:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 06, 2026, 09:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2026 Degraded performance 1h Application, Dependency API, Gem Index API

Started Mar 31, 2026, 09:58 AM UTC· resolved Mar 31, 2026, 10:59 AM UTC

  1. investigating Mar 31, 2026, 09:58 AM UTC

    We're currently investigating response time degradation on rubygems.org and index.rubygems.org

  2. monitoring Mar 31, 2026, 10:18 AM UTC

    We have identified the cause of the performance degradation and have begun restoring normal service. We're continuing to monitor the situation.

  3. resolved Mar 31, 2026, 10:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 12, 2026 Search degredation 2h 14m Application

Started Feb 12, 2026, 08:21 PM UTC· resolved Feb 12, 2026, 10:36 PM UTC

  1. investigating Feb 12, 2026, 08:21 PM UTC

    We are currently experiencing a partial outage affecting RubyGems.org search functionality. Our team is investigating the issue and working towards a resolution.

  2. identified Feb 12, 2026, 09:21 PM UTC

    We've identified and are addressing the underlying issue affecting RubyGems.org search. Service restoration is underway, and we anticipate normal operations to resume within the next hour.

  3. monitoring Feb 12, 2026, 10:15 PM UTC

    The issue affecting RubyGems.org search has been resolved. We are monitoring the service to ensure stability and will provide an update if any further issues arise.

  4. resolved Feb 12, 2026, 10:36 PM UTC

    This incident has been resolved

Read the full incident report →

Minor October 15, 2025 Gem pushes with attestation failing 12d 14h Application

Started Oct 15, 2025, 06:56 AM UTC· resolved Oct 27, 2025, 09:05 PM UTC

  1. identified Oct 15, 2025, 06:56 AM UTC

    Gem pushes utilising the attestation feature are failing and will respond with an application error. We've identified the issue and are currently working to push a fix.

  2. identified Oct 15, 2025, 11:04 PM UTC

    We have implemented a fix for gem pushes that use attestations on rubygems.org. However, gems that rely on the release-gem GitHub Action (https://github.com/rubygems/release-gem) to deploy to rubygems.org will still experience errors. The release-gem action will automatically retry pushing to rubygems.org without attestations, which continue to function as expected. We are closely monitoring the situation and collaborating with the Sigstore team to resolve this issue.

  3. identified Oct 17, 2025, 02:15 AM UTC

    We're continuing to work with the sigstore team to help resolve users being unable to gem pushes with attestations. For the time being, we recommend users update their workflows to retry gem pushes without attestations.

  4. identified Oct 27, 2025, 08:15 PM UTC

    This issue has been resolved. Please ensure that you're using the latest version of the https://github.com/rubygems/release-gem in your Github Actions tasks.

  5. resolved Oct 27, 2025, 09:05 PM UTC

    This incident has been resolved.

Read the full incident report →