Vendor record
RubyGems.org
Checked
Front door check counts and RubyGems.org’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against RubyGems.org in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every RubyGems.org product, region or your app worked.
How we count front door checksRubyGems.org says
Incident posts from RubyGems.org’s status page, with its titles, impact levels and times. They say what RubyGems.org chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents RubyGems.org posted, last 30 days
Most recent records · all dates
Elevated Errors
MajorRubyGems.org’s postStarted, per RubyGems.org
Latest status RubyGems.org postedMonitoring. No resolution posted.
Degraded service on RubyGems.org
MajorRubyGems.org’s postStarted, per RubyGems.org
Closed in our record(25d 17h)
Temporarily disabling new user registrations
Not specifiedRubyGems.org’s postStarted, per RubyGems.org
Closed in our record(73d 2h)
Rubygems.org is experiencing a partial outage
MajorRubyGems.org’s postStarted, per RubyGems.org
Closed in our record(4d 14h)
Degraded performance
MinorRubyGems.org’s postStarted, per RubyGems.org
Closed in our record(6d 10h)
Your code, your dependencies
See which of your code paths call RubyGems.org
Connect GitHub or GitLab to find where your public or private repository uses RubyGems.org. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add RubyGems.org status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is RubyGems.org currently down?
RubyGems.org's latest recorded status is Degraded. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did RubyGems.org last have an outage?
The most recent closed incident record began 84 days ago and spans 25d 17h. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for RubyGems.org?
No. CheckUpstream does not run front door checks against RubyGems.org. The incident history on this page is what RubyGems.org reported, not a measure of how often it was available.
How do I monitor RubyGems.org in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track RubyGems.org?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.