Redis Cloud did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-11-05 15:34 UTC. This page shows the end time when Redis Cloud marks it resolved.

How do I get alerts for Redis Cloud?

Subscribe to the Redis Cloud live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Redis Cloud. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

Redis CloudIncident ·

GCP Issue Affecting Redis Cloud in asia-east1

Q: What happened?

Redis Cloud reported "GCP Issue Affecting Redis Cloud in asia-east1" on its status page at 2026-11-05 15:34 UTC. Redis Cloud has intermittent service disruptions in the asia-east1 region. The disruptions come from a GCP issue. Redis Cloud monitors the affected services and works with Google Cloud Support.

DegradedOfficial update

Redis Cloud has intermittent service disruptions in the asia-east1 region. The disruptions come from a GCP issue. Redis Cloud monitors the affected services and works with Google Cloud Support.

State

Monitoring

Started

Ongoing for

1 h 25 min

Worst impact

Degraded

Timeline

2 updates

15:3415:5516:1616:3816:59

DegradedUpdate postedTimes in UTC

Acknowledged

5 min 6%

Monitoring

1 h 20 min 94%

Updates

Times in UTC

As posted by Redis Cloud

Monitoring

We are investigating intermittent service disruptions caused by a GCP issue in the asia-east1 region. Our team is actively monitoring the affected services and working with Google Cloud Support. We will provide further updates as more information becomes available.

Acknowledged

Redis Cloud in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

3 h 31 min

This incident

59% shorter than 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

Redis Cloud·GCP region europe-west2 and zone europe-west2-b issues

All environments have been returned to a full operational state at this time. Please contact our Support team if there are questions or assistance is needed.

Resolved

Redis Cloud·Redis Cloud – Temporary Issues with Redis IRIS

This issue is now resolved, if you see or experience any additional issues, please contact https://redis.io/support/

Resolved

Redis Cloud·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.

Resolved

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.live/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.live/feed.xml?providers=redis

Slack

/feed subscribe https://outages.live/feed.xml?providers=redis

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane