Redis: Urgent maintenance
Timeline of updates
- update
➡️ Monitoring — Urgent maintenance applies to all of the resources with the following pattern in their endpoint: c100.us-east-1-4
- 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
48057622c66b9663…
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: none) posted by Redis, started 2026-03-10 17:08 UTC, resolved after 30 min, 2 update(s).
- Title
- Urgent maintenance
- Vendor
- Redis
- Date
- URL
- https://rewindex.com/company/redis/incidents/74e0b30d-77a1-40c2-9c66-ba10649f10ed
Redis profileRecent Redis incidentsAll outages on March 10, 2026Redis in March 2026MarkdownJSON