Redis: Clusters – Instance Failure
Timeline of updates
- identified
We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c240
- identified
We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c240
- identified
Our teams continue to investigate the instance failure issue in order to resolve it. We will continue to update as we progress. Thank you for your continued patience.
- identified
Our teams are still working on the instance failure issue in order to restore the service. Thank you for your patience.
- identified
We have identified the issue and are currently working on the resolution steps. Thank you for your patience.
- resolved
The incident has been resolved. We will continue to monitor system performance to ensure ongoing stability. If you continue to experience any issues, please contact our support team for assistance.
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
ec4a670c9ef9952c…
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 2026-05-10 10:53 UTC, resolved after 4.8 h, 6 update(s).
- Title
- Clusters – Instance Failure
- Vendor
- Redis
- Date
- URL
- https://rewindex.com/company/redis/incidents/ad11116e-8c5e-4da1-a664-80faf730132a
Redis profileRecent Redis incidentsAll outages on May 10, 2026Redis in May 2026MarkdownJSON