Skip to content
Upstash · Data and observabilityFeb 25, 2025, 14:03 UTC

Regional AWS eu-west-1 Cluster Performance Degradation Issue

MinorDatabaseUpdated 17h ago
Feb 25, 14:03 UTCFeb 25, 21:23 UTC
Duration
7h 20m
Impact
Minor
Root cause
Database
Upstash, 90 days
5 incidents
Affected
AWS EU-WEST-1Redis Regional - AWS EU-WEST-1
Status page

Final update

### Incident Summary During a maintenance update to the regional Upstash Redis databases in AWS eu-west-1, several databases hosted in that region has unnecessarily triggered a full synchronisation between their primary and backup replicas. ### Root Cause A full synchronisation is the invalidation of the whole data in the target replica and starting a fresh re-population from the source replica. Under normal circumstances, full synchronisation is required only in cases where the data integrity is lost in one of the replicas, which was not the case here. ### Impact This incident impacted the performance of regional databases on AWS eu-west-1 only. Full synchronisation has caused a very high CPU load and caused a performance degradation on some of the databases that has a replica in this region. Moreover, our system throttles the databases that are going through this operation to allocate more CPU to the synchronisation to finish it sooner. No data or consistency has been lost. ### Resolution As a quick remediation, we have unthrottled affected databases on 15:06UTC and enabled more throughput, however high latency has still been observed until the full synchronisation is completed

Timeline

  1. Postmortem · Feb 26, 12:29 UTC
    ### Incident Summary During a maintenance update to the regional Upstash Redis databases in AWS eu-west-1, several databases hosted in that region has unnecessarily triggered a full synchronisation between their primary and backup replicas. ### Root Cause A full synchronisation is the invalidation of the whole data in the target replica and starting a fresh re-population from the source replica. Under normal circumstances, full synchronisation is required only in cases where the data integrity is lost in one of the replicas, which was not the case here. ### Impact This incident impacted the performance of regional databases on AWS eu-west-1 only. Full synchronisation has caused a very high CPU load and caused a performance degradation on some of the databases that has a replica in this region. Moreover, our system throttles the databases that are going through this operation to allocate more CPU to the synchronisation to finish it sooner. No data or consistency has been lost. ### Resolution As a quick remediation, we have unthrottled affected databases on 15:06UTC and enabled more throughput, however high latency has still been observed until the full synchronisation is completed on 21:23UTC. A fix has been prepared to avoid this unnecessary full synchronisation on regional databases, and will be deployed shortly. This issue is not present on Upstash Global databases, which is our new generation infrastructure and is now our default offering. We will reach out to our regio
  2. Resolved · Feb 25, 21:23 UTC
    This incident has been resolved.
  3. Monitoring · Feb 25, 20:54 UTC
    A fix has been implemented and we are monitoring the results.
  4. Identified · Feb 25, 14:03 UTC
    Regional AWS eu-west-1 cluster is experiencing performance degradation, and we are adding more resources to the cluster.

More from Upstash

Full history

Also caused by database

All
StartedIncidentDuration
Sep 1309:16 UTCIncident with several GitHub ServicesGitHub1h 29m
Sep 921:53 UTCINC20000211Snowflake1h 58m
Aug 2616:17 UTCIssues performance is degraded in the USSentry4h 19m
Aug 1216:16 UTCIncident with Pull Requests and IssuesGitHub25m
Aug 818:57 UTCAccount Registration, Droplets, and Related ServicesDigitalOcean6h 3m
Jul 2817:41 UTCEvent ingestion and retrieval delays for some North America customersHubSpot2h

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.