Upstash
operationalLast checked 17 Oct 2026, 06:42 UTC. Homepage reachable.
- EU-CENTRAL-1
- AWS - US-EAST-1
- N. Virginia, USA (us-east-1)
- AWS - EU-WEST-1
- N. California, USA (us-west-1)
- US-EAST-1
- AWS EU-WEST-1
- GCP - US-CENTRAL1
- Oregon, USA (us-west-2)
- AWS US-EAST-1
- Frankfurt, Germany (eu-central-1)
- AWS US-WEST-1
- Ireland (eu-west-1)
- AWS AP-NORTHEAST-1
- Singapore (ap-southeast-1)
- Upstash Console
- GCP US-CENTRAL-1
- Sydney, Australia (ap-southeast-2)
- Context7
- AWS US-WEST-2
- Mumbai, India (ap-south-1)
- Context7 Console
- AWS EU-CENTRAL-1
- Tokyo, Japan (ap-northeast-1)
No open incidents on the vendor status page.
Recent history
- Brief connection proxy degradation in us-east-1 (resolved)
- Intermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1) (resolved)
- Upstash Console login issue (resolved)
- Message Persistence Issue — QStash us-east-1 (resolved)
- Fly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW Region (resolved)
- QStash us-east-1 - URL Publish Errors (resolved)
- Upstash Redis Partial Service Disruption (resolved)
- QStash EU Region — Degraded Performance (postmortem)