PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if RubyGems is down?

PulseWatch evaluates user reports and replay-approved automated evidence for RubyGems. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported RubyGems issues today?

As of Oct 2, 2026 13:36 UTC, 0 users had reported issues with RubyGems in the previous 24 hours.

How can I report a RubyGems outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is RubyGems down right now?

NormalOfficial status last polled Oct 2, 2026 12:58 UTCrubygems.org Official status page

RubyGems package registry for Ruby

Are you on the RubyGems team and see something inaccurate? Report it to us. We respond within one business day.

Is RubyGems down right now?

No. RubyGems has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 2, 2026 13:36 UTC

Normal

RubyGems is operating normally

As of Oct 2, 2026 13:36 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Aug 19, 2026 07:27 UTC

Trend

0/15m

Baseline

5/hr

Observed health

100/100

2 of 2 assessed samples succeeded within their latency target.

5/5 responses validated in the last 15 minutes. 3 successful samples have no qualified latency target.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for RubyGems.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for RubyGems. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

RubyGems outage on May 5 — 19-minute disruption

May 5, 05:13 PM → May 5, 05:33 PM · 19 minutes · high

RubyGems experienced an outage on May 5, 2026, which was detected via user reports. The incident was resolved on May 5, 2026, at 17:33 UTC.

Peak reports

in 15 min

Total reports

during outage

Duration

19 minutes

until recovery

Impact

Users reported issues with RubyGems, leading to the detection of this outage. While the exact nature of the user-visible impact, such as specific features affected or geographical regions, was not recorded, the incident was identified through these reports. Our monitoring platform did not record specific issue types or top impacted regions during this period.

Outage timeline

May 5, 05:13 PM
PulseWatch detected elevated report volume (high severity)
May 5, 05:15 PM
Peak of 0 reports in 15 minutes (baseline 1.3)
May 5, 05:33 PM
Report volume returned to baseline — incident resolved

Official updates

May 5, 05:13 PM
RubyGems status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.99%

90-day uptime

99.89%

Calculated from RubyGems's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.