Redis: Network Issues
Timeline of updates
- resolved
We are currently investigating network issues to some resources that have the following pattern in their endpoint: crce177
- update
Incident is 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
bb5d7cb1969c5c45…
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-04-01 01:46 UTC, resolved after 6 min, 2 update(s).
- Title
- Network Issues
- Vendor
- Redis
- Date
- URL
- https://rewindex.com/company/redis/incidents/03606778-c03c-41b4-8886-d3689f4ea8c8
Redis profileRecent Redis incidentsAll outages on April 1, 2026Redis in April 2026MarkdownJSON