← Back to the carnage
REDIS

🟡 AWS me-east-1 zone mec1az2 is having a whole identity crisis—Redis clusters in that zone are now experiencing the full spectrum of chaos: connectivity dropout, latency spikes, and the kind of temporary suffering that makes engineers check their resume. Pro tip: your data's still there, it's just taking the scenic route to get to you. (Auto-resolved: no updates in 24h)

⏰ Mar 01, 2026 Fixed (for now) spotted via status_rss

// The official story

AWS me-central-1 Zone Issue

// Status page says

Mar 1 , 14:33 UTC Investigating - Type - network issues Status - investigating We are aware of an ongoing AWS service disruption impacting an availability zone within the me-east-1 region (zone ID: mec1az2). This zone may appear under different availability zone names across AWS accounts. As a result, some Redis Cloud clusters located in this zone may experience connectivity issues, increased latency, or temporary s

🔗 Official status page (for the PR-approved version)

https://status.redis.io/incidents/hhvm3jqd2kh0

Redis's Greatest Hits

🟢 REDIS Feb 07, 2026
🟡 Redis Azure customers discovering that 'cloud' apparently means 'sometimes invisible.' Network gremlins are loose and engineers are pretending to know where they came from. (Auto-resolved: no updates in 24h)