rewindex

ChangesRedisGCP Issue Affecting Redis Cloud in asia-east1

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

Incident updateNot classified yetChanged 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: 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/

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.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayThursday, November 5Thu, Nov 5

2 incident changes

Cite this

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

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

All Redis changesRedis profileMarkdownJSON