down
Is RubyGems down?
Check RubyGems availability, incident history, downtime reports, and website performance.
https://rubygems.org/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for RubyGems
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-08 16:11:32 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
RubyGems outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
RubyGems website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-08 16:11:32 UTC.
Checked address: https://rubygems.org/
DNS lookup: 3 ms · TCP connection: 2 ms · TLS handshake: 4 ms. Certificate expires 2027-03-09; trusted connection: yes.
100%
Successful website checks (24h)
21 successful / 21 measurable checks
14 ms
Median response time
70 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
RubyGems official status · fetched 2026-11-08 16:51:14 UTC
87 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Gem Downloads | operational |
| Fastly Frankfurt (FRA) | operational |
| Application | operational |
| Dependency API | operational |
| Fastly Sydney (SYD) | operational |
| Fastly Amsterdam (AMS) | operational |
| Gem Index API | operational |
| Upstream Provider: AWS | operational |
| Fastly Ashburn (IAD) | operational |
| Upstream Provider: DNSimple Name Servers | operational |
| Fastly Singapore (SIN) | operational |
| Fastly London (LCY) | under maintenance |
| Upstream Provider: Fastly | under maintenance |
| Fastly Denver (DEN) | operational |
| Fastly London (LHR) | operational |
| Fastly New Zealand (AKL) | operational |
| Fastly Chicago (ORD) | operational |
| Fastly New Zealand (WLG) | operational |
| Fastly Stockholm (BMA) | operational |
| Fastly Hong Kong (HKG) | operational |
| Fastly Miami (MIA) | operational |
| Fastly Dallas (DFW) | operational |
| Fastly Melbourne (MEL) | operational |
| Fastly Osaka (ITM) | operational |
| Fastly San Jose (SJC) | operational |
| Fastly Brisbane (BNE) | operational |
| Fastly Seattle (SEA) | operational |
| Fastly Dubai (FJR) | operational |
| Fastly Perth (PER) | operational |
| Fastly Frankfurt (HHN) | operational |
| Fastly Paris (CDG) | operational |
| Fastly Madrid (MAD) | operational |
| Fastly Boston (BOS) | operational |
| Fastly Minneapolis (MSP) | operational |
| Fastly Johannesburg (JNB) | operational |
| Fastly Montreal (YUL) | operational |
| Fastly Toronto (YYZ) | operational |
| Fastly Sāo Paulo (GRU) | operational |
| Fastly Tokyo (HND) | operational |
| Fastly Tokyo (TYO) | operational |
| Fastly Singapore (QPG) | operational |
| Fastly Tokyo (NRT) | operational |
| Fastly Copenhagen (CPH) | operational |
| Fastly Dublin (DUB) | operational |
| Fastly Helsinki (HEL) | operational |
| Fastly London (LON) | operational |
| Fastly Manchester (MAN) | operational |
| Fastly Marseille (MRS) | operational |
| Fastly Milan (MXP) | operational |
| Fastly Oslo (OSL) | operational |
| Fastly Vienna (VIE) | operational |
| Fastly Munich (MUC) | operational |
| Fastly Chennai (MAA) | operational |
| Fastly Mumbai (BOM) | operational |
| Fastly New Delhi (DEL) | operational |
| Fastly Ashburn (BWI) | operational |
| Fastly Ashburn (DCA) | operational |
| Fastly Ashburn (WDC) | operational |
| Fastly Atlanta (FTY) | operational |
| Fastly Atlanta (PDK) | operational |
| Fastly Chicago (CHI) | operational |
| Fastly Chicago (MDW) | operational |
| Fastly Chicago (PWK) | operational |
| Fastly Columbus (CMH) | operational |
| Fastly Columbus (LCK) | operational |
| Fastly Dallas (DAL) | operational |
| Fastly Houston (IAH) | operational |
| Fastly Jacksonville (JAX) | operational |
| Fastly Kansas City (MCI) | operational |
| Fastly Los Angeles (BUR) | operational |
| Fastly Los Angeles (LGB) | operational |
| Fastly Minneapolis (STP) | operational |
| Fastly New York (LGA) | operational |
| Fastly Newark (EWR) | operational |
| Fastly Palo Alto (PAO) | operational |
| Fastly Phoenix (PHX) | operational |
| Fastly Portland (PDX) | operational |
| Fastly St. Louis (STL) | operational |
| Fastly Vancouver (YVR) | operational |
| Fastly Cape Town (CPT) | operational |
| Fastly Buenos Aires (EZE) | operational |
| Fastly Bogota (BOG) | operational |
| Fastly Curitiba (CWB) | operational |
| Fastly Rio de Janeiro (GIG) | operational |
| Fastly Santiago (SCL) | operational |
| Fastly Sāo Paulo (CGH) | operational |
| Fastly Lima (LIM) | operational |
Official incident timeline
Elevated Errors · resolved · 2026-08-19T06:59:38.680Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
The issue has been identified and a fix is being implemented.
- · investigating
We're experiencing an elevated level of errors and are currently looking into the issue.
Degraded service on RubyGems.org · resolved · 2026-07-24T12:06:10.022Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We've traced the problem to one of our upstream providers and are watching closely as service recovers. Installs and pushes should be working again, though you may still see the occasional error while things settle.
- · identified
We're currently investigating problems across parts of RubyGems.org. Gem installs and pushes may be slow or failing, and the site itself may not load reliably.
Temporarily disabling new user registrations · resolved · 2026-05-16T05:12:19.021Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This incident has been resolved and we've re-enabled account registrations
- · identified
The malicious spam activity against rubygems.org has stopped. The bot accounts responsible have been blocked and removed, and the 500+ malicious packages pushed during the attack have been yanked from the registry. Registrations will remain closed while we coordinate with Fastly to enable WAF protection and tighten rate limiting on account creation. We expect this to take two to three days. We'll post another update when we're closer being ready to re-enable user registrations. Gem installs an
- · identified
Due to an ongoing DDoS attack against rubygems.org, we have temporarily disabled registrations. We'll share an update once we've made changes to protect legitimate users and prevent further abuse.
Rubygems.org is experiencing a partial outage · resolved · 2026-04-06T21:04:02.214Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
A fix has been implemented and we are monitoring the results.
- · identified
The issue has been identified and a fix is being implemented.
- · investigating
We are currently investigating this issue.
Degraded performance · resolved · 2026-03-31T10:59:29.718Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · monitoring
We have identified the cause of the performance degradation and have begun restoring normal service. We're continuing to monitor the situation.
- · investigating
We're currently investigating response time degradation on rubygems.org and index.rubygems.org
Search degredation · resolved · 2026-02-12T22:36:07.721Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved
- · monitoring
The issue affecting RubyGems.org search has been resolved. We are monitoring the service to ensure stability and will provide an update if any further issues arise.
- · identified
We've identified and are addressing the underlying issue affecting RubyGems.org search. Service restoration is underway, and we anticipate normal operations to resume within the next hour.
- · investigating
We are currently experiencing a partial outage affecting RubyGems.org search functionality. Our team is investigating the issue and working towards a resolution.
Gem pushes with attestation failing · resolved · 2025-10-27T21:05:53.577Z
Product match: components.
Read the provider’s incident report
- · resolved
This incident has been resolved.
- · identified
This issue has been resolved. Please ensure that you're using the latest version of the https://github.com/rubygems/release-gem in your Github Actions tasks.
- · identified
We're continuing to work with the sigstore team to help resolve users being unable to gem pushes with attestations. For the time being, we recommend users update their workflows to retry gem pushes without attestations.
- · identified
We have implemented a fix for gem pushes that use attestations on rubygems.org. However, gems that rely on the release-gem GitHub Action (https://github.com/rubygems/release-gem) to deploy to rubygems.org will still experience errors. The release-gem action will automatically retry pushing to rubygems.org without attestations, which continue to function as expected. We are closely monitoring the situation and collaborating with the Sigstore team to resolve this issue.
- · identified
Gem pushes utilising the attestation feature are failing and will respond with an application error. We've identified the issue and are currently working to push a fix.
Google Safe Browsing flag as malware · resolved · 2023-05-12T01:01:20.952Z
Product match: components.
Read the provider’s incident report
- · 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.
Recovery tracker
No recent recovery can be established from available evidence.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: 14 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of RubyGems.
No active incidents recorded.
- Spectrum Availability Issue in Phoenix · monitoring
- Fedramp Customers have Delayed Purges · identified
About RubyGems status on Iszdown
Check RubyGems availability, incident history, downtime reports, and website performance.
This page combines the available RubyGems report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
87 product-matched official components are listed above. Latest public website measurement: 2026-11-08T16:11:32.000Z.
Visit the official RubyGems website · Official provider status · How it works
What to check when RubyGems is not working
These are troubleshooting suggestions, not a list of currently reported problems.
RubyGems will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
RubyGems is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent RubyGems outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Elevated Errors | 149 min | resolved | |
| Degraded service on RubyGems.org | 37 min | resolved | |
| Rubygems.org is experiencing a partial outage | 30 min | resolved | |
| Degraded performance | 61 min | resolved | |
| Search degredation | 134 min | resolved |
Frequently asked questions about RubyGems
Is RubyGems down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-08T17:06:44.000Z.
How many RubyGems outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-07T17:00:00.000Z to 2026-11-08T17:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does RubyGems show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every RubyGems feature.
When was RubyGems status last updated?
The latest status observation was 2026-11-08T16:51:14.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has RubyGems had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow RubyGems or report a problem?
Use “Watch this service” to save RubyGems in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to RubyGems
Check a related product separately; its status can differ from RubyGems.