Elevated Errors
This incident has been resolved.
The latest update from RubyGems.
State
Resolved
Started
75 d ago
2026-08-19 04:30 UTC
Lasted
2 h 29 min
until 2026-08-19 06:59 UTC
Worst impact
Partial outage
Timeline
4 updatesInvestigating
36 min 24%
Identified
53 min 35%
Monitoring
1 h 40%
Updates
Times in UTCAs posted by RubyGems
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We're experiencing an elevated level of errors and are currently looking into the issue.
Affected components
3RubyGems in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
2 h 29 min
This incident
About the median
Follow RubyGems
Your coding agent knows when RubyGems is down, and tells you when a failure is theirs, not yours. You can also get RubyGems incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "rubygems" and tell me if RubyGems has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=rubygems/feed subscribe https://outages.cc/feed.xml?providers=rubygemsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane