Redis Outage History

Redis resources with endpoint pattern "c14" underwent urgent maintenance for 35 minutes. All affected resources experienced service disruption during the maintenance window. The incident was resolved after monitoring confirmed successful completion of the maintenance work.

Redis resources with endpoint pattern c100.us-east-1-4 underwent urgent maintenance affecting service availability. The maintenance impacted all resources matching this specific endpoint pattern in the us-east-1-4 region. The incident was resolved after 33 minutes of downtime.

A Redis instance failure occurred affecting resources with the endpoint pattern c6.eu-west-mz.1 in the eu-west region. The incident was classified as minor and lasted 11 minutes before being resolved. The service was restored and the incident was marked as resolved.

Redis Cloud performed scheduled periodic maintenance on their admin console and REST API for 17 minutes, which impacted user access to the management interface at cloud.redis.io. Database connectivity remained unaffected throughout the maintenance window, and the incident was resolved without further complications.

Redis experienced urgent maintenance affecting all resources with "c320" in their endpoint pattern. The maintenance lasted 10 minutes and was classified as a minor incident. The issue was resolved through the completion of the scheduled maintenance work.

Redis experienced urgent maintenance affecting all resources with the "c17.us-east-1-4" endpoint pattern in the US East region. The maintenance lasted 1.2 hours and has been resolved.

An AWS service disruption affected availability zone mec1az2 in the me-central-1 region, causing Redis Cloud clusters in that zone to experience connectivity issues, increased latency, and temporary service interruptions. The incident expanded to impact multiple availability zones (mec1az2 and mec1az3) with extended restoration timelines due to underlying infrastructure issues. The incident was resolved after 55 hours with Redis operating within regional constraints, and customers were advised to consider migrating workloads to alternate regions while AWS recovery efforts continued.

A Redis instance failure occurred in the me-central-1b availability zone, affecting resources with endpoints containing that pattern. The incident lasted 19 minutes and has been resolved.