Incident Library
Applied filters ComponentIn-memory cacheFactorAutomation amplificationOrganisationUpstashClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. IL-0376 A maintenance update set off needless full syncs between Upstash Redis replicas in eu-west-1, slowing the databases
    Upstash2025
    Symptoms

    On 25 February 2025, regional Upstash Redis databases in AWS eu-west-1 slowed down after a maintenance update, with very high CPU load on databases that have a replica in that region. Latency stayed high until about 21:23 UTC, even after the affected databases were unthrottled at 15:06 UTC.

    High latencySustained high node CPU
    Trigger

    A maintenance update to the regional Upstash Redis databases in AWS eu-west-1.

    Root cause
    Software defect
    Component
    In-memory cacheDatabase replication
    Contributing factor
    Automation amplification
    Remediation
    • Added more resources to the regional eu-west-1 cluster
    • Unthrottled the affected databases at 15:06 UTC and enabled more throughput
    Action items
    • Deploy a fix that stops regional databases from starting unnecessary full synchronisations
    • Contact regional database users about migrating to Upstash Global, which does not have this issue
    View case
Check your cluster for this

This case involves In-memory cache and Database replication. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

Open kubegap

By root cause1

Software defect1 case

Component
In-memory cacheDatabase replication
Contributing factor
Automation amplification
Organisation
Upstash
  1. IL-0376 A maintenance update set off needless full syncs between Upstash Redis replicas in eu-west-1, slowing the databases
    Upstash2025