Changes / Upstash / Degraded Performance

Upstash: Critical incident: Degraded Performance

Summary

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 diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: degradation (model (Jev), 97%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Degraded Performance
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: postmortem
AddedStart time#4
Before: not present
After: 2025-06-11 06:51 UTC
AddedResolved time#5
Before: not present
After: 2025-06-11 10:02 UTC
AddedAffected components#6
Before: not present
After: Frankfurt, Germany (eu-central-1), Ireland (eu-west-1), London, UK (eu-west-2), Mumbai, India (ap-south-1), N. California, USA (us-west-1), N. Virginia, USA (us-east-1), Ohio, USA (us-east-2), Oregon, USA (us-west-2), Redis Global - Frankfurt, Germany (eu-central-1), Redis Global - Ireland (eu-west-1), Redis Global - London, UK (eu-west-2), Redis Global - Mumbai, India (ap-south-1), Redis Global - N. California, USA (us-west-1), Redis Global - N. Virginia, USA (us-east-1), Redis Global - Ohio, USA (us-east-2), Redis Global - Oregon, USA (us-west-2), Redis Global - São Paulo, Brazil (sa-east-1), Redis Global - Singapore (ap-southeast-1), Redis Global - Sydney, Australia (ap-southeast-2), Redis Global - Tokyo, Japan (ap-northeast-1), São Paulo, Brazil (sa-east-1), Singapore (ap-southeast-1), Sydney, Australia (ap-southeast-2), Tokyo, Japan (ap-northeast-1)
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating this issue.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdatemonitoring#9
Before: not present
After: A fix has been implemented and we are monitoring the results.
AddedUpdateresolved#10
Before: not present
After: This incident has been resolved.
AddedUpdatepostmortem#11
Before: not present
After: 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.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: Degraded Performance (this change)
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.
Major incident

All Upstash changes → · Upstash profile · Markdown · JSON