Upstash incident

Performance Degradation

Minor Resolved View vendor source →

Upstash experienced a minor incident on June 10, 2025 affecting N. Virginia, USA (us-east-1), lasting 4h 45m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2025, 07:23 AM UTC
Resolved
Jun 10, 2025, 12:08 PM UTC
Duration
4h 45m
Detected by Pingoru
Jun 10, 2025, 07:23 AM UTC

Affected components

N. Virginia, USA (us-east-1)

Update timeline

  1. investigating Jun 10, 2025, 07:23 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 10, 2025, 07:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 10, 2025, 12:08 PM UTC

    This incident has been resolved.

  4. postmortem Jun 11, 2025, 11:37 AM UTC

    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.