Redis: Connectivity issue on c265.
Timeline of updates
- investigating
We are currently investigating connectivity issues with some resources that have the following pattern in their endpoint: c265. Some resources in this cluster may be impacted. We will continue to update until the resolution.
- identified
We have identified the issue and are currently working on the resolution steps. Thank you for your patience.
- resolved
Our teams continue to focus on the resolution steps to fully resolve this issue. Thank you for your continued patience.
- resolved
Our teams have made progress in the resolution effort and are actively applying mitigation steps. We are continuing to monitor recovery and work toward full resolution.
- resolved
The issue has been fully resolved. Should you encounter any remaining issues, please contact our support team via our support portal.
Thank you for your patience.
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
6ea7ccb228a54739…
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-13 16:07 UTC, resolved after 3.0 h, 5 update(s).
- Title
- Connectivity issue on c265.
- Vendor
- Redis
- Date
- URL
- https://rewindex.com/company/redis/incidents/64801e76-2493-41a1-a328-c0956508685f
Redis profileRecent Redis incidentsAll outages on May 13, 2026Redis in May 2026MarkdownJSON