Where does this status come from?

From Upstash's own status page API at https://status.upstash.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Upstash's words.

How can my agent or app check Upstash status?

Fetch https://upbutler.com/status/upstash/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"upstash"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Upstash's?

Add "upstash" to the dependencies of your UpButler workspace. When one of your monitors fails while Upstash has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Upstash down?

Right now

No. Upstash is operational.

No incidents reported.

Read from status.upstash.com 18 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/upstash/status.agent.json

MCP: upstream_status {"service":"upstash"}

Serverless Redis, QStash, Workflow and Vector. A QStash incident delays scheduled jobs instead of failing requests.

What Upstash reports

Operational

Taken as is from Upstash's own status page API. Incident titles and component names below are theirs.

Open status.upstash.com

UpButler's independent probe

There is no keyless endpoint of Upstash that says anything useful, so UpButler does not probe it. To check your own Upstash account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Upstash components

32 operational

QStash

EU-CENTRAL-1Operational
US-EAST-1Operational

Vector

AWS - US-EAST-1Operational
AWS - EU-WEST-1Operational
GCP - US-CENTRAL1Operational

Redis Global

N. Virginia, USA (us-east-1)Operational
N. California, USA (us-west-1)Operational
Oregon, USA (us-west-2)Operational
Frankfurt, Germany (eu-central-1)Operational
Ireland (eu-west-1)Operational
Singapore (ap-southeast-1)Operational
Sydney, Australia (ap-southeast-2)Operational
Mumbai, India (ap-south-1)Operational
Tokyo, Japan (ap-northeast-1)Operational
São Paulo, Brazil (sa-east-1)Operational
Ohio, USA (us-east-2)Operational
London, UK (eu-west-2)Operational
Council Bluffs, Iowa, North America (us-central1)Operational
Ashburn, Virginia, North America (us-east4)Operational
Tokyo, Japan, APAC (asia-northeast1)Operational
St. Ghislain, Belgium, Europe (europe-west1)Operational

Redis Regional

AWS EU-WEST-1Operational
AWS US-EAST-1Operational
AWS US-WEST-1Operational
AWS AP-NORTHEAST-1Operational
GCP US-CENTRAL-1Operational
AWS US-WEST-2Operational
AWS EU-CENTRAL-1Operational

Upstash ConsoleOperational
Context7Operational
Context7 ConsoleOperational
BoxOperational

Upstash incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-09-29 15:36	Brief connection proxy degradation in us-east-1	minor	under a minute

Tell your outage from Upstash's

Declare that your project depends on Upstash. When one of your monitors fails while Upstash has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - upstash

Ask before you retry

curl -s https://upbutler.com/status/upstash/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "upstash",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Upstash down right now?: No. As of 2026-10-10 05:13 UTC, Upstash is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Upstash's own status page API at https://status.upstash.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Upstash's words.
How can my agent or app check Upstash status?: Fetch https://upbutler.com/status/upstash/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"upstash"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Upstash's?: Add "upstash" to the dependencies of your UpButler workspace. When one of your monitors fails while Upstash has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in databases and data

UpButler is not affiliated with Upstash. Status and incident text belong to Upstash and are read from their public status source; the probe result is UpButler's own measurement.