RubyGems

Affected: Application, Dependency API, Gem Index API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-19 04:30 UTC

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

2. identified 2026-08-19 05:06 UTC

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

3. monitoring 2026-08-19 05:59 UTC

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

4. resolved 2026-08-19 06:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-24 11:29 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 2026-07-24 11:57 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 2026-07-24 12:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: Security incident or emergency response to a vulnerability. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-12 08:54 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 2026-05-13 03:17 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...

3. resolved 2026-05-16 05:12 UTC

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

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-06 20:33 UTC

   We are currently investigating this issue.

2. identified 2026-04-06 20:51 UTC

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

3. monitoring 2026-04-06 20:58 UTC

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

4. resolved 2026-04-06 21:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application, Dependency API, Gem Index API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-31 09:58 UTC

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

2. monitoring 2026-03-31 10:18 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 2026-03-31 10:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-12 20:21 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 2026-02-12 21:21 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 2026-02-12 22:15 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 2026-02-12 22:36 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2025-10-15 06:56 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 2025-10-15 23:04 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...

3. identified 2025-10-17 02:15 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 2025-10-27 20:15 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 2025-10-27 21:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2023-05-11 21:45 UTC

   Google Safe Browsing has flagged the entire rubygems.org domain as malware, impacting all users of the Chrome, Safari, and Firefox browser. The underlying issue appears to be an incorrect malware flag applied to all versions of a gem from the metasploit family. In our...

2. identified 2023-05-11 22:01 UTC

   We have heard that our appeal has successfully been escalated within the Google Safe Browsing team, and they are working to resolve things.

3. resolved 2023-05-12 01:01 UTC

   Success! Google Safe Browsing has removed the malware flag from rubygems.org. Special thanks are owed to everyone who connected us to the Chrome and Safe Browsing teams, and the team members who assisted in clearing this up.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Gem Downloads, Application, Dependency API, Gem Index API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-06-08 10:00 UTC

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

2. investigating 2021-06-08 10:12 UTC

   The elevated 503 and 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/vpk0ssybt3bj.

3. identified 2021-06-08 10:46 UTC

   Our CDN partner has identified the issue and a fix is being implemented.

4. monitoring 2021-06-08 11:03 UTC

   Our CDN provider has applied a fix and over the last few minutes we saw traffic levels and errors return to normal.

