Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Störungsverlauf von Rubygems

    32 Rubygems incidents · November 2015 — official updates, affected components, duration and resolution details.

    Zurück zum aktuellen Status

    Erhöhte Fehler

    Beginn 19. August 2026 um 04:30 UTC · 2h 29m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    ApplicationDependency APIGem Index API
    1. 19. August 2026 um 04:30 UTCinvestigating

      Wir haben ein erhöhtes Maß an Fehlern und untersuchen derzeit das Problem.

    2. 19. August 2026 um 05:06 UTCidentified

      Das Problem wurde identifiziert und ein Fix wird implementiert.

    3. 19. August 2026 um 05:59 UTCmonitoring

      Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

    4. 19. August 2026 um 06:59 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    Degradierter Service auf RubyGems.org

    Beginn 24. Juli 2026 um 11:29 UTC · 37m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    Application
    1. 24. Juli 2026 um 11:29 UTCidentified

      Wir untersuchen derzeit Probleme in Teilen von RubyGems.org. Gem-Installationen und -Pushes können langsam sein oder fehlschlagen, und die Website selbst kann möglicherweise nicht zuverlässig geladen werden.

    2. 24. Juli 2026 um 11:57 UTCmonitoring

      Wir haben das Problem auf einen unserer Upstream-Anbieter zurückgeführt und beobachten genau, wie sich der Service erholt. Installationen und Pushes sollten wieder funktionieren, obwohl Sie möglicherweise immer noch den gelegentlichen Fehler sehen, während sich die Dinge beruhigen.

    3. 24. Juli 2026 um 12:06 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    Temporarily disabling new user registrations

    Beginn 12. Mai 2026 um 08:54 UTC · 3d 20h

    Pending
    1. 12. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 05:12 UTCresolved

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

    Rubygems.org is experiencing a partial outage

    Beginn 6. April 2026 um 20:33 UTC · 30m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    Application
    1. 6. April 2026 um 20:33 UTCinvestigating

      We are currently investigating this issue.

    2. 6. April 2026 um 20:51 UTCidentified

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

    3. 6. April 2026 um 20:58 UTCmonitoring

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

    4. 6. April 2026 um 21:04 UTCresolved

      This incident has been resolved.

    Degraded performance

    Beginn 31. März 2026 um 09:58 UTC · 1h 1m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    ApplicationDependency APIGem Index API
    1. 31. März 2026 um 09:58 UTCinvestigating

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

    2. 31. März 2026 um 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. März 2026 um 10:59 UTCresolved

      This incident has been resolved.

    Search degredation

    Beginn 12. Februar 2026 um 20:21 UTC · 2h 14m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    Application
    1. 12. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 22:36 UTCresolved

      This incident has been resolved

    Gem pushes with attestation failing

    Beginn 15. Oktober 2025 um 06:56 UTC · 12d 14h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Application
    1. 15. Oktober 2025 um 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. Oktober 2025 um 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. Oktober 2025 um 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. Oktober 2025 um 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. Oktober 2025 um 21:05 UTCresolved

      This incident has been resolved.

    Google Safe Browsing flag as malware

    Beginn 11. Mai 2023 um 21:45 UTC · 3h 16m

    Pending
    Betroffene Komponenten
    Application
    1. 11. Mai 2023 um 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. Mai 2023 um 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. Mai 2023 um 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.

    Elevated Errors

    Beginn 8. Juni 2021 um 10:00 UTC · 1h 29m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    ApplicationDependency APIGem Index APIGem Downloads
    1. 8. Juni 2021 um 10:04 UTCinvestigating

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

    2. 8. Juni 2021 um 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. Juni 2021 um 10:46 UTCidentified

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

    4. 8. Juni 2021 um 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. Juni 2021 um 11:29 UTCresolved

      This incident has been resolved.

    Unexpected Errors

    Beginn 12. Januar 2021 um 16:02 UTC · 53m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    ApplicationFastly Stockholm (BMA)Fastly Frankfurt (FRA)Fastly Denver (DEN)Fastly Dubai (FJR)Fastly Ashburn (IAD)Fastly Dallas (DFW)Fastly Osaka (ITM)Fastly New Zealand (AKL)Fastly Paris (CDG)Fastly Johannesburg (JNB)Fastly Miami (MIA)Fastly Madrid (MAD)Fastly Boston (BOS)Fastly Melbourne (MEL)Fastly Brisbane (BNE)Fastly Montreal (YUL)Fastly Sydney (SYD)Fastly London (LCY)Fastly Toronto (YYZ)Fastly Hong Kong (HKG)Fastly Minneapolis (MSP)Fastly Sāo Paulo (GRU)Fastly San Jose (SJC)Fastly Singapore (SIN)Fastly New Zealand (WLG)Fastly Perth (PER)Dependency APIFastly London (LHR)Fastly Frankfurt (HHN)Gem Index APIFastly Chicago (ORD)Fastly Amsterdam (AMS)Gem DownloadsFastly Seattle (SEA)
    1. 12. Januar 2021 um 16:13 UTCinvestigating

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

    2. 12. Januar 2021 um 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. Januar 2021 um 16:28 UTCmonitoring

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

    4. 12. Januar 2021 um 16:55 UTCresolved

      This incident has been resolved.

    Elevated DNS Errors

    Beginn 17. Juli 2020 um 21:20 UTC · 40m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    ApplicationDependency APIUpstream Provider: DNSimple Name ServersGem Index APIGem Downloads
    1. 17. Juli 2020 um 21:30 UTCinvestigating

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

    2. 17. Juli 2020 um 21:42 UTCmonitoring

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

    3. 17. Juli 2020 um 21:53 UTCmonitoring

      We are continuing to monitor for any further issues.

    4. 17. Juli 2020 um 22:01 UTCresolved

      This incident has been resolved.

    Users unable to access RubyGems.org

    Beginn 25. April 2020 um 10:03 UTC · 14m

    OutageKritischer Vorfall
    Betroffene Komponenten
    Application
    1. 25. April 2020 um 10:03 UTCinvestigating

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

    2. 25. April 2020 um 10:03 UTCinvestigating

      We are continuing to investigate this issue.

    3. 25. April 2020 um 10:16 UTCresolved

      This incident has been resolved

    DNS resolution errors for some users

    Beginn 2. April 2020 um 16:15 UTC · 1d 5h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    ApplicationDependency APIGem Index APIGem Downloads
    1. 2. April 2020 um 16:15 UTCidentified

      We are currently investigating DNS resolution errors for some users.

    2. 3. April 2020 um 21:33 UTCresolved

      DNS resolution should be working for all users now.

    Unexpected Problem

    Beginn 24. Februar 2020 um 10:38 UTC · 25m

    OutageKritischer Vorfall
    Betroffene Komponenten
    ApplicationDependency APIGem Index API
    1. 24. Februar 2020 um 13:28 UTCinvestigating

      We are currently investigating this issue.

    2. 24. Februar 2020 um 13:29 UTCmonitoring

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

    3. 24. Februar 2020 um 13:30 UTCresolved

      This incident has been resolved.

    Unexpected Problem

    Beginn 31. Januar 2019 um 10:42 UTC · 33m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    ApplicationDependency APIGem Index API
    1. 31. Januar 2019 um 10:42 UTCinvestigating

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

    2. 31. Januar 2019 um 10:55 UTCmonitoring

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

    3. 31. Januar 2019 um 13:21 UTCresolved

      This incident has been resolved.

    Elevated Errors

    Beginn 13. Januar 2019 um 16:53 UTC · 6h 50m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    ApplicationDependency API
    1. 13. Januar 2019 um 16:53 UTCmonitoring

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

    2. 13. Januar 2019 um 23:44 UTCresolved

      This incident has been resolved.

    Unexpected Problem

    Beginn 13. Januar 2019 um 09:05 UTC · 31m

    OutageKritischer Vorfall
    Betroffene Komponenten
    ApplicationDependency APIGem Index API
    1. 13. Januar 2019 um 09:23 UTCinvestigating

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

    2. 13. Januar 2019 um 09:33 UTCmonitoring

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

    3. 13. Januar 2019 um 09:36 UTCresolved

      This incident has been resolved.

    Problems installing gems

    Beginn 1. Januar 2019 um 14:02 UTC · 24m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Gem Index API
    1. 1. Januar 2019 um 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. Januar 2019 um 14:19 UTCmonitoring

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

    3. 1. Januar 2019 um 14:26 UTCresolved

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

    Unexpected Problem

    Beginn 25. Dezember 2017 um 20:08 UTC · 13h 48m

    IssuesGeringfügiger Vorfall
    1. 25. Dezember 2017 um 20:08 UTCinvestigating

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

    2. 25. Dezember 2017 um 20:21 UTCmonitoring

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

    3. 25. Dezember 2017 um 22:25 UTCinvestigating

      We are currently investigating this issue.

    4. 26. Dezember 2017 um 09:56 UTCresolved

      The site has been stable since 19:15 UTC.

    Unexpected problem

    Beginn 2. Mai 2017 um 14:58 UTC · 1h 9m

    IssuesGeringfügiger Vorfall
    1. 2. Mai 2017 um 14:58 UTCinvestigating

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

    2. 2. Mai 2017 um 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. Mai 2017 um 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. Mai 2017 um 16:07 UTCresolved

      This incident has been resolved.