RubyGems.org

Is RubyGems.org Down Right Now? Check if there is a current outage ongoing.

RubyGems.org is currently undergoing Planned Maintenance

Last checked from RubyGems.org's official status page

Historical record of incidents for RubyGems.org

Report: "Google Safe Browsing flag as malware"

Last update
resolved

Success! Google Safe Browsing has removed the malware flag from rubygems.org. Special thanks are owed to everyone who connected us to the Chrome and Safe Browsing teams, and the team members who assisted in clearing this up.

identified

We have heard that our appeal has successfully been escalated within the Google Safe Browsing team, and they are working to resolve things.

identified

Google Safe Browsing has flagged the entire rubygems.org domain as malware, impacting all users of the Chrome, Safari, and Firefox browser. The underlying issue appears to be an incorrect malware flag applied to all versions of a gem from the metasploit family. In our investigation we’ve identified that the same library is also available from GitHub and many Linux and BSD distro packages. We continue investigating, sharing information and working with Google to resolve this as soon as possible. For the time being, there are no other issues: the website can be accessed as normal if you bypass the warning. Gem downloads and pushes continue working as normal.

Report: "Elevated Errors"

Last update
resolved

This incident has been resolved.

monitoring

Our CDN provider has applied a fix and over the last few minutes we saw traffic levels and errors return to normal.

identified

Our CDN partner has identified the issue and a fix is being implemented.

investigating

The elevated 503 and 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/vpk0ssybt3bj.

investigating

We're experiencing an elevated level of errors and are currently looking into the issue.

Report: "Unexpected Errors"

Last update
resolved

This incident has been resolved.

monitoring

Fastly has implemented a fix and we are monitoring the results.

identified

The elevated 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/1rbr326kjsmt.

investigating

We're experiencing an elevated level of errors and are currently looking into the issue.

Report: "Elevated DNS Errors"

Last update
resolved

This incident has been resolved.

monitoring

We are continuing to monitor for any further issues.

monitoring

DNS seems to be resolving again. We continue to monitor the situation.

investigating

We're experiencing an elevated level of DNS errors and are currently looking into the issue.

Report: "Users unable to access RubyGems.org"

Last update
resolved

This incident has been resolved

investigating

We are continuing to investigate this issue.

investigating

We're currently investigating users being unable to access rubygems.org

Report: "DNS resolution errors for some users"

Last update
resolved

DNS resolution should be working for all users now.

identified

We are currently investigating DNS resolution errors for some users.

Report: "Unexpected Problem"

Last update
resolved

This incident has been resolved.

monitoring

A fix has been implemented and we are monitoring the results.

investigating

We are currently investigating this issue.

Report: "Unexpected Problem"

Last update
resolved

This incident has been resolved.

monitoring

A fix has been implemented and we are monitoring the results.

investigating

We're experiencing an elevated level errors and are currently looking into the issue.

Report: "Elevated Errors"

Last update
resolved

This incident has been resolved.

monitoring

Over the last 20 minutes we experienced an elevated level of errors. We are currently monitoring the issue.

Report: "Unexpected Problem"

Last update
resolved

This incident has been resolved.

monitoring

A fix has been implemented and we are monitoring the results.

investigating

We're experiencing an unexpected problem and are currently looking into the issue.

Report: "Problems installing gems"

Last update
resolved

This incident has been resolved. All gems should be included in the versions API again.

monitoring

A fix has been implemented and we are monitoring the results.

identified

We have received reports of some gems not being able to be installed. We have identified the issue and we are working on resolving it. Gems published before 2015-08-23 may be unlisted on the versions API.

Report: "Unexpected Problem"

Last update
resolved

The site has been stable since 19:15 UTC.

investigating

We are currently investigating this issue.

monitoring

All services should be working now. We will continue to monitor.

investigating

We're experiencing an elevated level of errors and are currently looking into the issue.

Report: "Unexpected problem"

Last update
resolved

This incident has been resolved.

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.

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.

investigating

We are aware of reports that services are unavailable in some regions. We're looking into it now!

Report: "Problems accessing RubyGems.org using TLS 1.1"

Last update
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.

Report: "Gem index delays"

Last update
resolved

All gems appear to be installing successfully.

monitoring

All gems should be indexed now. We are monitoring to make sure new gems are added in a timely manor.

identified

The issue has been identified and a fix is being implemented.

investigating

We're aware that new gems published may not be added to the new gem index in a timely manor. Our team is investigating. Running 'bundle install --full-index', as well as 'gem install' are unaffected by this delay.

Report: "DNS Problems"

Last update
resolved

This incident has been resolved.

monitoring

We are continuing to monitor the DNS propagation.

identified

We have identified and fixed the problem. Service will be restored as soon as DNS propagates.

investigating

We are receiving reports of DNS problems. We are investigating.

Report: "Elevated Errors"

Last update
resolved

This incident has been resolved.

investigating

We're experiencing an elevated level of errors and are currently looking into the issue.

Report: "Elevated response times"

Last update
resolved

This incident has been resolved.

monitoring

A fix has been implemented and we are monitoring the results.

investigating

We're experiencing elevated response times and are currently looking into the issue.

Report: "Elevated Errors"

Last update
resolved

This incident has been resolved.

monitoring

A fix has been implemented and we are monitoring the results.

investigating

We're experiencing an elevated level of errors and are currently looking into the issue.

Report: "Problems with gem downloads and Dependency API"

Last update
resolved

This incident has been resolved.

monitoring

A fix has been implemented and we are monitoring the results.

investigating

All gem downloads are working again.

investigating

We are aware that some gem downloads are not working and the Dependency API is not working for some versions of bundler. Our team is looking into it. Sorry for the inconvenience – we’ll have a solution for this soon!

Report: "Unexpected problems with the Dependencies API."

Last update
resolved

This incident has been resolved.

monitoring

We've resolved the issue and the Dependency API should be working normally again.

identified

Heads up: we're running on the legacy dependency API for now. bundle installs might be slow!

investigating

We’re investigating some issues with our dependencies API not updating - sorry folks!

Report: "New gems not available"

Last update
resolved

This incident has been resolved.

monitoring

We have identified the problem and deployed a fix.

investigating

We are aware that some newly pushed gems are not able to be installed when the dependency API is used. This is used by most versions of bundler and RubyGems. Our team is looking into it. Sorry for the inconvenience – we’ll have a solution for this soon!

Report: "Degraded Performance on Dependency API"

Last update
resolved

The dependency API has been stable, answering all requests, for about two hours. We'll keep an eye on it, but everything seems resolved for now.

monitoring

Service has been restored. After many infrastructure, configuration, and code changes today we have found the problem. The dependency API should be returning results in a reasonable time with no errors now. We're continuing to monitor things.

investigating

We're aware of intermittent errors on the dependency api. We saw an increase in traffic yesterday and the API was having trouble responding in a timely manner. We've made several changes to the service in the last 24 hours to reduce the error rates. Our failures are down but we are still seeing some requests fail with HTTP 500 errors. We're working to fix the remaining errors, but in the meantime you can work around this by running: `bundle install --full-index`.

Report: "CDN Outage"

Last update
resolved

Error rates have returned to normal. Everything should be working now.

monitoring

Our provider is reporting that service is returning to normal. We're still seeing higher than normal error rates so we are continuing to monitor closely.

identified

Our CDN provider is experiencing an outage right now. Gem installs might not be working in some regions. We'll update when we know more.

Report: "Unexpected problem"

Last update
resolved

High load on our database is causing errors right now.