
Upstash Status
Real-time updates of Upstash issues and outages
Upstash status is Operational
EU-CENTRAL-1
Upstash Box
You're checking on Upstash - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
We are currently investigating this issue.
Between 01:18 and 04:03 UTC, customers were unable to access running boxes or perform create, read, update, or delete operations. Running containers were not affected and continued operating throughout. The issue has been fully resolved and all box operations are functioning normally.
We are taking all necessary measures to prevent this from happening again. We apologize for the disruption.
Upstash Outage Survival Guide
Upstash Components
Upstash Redis Global
Upstash Database Free Tier
AWS US-EAST-1
N. Virginia, USA (us-east-1)
AWS US-WEST-1
N. California, USA (us-west-1)
AWS EU-WEST-1
Oregon, USA (us-west-2)
AWS AP-NORTHEAST-1
Frankfurt, Germany (eu-central-1)
GCP US-CENTRAL-1
Ireland (eu-west-1)
AWS US-WEST-2
Singapore (ap-southeast-1)
Sydney, Australia (ap-southeast-2)
AWS EU-CENTRAL-1
Mumbai, India (ap-south-1)
Tokyo, Japan (ap-northeast-1)
São Paulo, Brazil (sa-east-1)
Ohio, USA (us-east-2)
London, UK (eu-west-2)
Council Bluffs, Iowa, North America (us-central1)
Ashburn, Virginia, North America (us-east4)
Tokyo, Japan, APAC (asia-northeast1)
Upstash Global
St. Ghislain, Belgium, Europe (europe-west1)
Upstash Redis Regional
AWS EU-WEST-1
AWS US-EAST-1
AWS US-WEST-1
AWS AP-NORTHEAST-1
GCP US-CENTRAL-1
AWS US-WEST-2
AWS EU-CENTRAL-1
Upstash Kafka
Upstash Vector
EU-WEST-1
AWS - US-EAST-1
EU-CENTRAL-1
US-EAST-1
AWS - EU-WEST-1
GCP - US-CENTRAL1
Upstash Console
Upstash Context7
Upstash Context7 Console
Upstash QStash
EU-CENTRAL-1
We are currently investigating this issue.
US-EAST-1
Upstash Box
Between 01:18 and 04:03 UTC, customers were unable to access running boxes or perform create, read, update, or delete operations. Running containers were not affected and continued operating throughout. The issue has been fully resolved and all box operations are functioning normally.
We are taking all necessary measures to prevent this from happening again. We apologize for the disruption.