outages.live
Live

Upstash

Upstash is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

32

QStash

EU-CENTRAL-1 Operational
90 days agoNo incidentsToday
US-EAST-1 Operational
90 days agoNo incidentsToday

Vector

AWS - US-EAST-1 Operational
90 days agoNo incidentsToday
AWS - EU-WEST-1 Operational
90 days agoNo incidentsToday
GCP - US-CENTRAL1 Operational
90 days agoNo incidentsToday

Redis Global

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

Redis Regional

AWS EU-WEST-1 Operational
90 days agoNo incidentsToday
AWS US-EAST-1 Operational
90 days agoNo incidentsToday
AWS US-WEST-1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow Upstash

Your coding agent knows when Upstash is down, and tells you when a failure is theirs, not yours. You can also get Upstash incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "upstash" and tell me if Upstash has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=upstash
Slack
/feed subscribe https://outages.live/feed.xml?providers=upstash

Go from tracking outages to fixing production issues with Polylane.

Try Polylane