rewindex

ChangesRedisGCP Issue Affecting Redis Cloud in asia-east1

Redis: Incident updated: GCP Issue Affecting Redis Cloud in asia-east1

Incident updateNormal progress (rule, 100%)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.

AddedUpdate#1
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

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.

History of this incident

Saturday, November 7

3 incident changes

Friday, November 6

6 incident changes

Thursday, November 5

2 incident changes

Cite this

Incident updated: GCP Issue Affecting Redis Cloud in asia-east1 on Redis’s status page, changed 2026-11-07 18:38 UTC (change 10 of 11).

Title
Incident updated: GCP Issue Affecting Redis Cloud in asia-east1
Vendor
Redis
Date
URL
https://rewindex.com/change/r5ae943a0efb674

All Redis changesRedis profileMarkdownJSON