Live

GCP US-Central1 issue

GCP has confirmed that the US-Central1 event is resolved. Our services are operating normally, and we are marking this issue as closed. If you have any questions or need assistance, please contact support@redis.com.

The latest update from Redis Cloud.

State

Resolved

Started

61 d ago

2026-09-01 16:00 UTC

Lasted

3 h 31 min

until 2026-09-01 19:31 UTC

Worst impact

Degraded

Timeline

4 updates
16:0016:5317:4518:3819:31
DegradedUpdate postedTimes in UTC

Update

3 h 31 min 100%

Updates

Times in UTC

As posted by Redis Cloud

Update2026-09-01 19:30 UTC

GCP has confirmed that the US-Central1 event is resolved. Our services are operating normally, and we are marking this issue as closed. If you have any questions or need assistance, please contact support@redis.com.

Update2026-09-01 19:21 UTC

We continue to closely monitor the GCP US-Central1 event. Our services remain operational and are performing normally. For questions or assistance, please contact support@redis.com

Update2026-09-01 17:27 UTC

We continue to monitor the ongoing GCP US-Central1 event. Currently, our services are operating normally. For questions or assistance, please contact support@redis.com

Update2026-09-01 16:01 UTC

We are aware of an issue in GCP US-Central1 and are actively investigating. If you experience any impact, please contact our Support team.

Redis Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

3 h 31 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

10 h 36 min
median 3 h 31 min
90 days agoToday

Other Redis Cloud incidents

All incidents

Follow Redis Cloud

Your coding agent knows when Redis Cloud is down, and tells you when a failure is theirs, not yours. You can also get Redis Cloud 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 "redis" and tell me if Redis Cloud 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=redis
Slack
/feed subscribe https://outages.cc/feed.xml?providers=redis

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane