Skip to main content
RubyGems.org

Problems accessing RubyGems.org using TLS 1.1

Degraded Lasted 0m · started · RubyGems.org's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on RubyGems.org. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2017-05-02 12:00 UTC and 2017-05-02 12:00 UTC may need a replay.
  • Subscribe to RubyGems.org's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=rubygems works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RubyGems.org 1

  1. 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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-8faa4d0a2f

Is RubyGems.org still down?

No, this incident was resolved 2017-05-02 12:00 UTC. For RubyGems.org's live state, see https://down.guide/rubygems.

How long did it last?

0m, from 2017-05-02 12:00 UTC to 2017-05-02 12:00 UTC, by the times RubyGems.org posted.

What caused it?

RubyGems.org hasn't published a root cause. If it does, it shows here.

Where does this come from?

RubyGems.org's official status page, https://status.rubygems.org, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.