5. resolved 2021-06-08 11:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Gem Downloads, Fastly Frankfurt (FRA), Application, Dependency API, Fastly Sydney (SYD), Fastly Amsterdam (AMS), Gem Index API, Fastly Ashburn (IAD), Fastly Singapore (SIN), Fastly London (LCY), Fastly Denver (DEN), Fastly London (LHR), Fastly New Zealand (AKL), Fastly Chicago (ORD), Fastly New Zealand (WLG), Fastly Stockholm (BMA), Fastly Hong Kong (HKG), Fastly Miami (MIA), Fastly Dallas (DFW), Fastly Melbourne (MEL), Fastly Osaka (ITM), Fastly San Jose (SJC), Fastly Brisbane (BNE), Fastly Seattle (SEA), Fastly Dubai (FJR), Fastly Perth (PER), Fastly Frankfurt (HHN), Fastly Paris (CDG), Fastly Madrid (MAD), Fastly Boston (BOS), Fastly Minneapolis (MSP), Fastly Johannesburg (JNB), Fastly Montreal (YUL), Fastly Toronto (YYZ), Fastly Sāo Paulo (GRU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-01-12 16:02 UTC

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

2. identified 2021-01-12 16:14 UTC

   The elevated 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/1rbr326kjsmt.

3. monitoring 2021-01-12 16:28 UTC

   Fastly has implemented a fix and we are monitoring the results.

4. resolved 2021-01-12 16:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Gem Downloads, Application, Dependency API, Gem Index API, Upstream Provider: DNSimple Name Servers

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2020-07-17 21:20 UTC

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

2. monitoring 2020-07-17 21:42 UTC

   DNS seems to be resolving again. We continue to monitor the situation.

3. monitoring 2020-07-17 21:53 UTC

   We are continuing to monitor for any further issues.

4. resolved 2020-07-17 22:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-04-25 10:03 UTC

   We're currently investigating users being unable to access rubygems.org

2. investigating 2020-04-25 10:03 UTC

   We are continuing to investigate this issue.

3. resolved 2020-04-25 10:16 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Gem Downloads, Application, Dependency API, Gem Index API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2020-04-02 16:15 UTC

   We are currently investigating DNS resolution errors for some users.

2. resolved 2020-04-03 21:33 UTC

   DNS resolution should be working for all users now.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application, Dependency API, Gem Index API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-02-24 10:38 UTC

   We are currently investigating this issue.

2. monitoring 2020-02-24 10:53 UTC

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

3. resolved 2020-02-24 11:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application, Dependency API, Gem Index API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2019-01-31 10:42 UTC

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

2. monitoring 2019-01-31 10:55 UTC

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

3. resolved 2019-01-31 11:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application, Dependency API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2019-01-13 16:53 UTC

   Over the last 20 minutes we experienced an elevated level of errors. We are currently monitoring the issue.

2. resolved 2019-01-13 23:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Application, Dependency API, Gem Index API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2019-01-13 09:05 UTC

   We're experiencing an unexpected problem and are currently looking into the issue.

2. monitoring 2019-01-13 09:33 UTC

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

3. resolved 2019-01-13 09:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Affected: Gem Index API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2019-01-01 14:02 UTC

   We have received reports of some gems not being able to be installed. We have identified the issue and we are working on resolving it. Gems published before 2015-08-23 may be unlisted on the versions API.

2. monitoring 2019-01-01 14:19 UTC

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

3. resolved 2019-01-01 14:26 UTC

   This incident has been resolved. All gems should be included in the versions API again.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2017-12-25 20:08 UTC

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

2. monitoring 2017-12-25 20:21 UTC

   All services should be working now. We will continue to monitor.

3. investigating 2017-12-25 22:25 UTC

   We are currently investigating this issue.

4. resolved 2017-12-26 09:56 UTC

   The site has been stable since 19:15 UTC.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2017-05-02 14:58 UTC

   We are aware of reports that services are unavailable in some regions. We're looking into it now!

2. monitoring 2017-05-02 15:14 UTC

   Our upstream provider has implemented a fix and we are monitoring the results. We are also seeing reports of general internet issues in Europe. We will post more information as we get it.

3. monitoring 2017-05-02 16:05 UTC

   We receive reports that a major ISP had a complete outage between the United States and Europe for about 20 minutes at 14:45 UTC.

4. resolved 2017-05-02 16:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2017-05-02 12:00 UTC

   We received reports of legacy software being unable to access RubyGems.org. Specifically anyone using TLS 1.1. This is common on older operating systems like Ubuntu Precise 12.04. We quickly realized that our CDN provider had disabled TLS 1.1 today due to a previously announced...

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2016-10-03 19:23 UTC

   We're aware that new gems published may not be added to the new gem index in a timely manor. Our team is investigating. Running 'bundle install --full-index', as well as 'gem install' are unaffected by this delay.

2. identified 2016-10-03 19:34 UTC

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

3. monitoring 2016-10-03 19:42 UTC

   All gems should be indexed now. We are monitoring to make sure new gems are added in a timely manor.

4. resolved 2016-10-03 22:22 UTC

   All gems appear to be installing successfully.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2016-09-12 03:17 UTC

   We are receiving reports of DNS problems. We are investigating.

2. identified 2016-09-12 03:29 UTC

   We have identified and fixed the problem. Service will be restored as soon as DNS propagates.

3. monitoring 2016-09-12 03:36 UTC

   We are continuing to monitor the DNS propagation.

4. resolved 2016-09-12 13:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2016-09-06 20:36 UTC

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

2. resolved 2016-09-07 01:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2016-06-27 18:47 UTC

   We're experiencing elevated response times and are currently looking into the issue.

2. monitoring 2016-06-27 19:44 UTC

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

3. resolved 2016-06-27 22:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2016-06-10 04:16 UTC

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

2. monitoring 2016-06-10 04:21 UTC

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

3. resolved 2016-06-10 04:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2016-06-06 10:46 UTC

   We are aware that some gem downloads are not working and the Dependency API is not working for some versions of bundler. Our team is looking into it. Sorry for the inconvenience – we’ll have a solution for this soon!

2. investigating 2016-06-06 10:53 UTC

   All gem downloads are working again.

3. monitoring 2016-06-06 11:09 UTC

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

4. resolved 2016-06-06 13:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2016-05-24 12:41 UTC

   We’re investigating some issues with our dependencies API not updating - sorry folks!

2. identified 2016-05-24 13:26 UTC

   Heads up: we're running on the legacy dependency API for now. bundle installs might be slow!

3. monitoring 2016-05-24 14:29 UTC

   We've resolved the issue and the Dependency API should be working normally again.

4. resolved 2016-05-24 15:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2016-04-30 15:05 UTC

   We are aware that some newly pushed gems are not able to be installed when the dependency API is used. This is used by most versions of bundler and RubyGems. Our team is looking into it. Sorry for the inconvenience – we’ll have a solution for this soon!

2. monitoring 2016-04-30 15:31 UTC

   We have identified the problem and deployed a fix.

3. resolved 2016-04-30 16:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2016-03-22 15:58 UTC

   We're aware of intermittent errors on the dependency api. We saw an increase in traffic yesterday and the API was having trouble responding in a timely manner. We've made several changes to the service in the last 24 hours to reduce the error rates. Our failures are down but we...

2. monitoring 2016-03-22 20:12 UTC

   Service has been restored. After many infrastructure, configuration, and code changes today we have found the problem. The dependency API should be returning results in a reasonable time with no errors now. We're continuing to monitor things.

3. resolved 2016-03-22 22:03 UTC

   The dependency API has been stable, answering all requests, for about two hours. We'll keep an eye on it, but everything seems resolved for now.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2015-12-31 22:16 UTC

   Our CDN provider is experiencing an outage right now. Gem installs might not be working in some regions. We'll update when we know more.

2. monitoring 2015-12-31 22:36 UTC

   Our provider is reporting that service is returning to normal. We're still seeing higher than normal error rates so we are continuing to monitor closely.

3. resolved 2015-12-31 23:42 UTC

   Error rates have returned to normal. Everything should be working now.

Excerpts are shortened. Read the full incident on RubyGems's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2015-11-30 12:00 UTC

   High load on our database is causing errors right now.

Excerpts are shortened. Read the full incident on RubyGems's status page.