Rubygems 장애 기록

1. 2026년 8월 19일 오전 4:30 UTCinvestigating

   우리는 높은 수준의 오류를 경험하고 현재 문제가 있습니다.

2. 2026년 8월 19일 오전 5:06 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 8월 19일 오전 5:59 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 8월 19일 오전 6:59 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 오전 11:29 UTCidentified

   RubyGems.org의 부품 전반에 걸쳐 문제가 있습니다. Gem installs and pushes may be slow or failureing, 사이트 자체는 믿을 수 없습니다.

2. 2026년 7월 24일 오전 11:57 UTCmonitoring

   우리는 우리의 상류 공급자의 하나에 문제를 추적하고 서비스 회복으로 밀접하게 지켜집니다. 설치 및 푸시는 다시 작동해야하지만, 여전히 상황이 정착하는 동안 가끔 오류를 볼 수 있습니다.

3. 2026년 7월 24일 오후 12:06 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 12일 오전 8: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. 2026년 5월 13일 오전 3: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. 2026년 5월 16일 오전 5:12 UTCresolved

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

1. 2026년 4월 6일 오후 8:33 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 6일 오후 8:51 UTCidentified

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

3. 2026년 4월 6일 오후 8:58 UTCmonitoring

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

4. 2026년 4월 6일 오후 9:04 UTCresolved

   This incident has been resolved.

1. 2026년 3월 31일 오전 9:58 UTCinvestigating

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

2. 2026년 3월 31일 오전 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. 2026년 3월 31일 오전 10:59 UTCresolved

   This incident has been resolved.

1. 2026년 2월 12일 오후 8: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. 2026년 2월 12일 오후 9: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. 2026년 2월 12일 오후 10: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. 2026년 2월 12일 오후 10:36 UTCresolved

   This incident has been resolved

1. 2025년 10월 15일 오전 6: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. 2025년 10월 15일 오후 11: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. 2025년 10월 17일 오전 2: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. 2025년 10월 27일 오후 8: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. 2025년 10월 27일 오후 9:05 UTCresolved

   This incident has been resolved.

1. 2023년 5월 11일 오후 9: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. 2023년 5월 11일 오후 10: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. 2023년 5월 12일 오전 1: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. 2021년 6월 8일 오전 10:04 UTCinvestigating

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

2. 2021년 6월 8일 오전 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. 2021년 6월 8일 오전 10:46 UTCidentified

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

4. 2021년 6월 8일 오전 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. 2021년 6월 8일 오전 11:29 UTCresolved

   This incident has been resolved.

1. 2021년 1월 12일 오후 4:13 UTCinvestigating

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

2. 2021년 1월 12일 오후 4: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. 2021년 1월 12일 오후 4:28 UTCmonitoring

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

4. 2021년 1월 12일 오후 4:55 UTCresolved

   This incident has been resolved.

1. 2020년 7월 17일 오후 9:30 UTCinvestigating

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

2. 2020년 7월 17일 오후 9:42 UTCmonitoring

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

3. 2020년 7월 17일 오후 9:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2020년 7월 17일 오후 10:01 UTCresolved

   This incident has been resolved.

1. 2020년 4월 25일 오전 10:03 UTCinvestigating

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

2. 2020년 4월 25일 오전 10:03 UTCinvestigating

   We are continuing to investigate this issue.

3. 2020년 4월 25일 오전 10:16 UTCresolved

   This incident has been resolved

1. 2020년 4월 2일 오후 4:15 UTCidentified

   We are currently investigating DNS resolution errors for some users.

2. 2020년 4월 3일 오후 9:33 UTCresolved

   DNS resolution should be working for all users now.

1. 2020년 2월 24일 오후 1:28 UTCinvestigating

   We are currently investigating this issue.

2. 2020년 2월 24일 오후 1:29 UTCmonitoring

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

3. 2020년 2월 24일 오후 1:30 UTCresolved

   This incident has been resolved.

1. 2019년 1월 31일 오전 10:42 UTCinvestigating

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

2. 2019년 1월 31일 오전 10:55 UTCmonitoring

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

3. 2019년 1월 31일 오후 1:21 UTCresolved

   This incident has been resolved.

1. 2019년 1월 13일 오후 4:53 UTCmonitoring

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

2. 2019년 1월 13일 오후 11:44 UTCresolved

   This incident has been resolved.

1. 2019년 1월 13일 오전 9:23 UTCinvestigating

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

2. 2019년 1월 13일 오전 9:33 UTCmonitoring

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

3. 2019년 1월 13일 오전 9:36 UTCresolved

   This incident has been resolved.

1. 2019년 1월 1일 오후 2: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. 2019년 1월 1일 오후 2:19 UTCmonitoring

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

3. 2019년 1월 1일 오후 2:26 UTCresolved

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

1. 2017년 12월 25일 오후 8:08 UTCinvestigating

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

2. 2017년 12월 25일 오후 8:21 UTCmonitoring

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

3. 2017년 12월 25일 오후 10:25 UTCinvestigating

   We are currently investigating this issue.

4. 2017년 12월 26일 오전 9:56 UTCresolved

   The site has been stable since 19:15 UTC.

1. 2017년 5월 2일 오후 2:58 UTCinvestigating

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

2. 2017년 5월 2일 오후 3: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. 2017년 5월 2일 오후 4: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. 2017년 5월 2일 오후 4:07 UTCresolved

   This incident has been resolved.