RubyGems experienced a minor incident on October 15, 2025 affecting Application, lasting 12d 14h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 15, 2025, 06:56 AM 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.
- identified Oct 15, 2025, 11:04 PM 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 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.
- identified Oct 17, 2025, 02:15 AM 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.
- identified Oct 27, 2025, 08:15 PM 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.
- resolved Oct 27, 2025, 09:05 PM UTC
This incident has been resolved.