outages.live
Live

RubyGems

RubyGems is reporting maintenance

Checked 46 s ago Maintenance

Service Under Maintenance

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

2 h 29 min

Longest incident

2 h 29 min

Components

86
Gem Downloads Operational
90 days agoNo incidentsToday
Application Operational
90 days ago1 day with an incidentToday
Dependency API Operational
90 days ago1 day with an incidentToday
Gem Index API Operational
90 days ago1 day with an incidentToday
Upstream Provider: AWS Operational
90 days agoNo incidentsToday
Upstream Provider: DNSimple Name Servers Operational
90 days agoNo incidentsToday

Upstream Provider: Fastly

Fastly Frankfurt (FRA) Operational
90 days agoNo incidentsToday
Fastly Sydney (SYD) Operational
90 days agoNo incidentsToday
Fastly Amsterdam (AMS) Operational
90 days agoNo incidentsToday
Fastly Ashburn (IAD) Operational
90 days agoNo incidentsToday
Fastly Singapore (SIN) Operational
90 days agoNo incidentsToday
Fastly London (LCY) Maintenance
90 days agoNo incidentsToday
Fastly Denver (DEN) Operational
90 days agoNo incidentsToday
Fastly London (LHR) Operational
90 days agoNo incidentsToday
Fastly New Zealand (AKL) Operational
90 days agoNo incidentsToday
Fastly Chicago (ORD) Operational
90 days agoNo incidentsToday
Fastly New Zealand (WLG) Operational
90 days agoNo incidentsToday
Fastly Stockholm (BMA) Operational
90 days agoNo incidentsToday
Fastly Hong Kong (HKG) Operational
90 days agoNo incidentsToday
Fastly Miami (MIA) Operational
90 days agoNo incidentsToday
Fastly Dallas (DFW) Operational
90 days agoNo incidentsToday
Fastly Melbourne (MEL) Operational
90 days agoNo incidentsToday
Fastly Osaka (ITM) Operational
90 days agoNo incidentsToday
Fastly San Jose (SJC) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Aug 19, 2026

Duration2 h 29 min04:30 to 06:59Elevated ErrorsPartial outage

This incident has been resolved.

Affected components

1
  • Fastly London (LCY)Upstream Provider: FastlyMaintenance

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=rubygems
Slack
/feed subscribe https://outages.cc/feed.xml?providers=rubygems

Go from tracking outages to fixing production issues with Polylane.

Try Polylane