Upstash statusLiveFetched seconds agoSource: status.upstash.com
Is Upstash down?
Live status check · All systems operational
Live status pulled from status.upstash.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Upstash status
Upstash is the serverless data platform (per-request pricing) behind Redis, Kafka, Vector, and QStash, a cult favorite among serverless and edge-function teams. Incidents are usually scoped to a single product or a single region rather than the whole platform.
Components and surfaces that can break
- Surface 01
Upstash Redis (HTTP REST and native Redis protocol endpoints, per region).
- Surface 02
Upstash Kafka and Upstash Vector.
- Surface 03
QStash and the management console.
Recent Upstash incidents
Upstash maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Upstash is actually down
REST and native Redis are separate transports
Upstash exposes both an HTTP REST API and the native Redis protocol. A REST degradation does not always mean the native protocol is also affected, and vice versa. If one transport is failing, switching client libraries is sometimes enough to keep traffic flowing.
Confirm your region first
Upstash status is reported per region (us-east-1, eu-west-1, ap-southeast-1, etc.). An incident in us-east-1 says nothing about your eu-west-1 database. Check the component matching your project's region before assuming Upstash is fully down.
QStash is Upstash's own scheduler
If you rely on QStash to fire HTTP cron jobs and QStash is degraded, those scheduled jobs may skip silently. Crontap is an external scheduler that does not share infrastructure with Upstash, so the two can coexist, with Crontap acting as the fallback that keeps firing while QStash recovers.
Keep firing through the incident
Schedule your own Upstash health check with Crontap
Scheduled Upstash data jobs (cache warmup, Kafka offset checks, vector index refresh) are HTTP cron when wrapped in a small endpoint that talks to Upstash. The wry part: if you have been using QStash as your scheduler, Crontap is the external alternative that does not go down with Upstash. The two can coexist on the same project.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Upstash status: FAQ
- Where can I see the official Upstash status?
- status.upstash.com publishes component status for Redis, Kafka, Vector, QStash, and the console, broken out per region. The history page tracks past incidents with post-mortems.
- What happens to my QStash schedules during an Upstash incident?
- If QStash itself is degraded, scheduled deliveries can be delayed or skipped. QStash retries failed deliveries once it recovers, but a scheduled fire-time that lands inside the incident window is not guaranteed to run on time. For workloads where the schedule must hold, run a parallel Crontap schedule against the same endpoint as a backstop.
- Does Upstash retry commands during an outage?
- The REST client and most Redis SDKs retry transient errors with backoff, but they do not buffer commands across a full regional outage. Treat Upstash like any other remote dependency: catch errors at the call site, and have your app degrade gracefully (serve stale cache, queue writes locally) instead of assuming the command landed.