Is rubygems.org down or not working?

What happened to rubygems.org, why did the website go down and not work? Here you can see who else is having the same problem with rubygems.org, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, rubygems.org is working fine, but single failures are possible. If rubygems.org does not work for you, then report your problem and write a comment.
Add comment

What to do if the site rubygems.org is not available? Try our guide.

rubygems.org outage reports in the last 24 hours

rubygems.org - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
RubyGems.org | your community gem host
Protocol:
https
Status code:
200
Page size:
18.7 KB
Response time:
0.376sec.
IP:
151.101.1.227
Response headers:
connection: close
content-length: 19224
content-type: text/html; charset=utf-8
x-frame-options: SAMEORIGIN
x-xss-protection: 0
x-content-type-options: nosniff
x-permitted-cross-domain-policies: none
referrer-policy: strict-origin-when-cross-origin
cross-origin-opener-policy: same-origin
link: </assets/application-d325a391fb7bcd24972cb78a07941d83e096a15f1362dfeaf43b7de73ad2c0f8.css>; rel=preload; as=style; nopush
cache-control: max-age=0, private, must-revalidate
content-security-policy: default-src 'self'; font-src 'self' https://fonts.gstatic.com; img-src 'self' https://secure.gaug.es https://gravatar.com https://www.gravatar.com https://secure.gravatar.com https://*.fastly-insights.com https://avatars.githubusercontent.com; object-src 'none'; script-src 'self' 'sha256-E/byyx9V9Hm6EynIlwLNkMfOiDTB+Bct7NSCF5xsqL4=' https://secure.gaug.es https://www.fastly-insights.com 'nonce-3277fd4bab529b62b8976a268d25c502'; style-src 'self' https://fonts.googleapis.com 'nonce-3277fd4bab529b62b8976a268d25c502'; connect-src 'self' https://s3-us-west-2.amazonaws.com/rubygems-dumps/ https://*.fastly-insights.com https://fastly-insights.com https://api.github.com http://localhost:*; form-action 'self' https://github.com/login/oauth/authorize; frame-ancestors 'self'; base-uri 'self'; report-uri https://csp-report.browser-intake-datadoghq.com/api/v2/logs?dd-api-key=pub852fa3e2312391fafa5640b60784e660&dd-evp-origin=content-security-policy&ddsource=csp-report&ddtags=service%3Arubygems.org%2Cversion%3Af71762f23f67f1d7e6478dcdf7db4bc6e443c594%2Cenv%3Aproduction%2Ctrace_id%3A4331536846518060085
set-cookie: _rubygems_session=9v0mGsQ5Scq4LRLHoNoDR6UPJDSM2Te3LIAaAfbhDwmtueSo4Xdequm62RA%2FJLlZMXyAKkIpfoqnDYmH3mJada8i%2FMCT8cpNfwHB%2Be6TZ90%2BPwjUkDyswEGm9jzLOYrzM05SXobMrLEN306TUS9l%2FzU%2FmLpR0MTO2X4eVsjjn%2BZuacorTONWgra6so3VXMt3nbtSv88oe2VgN16ZWYNAGuABEJeOTgkec35z3rtcDWgqKd6nWNKW9u7HOIKTwBJC%2F3glRqPHdmXXM%2F%2F0h%2BeNn9794bULMEngCg%3D%3D--wF5gNWzNCGrbgQwx--1FnawLYOFeOcEAFMLlLatw%3D%3D; path=/; secure; httponly; samesite=strict
x-request-id: 1bcc3e79-8423-4fd4-8867-73d8f7da6aaf
x-runtime: 0.009041
strict-transport-security: max-age=31536000
x-backend: F_Rails 52.89.193.101:443
accept-ranges: bytes
date: Tue, 01 Oct 2024 15:52:35 GMT
via: 1.1 varnish
x-served-by: cache-ams21078-AMS
x-cache: MISS
x-cache-hits: 0
x-timer: S1727797955.193854,VS0,VE319
vary: Accept-Encoding
etag: "f143438436d531e6264046052df7a379"
server: RubyGems.org

SEO headers

h1 Find, install, and publish RubyGems.
h2 179,602,317,385 downloads & counting

How to solve problems with rubygems.org

Errors on the rubygems.org website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of rubygems.org on your own.