← Back to Redis Cloud History
unknown✓ Resolved
GCP Issue Affecting Redis Cloud in asia-east1
Status
resolved
Duration
2d 3h
Updates
11
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
Status changed to resolved
monitoring
Google Cloud has confirmed that the remediation in asia-east1-c is complete and the zone is stable.
Following final validation, all affected Redis Cloud subscriptions are operating normally and no further impact has been observed. This incident is resolved.
If you have any questions or need assistance, please contact https://redis.io/support
monitoring
Google Cloud has confirmed that the zone-wide rollback in asia-east1-c has been successfully completed and the zone is now fully stabilized.
Our teams are completing the remaining recovery actions and final health validation across the affected subscriptions. We will provide a further update once these activities are complete.
If you have any questions or need assistance, please contact https://redis.io/support
monitoring
Google Cloud has confirmed that the rollback in the asia-east1-c zone has progressed to the final remaining physical host. Google is awaiting final confirmation that the rollback has completed successfully and that the zone is fully stabilized.
We continue to monitor affected subscriptions and recommend avoiding configuration changes in the asia-east1 region until Google confirms the remediation is complete.
We will provide a further update once Google confirms full remediation.
If you have any questions or need assistance, please contact https://redis.io/support
monitoring
Google Cloud has confirmed that the rollback of the recent update in the asia-east1-c zone remains in its initial phase, with workloads being safely migrated from the affected infrastructure as part of the mitigation efforts.
Databases configured with high availability (replication) remain unaffected. Databases without high availability in the affected zone may continue to experience brief restarts or client reconnections while remediation is in progress.
We continue to closely monitor affected subscriptions and recommend holding configuration changes in the asia-east1 region until remediation is confirmed complete.
If you have any questions or need assistance, please contact https://redis.io/support/.
monitoring
Google Cloud’s remediation efforts for the asia-east1-c zone remain ongoing, with no material change since our previous update. Databases configured with high availability (replication) remain unaffected. Databases without high availability in the affected zone may continue to experience brief restarts or client reconnections while remediation is in progress.We continue to closely monitor affected subscriptions and recommend holding configuration changes in the asia-east1 region until remediation is confirmed complete.
We will share additional information as it becomes available.
If you have any questions or need assistance, please contact https://redis.io/support/
monitoring
Google Cloud's remediation of the asia-east1-c zone issue remains in progress and is taking longer than initially expected. Databases configured with high availability (replication) were not impacted. Databases without high availability in this zone may continue to experience brief restarts or client reconnections until remediation is complete. We are monitoring affected subscriptions and recommend holding configuration changes in asia-east1 until resolved.
If you have any questions or need assistance, please contact https://redis.io/support/
monitoring
GCP has identified the cause of the infrastructure issue in the asia-east1-c zone and is rolling back a recent update there. Google estimates the rollback will take up to 5 more hours. The asia-east1-a and asia-east1-b zones are not affected.
Until the rollback is complete, some databases with nodes in asia-east1-c may still see brief node restarts or client reconnections. Our teams are monitoring affected subscriptions around the clock, working directly with Google Cloud. As a precaution, we recommend avoiding configuration changes to databases in asia-east1 until this incident is resolved.
We will share further updates as soon as the situation changes.
If you have any questions or need assistance, please contact https://redis.io/support/
monitoring
We continue to monitor the ongoing service disruptions affecting the GCP asia-east1-c region and remain in close contact with GCP as they work towards restoring stability. Our teams are closely tracking and monitoring the situation and will share further updates as more information becomes available.
If you have any questions or need assistance, please contact https://redis.io/support/
monitoring
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/
investigating
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.
📊 TECHNICAL DETAILS
Internal ID
9fadbe8a-a6da-4642-85de-b51bf6fe3b60
External ID
9cfa4e6d-ce41-456e-a86c-9225e607bb58
🕐 Started
🔄 Last Updated
✓ Resolved
UNKNOWN
Impact Level
2d 3h
Total Duration
11
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed