ChangesRedisGCP Issue Affecting Redis Cloud in asia-east1
Redis: Incident updated: GCP Issue Affecting Redis Cloud in asia-east1
Incident updateNormal progress (typesafe/jev-1.13-20260917, 54%)Changed status.redis.io (opens in new tab)
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Redis removed; blue is what they added. Muted text is unchanged context.
Before: monitoring
After: resolved
Before: not present
After: 2026-11-07 19:20 UTC
Before: not present
After: 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.
Before: 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.
After: removed
Before: 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/
After: removed
Before: not present
After: 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/
Before: not present
After: 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/
Before: 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/
After: removed
Before: not present
After: 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/
Before: 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/
After: removed
Before: 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/
After: removed
Before: not present
After: 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/
Before: not present
After: 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/
Before: 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/
After: removed
Before: 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/.
After: removed
Before: not present
After: 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/.
Before: not present
After: 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
Before: 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
After: removed
Before: not present
After: 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
Before: 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
After: removed
Before: not present
After: 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
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-11-07 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1423a3b0b0e75df7…After captured
In the 2026-11-07 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c206a745cfd3690a…
History of this incident
Saturday, November 7
3 incident changes
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1this change
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
Friday, November 6
6 incident changes
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
Thursday, November 5
2 incident changes
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
- Normal progressIncident
Incident updateGCP Issue Affecting Redis Cloud in asia-east1
Cite this
Incident updated: GCP Issue Affecting Redis Cloud in asia-east1 on Redis’s status page, changed 2026-11-07 19:38 UTC (change 11 of 11).
- Title
- Incident updated: GCP Issue Affecting Redis Cloud in asia-east1
- Vendor
- Redis
- Date
- URL
- https://rewindex.com/change/rad6cfa2782859c