- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, us
- Down Index
- 26of 100
What to do
Check whether you use RubyGems.org in eu, us. 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 1h 9m it lasted.
Anything that failed between 2017-05-02 14:58 UTC and 2017-05-02 16:07 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 4
- investigating
We are aware of reports that services are unavailable in some regions. We're looking into it now!
provider
- monitoring
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.
provider
- monitoring
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.
provider
- resolved
This incident has been resolved.
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-d6162b515e
Is RubyGems.org still down?
No, this incident was resolved 2017-05-02 16:07 UTC. For RubyGems.org's live state, see https://down.guide/rubygems.
How long did it last?
1h 9m, from 2017-05-02 14:58 UTC to 2017-05-02 16:07 UTC, by the times RubyGems.org posted.
What was affected?
RubyGems.org named in eu, us.
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.