История сбоев Rubygems

1. 19 августа 2026 г. в 04:30 UTCinvestigating

   Мы испытываем повышенный уровень ошибок и в настоящее время изучаем проблему.

2. 19 августа 2026 г. в 05:06 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

3. 19 августа 2026 г. в 05:59 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

4. 19 августа 2026 г. в 06:59 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 24 июля 2026 г. в 11:29 UTCidentified

   В настоящее время мы изучаем проблемы в разных частях RubyGems.org. Установки и толчки Gem могут быть медленными или неэффективными, а сам сайт может не загружаться надежно.

2. 24 июля 2026 г. в 11:57 UTCmonitoring

   Мы отследили проблему до одного из наших провайдеров и внимательно следим за восстановлением сервиса. Установки и толчки должны работать снова, хотя вы все еще можете видеть случайную ошибку, пока все улаживается.

3. 24 июля 2026 г. в 12:06 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 12 мая 2026 г. в 08:54 UTCidentified

   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. 13 мая 2026 г. в 03:17 UTCidentified

   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. 16 мая 2026 г. в 05:12 UTCresolved

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

1. 6 апреля 2026 г. в 20:33 UTCinvestigating

   We are currently investigating this issue.

2. 6 апреля 2026 г. в 20:51 UTCidentified

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

3. 6 апреля 2026 г. в 20:58 UTCmonitoring

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

4. 6 апреля 2026 г. в 21:04 UTCresolved

   This incident has been resolved.

1. 31 марта 2026 г. в 09:58 UTCinvestigating

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

2. 31 марта 2026 г. в 10:18 UTCmonitoring

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

3. 31 марта 2026 г. в 10:59 UTCresolved

   This incident has been resolved.

1. 12 февраля 2026 г. в 20:21 UTCinvestigating

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

2. 12 февраля 2026 г. в 21:21 UTCidentified

   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. 12 февраля 2026 г. в 22:15 UTCmonitoring

   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. 12 февраля 2026 г. в 22:36 UTCresolved

   This incident has been resolved

1. 15 октября 2025 г. в 06:56 UTCidentified

   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. 15 октября 2025 г. в 23:04 UTCidentified

   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. 17 октября 2025 г. в 02:15 UTCidentified

   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. 27 октября 2025 г. в 20:15 UTCidentified

   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. 27 октября 2025 г. в 21:05 UTCresolved

   This incident has been resolved.

1. 11 мая 2023 г. в 21:45 UTCidentified

   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 investigation we’ve identified that the same library is also available from GitHub and many Linux and BSD distro packages. We continue investigating, sharing information and working with Google to resolve this as soon as possible. For the time being, there are no other issues: the website can be accessed as normal if you bypass the warning. Gem downloads and pushes continue working as normal.

2. 11 мая 2023 г. в 22:01 UTCidentified

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

3. 12 мая 2023 г. в 01:01 UTCresolved

   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.

1. 8 июня 2021 г. в 10:04 UTCinvestigating

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

2. 8 июня 2021 г. в 10:12 UTCinvestigating

   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. 8 июня 2021 г. в 10:46 UTCidentified

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

4. 8 июня 2021 г. в 11:03 UTCmonitoring

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

5. 8 июня 2021 г. в 11:29 UTCresolved

   This incident has been resolved.

1. 12 января 2021 г. в 16:13 UTCinvestigating

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

2. 12 января 2021 г. в 16:14 UTCidentified

   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. 12 января 2021 г. в 16:28 UTCmonitoring

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

4. 12 января 2021 г. в 16:55 UTCresolved

   This incident has been resolved.

1. 17 июля 2020 г. в 21:30 UTCinvestigating

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

2. 17 июля 2020 г. в 21:42 UTCmonitoring

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

3. 17 июля 2020 г. в 21:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 17 июля 2020 г. в 22:01 UTCresolved

   This incident has been resolved.

1. 25 апреля 2020 г. в 10:03 UTCinvestigating

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

2. 25 апреля 2020 г. в 10:03 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 апреля 2020 г. в 10:16 UTCresolved

   This incident has been resolved

1. 2 апреля 2020 г. в 16:15 UTCidentified

   We are currently investigating DNS resolution errors for some users.

2. 3 апреля 2020 г. в 21:33 UTCresolved

   DNS resolution should be working for all users now.

1. 24 февраля 2020 г. в 13:28 UTCinvestigating

   We are currently investigating this issue.

2. 24 февраля 2020 г. в 13:29 UTCmonitoring

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

3. 24 февраля 2020 г. в 13:30 UTCresolved

   This incident has been resolved.

1. 31 января 2019 г. в 10:42 UTCinvestigating

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

2. 31 января 2019 г. в 10:55 UTCmonitoring

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

3. 31 января 2019 г. в 13:21 UTCresolved

   This incident has been resolved.

1. 13 января 2019 г. в 16:53 UTCmonitoring

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

2. 13 января 2019 г. в 23:44 UTCresolved

   This incident has been resolved.

1. 13 января 2019 г. в 09:23 UTCinvestigating

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

2. 13 января 2019 г. в 09:33 UTCmonitoring

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

3. 13 января 2019 г. в 09:36 UTCresolved

   This incident has been resolved.

1. 1 января 2019 г. в 14:02 UTCidentified

   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. 1 января 2019 г. в 14:19 UTCmonitoring

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

3. 1 января 2019 г. в 14:26 UTCresolved

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

1. 25 декабря 2017 г. в 20:08 UTCinvestigating

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

2. 25 декабря 2017 г. в 20:21 UTCmonitoring

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

3. 25 декабря 2017 г. в 22:25 UTCinvestigating

   We are currently investigating this issue.

4. 26 декабря 2017 г. в 09:56 UTCresolved

   The site has been stable since 19:15 UTC.

1. 2 мая 2017 г. в 14:58 UTCinvestigating

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

2. 2 мая 2017 г. в 15:14 UTCmonitoring

   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. 2 мая 2017 г. в 16:05 UTCmonitoring

   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. 2 мая 2017 г. в 16:07 UTCresolved

   This incident has been resolved.