# Problems accessing RubyGems.org using TLS 1.1

- Provider: [RubyGems.org](https://down.guide/providers/rubygems)
- Confidence: Confirmed
- Impact: Operational
- lasted 0m
- started 2017-05-02 12:00 UTC
- id: DWN-8faa4d0a2f
- Official page: http://stspg.io/5PZ8

## Updates from RubyGems.org
### 2017-05-02 12:00 UTC: resolved
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 disabling support for TLS 1.1. We will announce these dates.

From the builder: does your app depend on RubyGems.org? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=rubygems) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention RubyGems.org.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-8faa4d0a2f), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.