GCP Issue Affecting Redis Cloud in asia-east1
Redis Cloud reports intermittent service disruptions in the GCP asia-east1 region. The provider is monitoring the situation. Services are recovering, but disruptions may continue.
State
Monitoring
Started
Ongoing for
9 h 26 min
Worst impact
Degraded
Timeline
3 updatesAcknowledged
5 min 1%
Monitoring
9 h 21 min 99%
Updates
Times in UTCAs posted by Redis Cloud
Services are recovering, but intermittent disruptions may continue in the GCP asia-east1 region. GCP has confirmed that they are actively investigating the ongoing issue as a high priority. Our teams continue to monitor service health and work closely with GCP. We will share further updates as more information becomes available. If you have any questions or need assistance, please contact https://redis.io/support/
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.
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.
Redis Cloud in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
5
Median duration
3 h 31 min
This incident
2.7× the median
Other Redis Cloud incidents
All incidentsRedis 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.
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/
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.
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.
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.
https://outages.cc/feed.xml?providers=redis/feed subscribe https://outages.cc/feed.xml?providers=redisFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane