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: 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/

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-06 08:08 UTC (change 3 of 11).

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

All Redis changesRedis profileMarkdownJSON