Companies / Upstash / incidents
Upstash: Degraded Performance
Upstash reported critical degraded performance affecting regional and Redis Global components from 2025-06-11 06:51 UTC to 2025-06-11 10:02 UTC (3 h 10 min). OS maintenance updates changed networking components and triggered restarts, causing EC2 nodes to fail health checks and disrupting high availability; a fix was implemented at 06-11 09:20 UTC.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Redis Global - Singapore (ap-southeast-1)Singapore (ap-southeast-1)Mumbai, India (ap-south-1)Redis Global - Mumbai, India (ap-south-1)Redis Global - Sydney, Australia (ap-southeast-2)Sydney, Australia (ap-southeast-2)Redis Global - São Paulo, Brazil (sa-east-1)São Paulo, Brazil (sa-east-1)Ireland (eu-west-1)Redis Global - Ireland (eu-west-1)Oregon, USA (us-west-2)Redis Global - Oregon, USA (us-west-2)London, UK (eu-west-2)Redis Global - London, UK (eu-west-2)N. Virginia, USA (us-east-1)Redis Global - N. Virginia, USA (us-east-1)Frankfurt, Germany (eu-central-1)Redis Global - Frankfurt, Germany (eu-central-1)Redis Global - Tokyo, Japan (ap-northeast-1)Tokyo, Japan (ap-northeast-1)Ohio, USA (us-east-2)Redis Global - Ohio, USA (us-east-2)N. California, USA (us-west-1)Redis Global - N. California, USA (us-west-1)
Timeline of updates
- investigating
We are currently investigating this issue.
- investigating
We are continuing to investigate this issue.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
- postmortem
A routine system maintenance operation at the OS level led to the application of system updates across multiple EC2 instances in our clusters in several AWS regions. These updates included changes to networking components, which inadvertently triggered restarts. As a result, several EC2 nodes failed health checks and temporarily dropped out of the cluster, disrupting high availability and causing partial connectivity issues for some clients and operations. We have since reproduced the issue in a controlled environment and verified the root cause. To prevent a recurrence, we are updating our node maintenance strategy to ensure greater control over the timing and impact of system-level changes and excluding networking components from automated upgrades.
Rewindex changes for this incident
- Critical incident: Degraded Performance 2025-06-11 06:51 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Upstash profile · Recent Upstash incidents · Markdown · JSON