32 incidentes de Rubygems registrados desde noviembre de 2015, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.
Estamos experimentando un nivel elevado de errores y actualmente estamos investigando el problema.
Se ha determinado la cuestión y se está aplicando una solución.
Se ha aplicado una solución y estamos monitoreando los resultados.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando problemas en partes de RubyGems.org. Gem instala y empuja puede ser lento o fallando, y el sitio en sí puede no cargar de forma fiable.
Hemos rastreado el problema a uno de nuestros proveedores de aguas arriba y estamos observando de cerca mientras el servicio se recupera. Las instalaciones y los empujes deben estar trabajando de nuevo, aunque todavía puede ver el error ocasional mientras las cosas se resuelven.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
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.
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.
This incident has been resolved and we've re-enabled account registrations
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigating response time degradation on rubygems.org and index.rubygems.org
We have identified the cause of the performance degradation and have begun restoring normal service. We're continuing to monitor the situation.
This incident has been resolved.
We are currently experiencing a partial outage affecting RubyGems.org search functionality. Our team is investigating the issue and working towards a resolution.
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.
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.
This incident has been resolved
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.
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.
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.
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.
This incident has been resolved.
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.
We have heard that our appeal has successfully been escalated within the Google Safe Browsing team, and they are working to resolve things.
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.
We're experiencing an elevated level of errors and are currently looking into the issue.
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.
Our CDN partner has identified the issue and a fix is being implemented.
Our CDN provider has applied a fix and over the last few minutes we saw traffic levels and errors return to normal.
This incident has been resolved.
We're experiencing an elevated level of errors and are currently looking into the issue.
The elevated 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/1rbr326kjsmt.
Fastly has implemented a fix and we are monitoring the results.
This incident has been resolved.
We're experiencing an elevated level of DNS errors and are currently looking into the issue.
DNS seems to be resolving again. We continue to monitor the situation.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're currently investigating users being unable to access rubygems.org
We are continuing to investigate this issue.
This incident has been resolved
We are currently investigating DNS resolution errors for some users.
DNS resolution should be working for all users now.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're experiencing an elevated level errors and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Over the last 20 minutes we experienced an elevated level of errors. We are currently monitoring the issue.
This incident has been resolved.
We're experiencing an unexpected problem and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. All gems should be included in the versions API again.
We're experiencing an elevated level of errors and are currently looking into the issue.
All services should be working now. We will continue to monitor.
We are currently investigating this issue.
The site has been stable since 19:15 UTC.
We are aware of reports that services are unavailable in some regions. We're looking into it now!
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.
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.
This incident has been resolved.
