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.
The latest update from Redis Cloud.
State
Resolved
Started
13 d ago
2026-10-20 06:47 UTC
Lasted
10 h 36 min
until 2026-10-20 17:23 UTC
Worst impact
Degraded
Timeline
8 updatesUpdate
10 h 36 min 100%
Updates
Times in UTCAs posted by Redis Cloud
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.
Our teams are continuing with the recovery procedures and are actively working to restore all affected services. We will provide further updates as they occur. If you require assistance, please contact our Support team.
The GCP power outage affecting the europe-west2 region and europe-west2-b zone has been mitigated, and the underlying GCP infrastructure has partially recovered. Our teams have initiated recovery procedures and are actively working to restore all affected services. We will continue monitoring the recovery and provide further updates as they become available. If you require assistance, please contact our Support team.
We continue to monitor the disruption affecting GCP europe-west2 and europe-west2-b while working to restore services. Please contact Support if you need assistance.
We are still actively monitoring the service disruption affecting the GCP europe-west2 region and europe-west2-b zone. Our teams remain focused on restoring services as quickly as possible. We will provide further updates as they become available. If you require assistance, please contact our Support team.
Our teams are actively monitoring the service disruption affecting the GCP europe-west2 region and europe-west2-b zone. Service restoration remains our highest priority, and we will provide further updates as they become available. For assistance, please contact our Support team.
We continue to closely monitor the issues affecting GCP region europe-west2 and zone europe-west2-b. Restoring services remains our top priority. If you have questions or need assistance, please contact our support team
We are aware of an issue in GCP region europe-west2 (London), zone europe-west2-b and are actively investigating. If you experience any impact, please contact our Support team.
Redis Cloud in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
3 h 31 min
This incident
3.0× the median
Other Redis Cloud incidents
All incidentsRedis 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