RubyGems outage, 2 May 2017

Problems accessing RubyGems.org using TLS 1.1

Started
Resolved
2 May 2017, 12:00 UTC
Impact
Not stated

Last update from RubyGems

We received reports of legacy software being unable to access RubyGems.org. Specifically anyone using TLS 1.1. This is common on older operating systems like Ubuntu Precise 12.04. We quickly realized that our CDN provider had disabled TLS 1.1 today due to a previously announced deprecation of TLS 1.1. Unfortunately we hadn't taken steps to avoid this action today. Once we realized what had happened we migrated back to a configuration that allowed TLS 1.1. I'm sorry if this impacted you today. Everything should be working again now. If you are still having issues please submit a help ticket. The migration today is a short term change, and in the future we will be permanently disablin...

2 May 2017, 12:00 UTC

Read the full incident on the official RubyGems status page

Is RubyGems down now?

This page is the record of one past incident. For the live status, see Is RubyGems down right now? - it reads the official status page every 2 minutes.

Other RubyGems incidents

  1. Elevated Errors

  2. Degraded service on RubyGems.org

  3. Temporarily disabling new user registrations

  4. Rubygems.org is experiencing a partial outage

  5. Degraded performance

  6. Search degredation

  7. Gem pushes with attestation failing

  8. Google Safe Browsing flag as malware

All recorded RubyGems incidents