Redis: Instance failure
Timeline of updates
- update
➡️ Investigating — We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c170.us-east-1-mz
- update
➡️ Resolved — This incident has been resolved.
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 this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-04 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4f1616f7d36a5ec1…
Impact, status and times are the vendor’s own, as last archived. View on status.redis.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Redis, started 2025-07-18 01:33 UTC, resolved after 18 min, 2 update(s).
- Title
- Instance failure
- Vendor
- Redis
- Date
- URL
- https://rewindex.com/company/redis/incidents/32908cf9-115c-492d-8de9-f25e88ef9ad7
Redis profileRecent Redis incidentsAll outages on July 18, 2025Redis in July 2025MarkdownJSON