Loading status…
Upstash status · Data & Backend · checked (1m ago)
Also searched as Upstash Redis, Upstash Vector, Upstash QStash.
No — Upstash is not down. All Upstash systems are reported operational.
According to Upstash's official status page, Upstash was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Upstash's feed reported no outage in 100.00% of our checks.
Everything above is read from Upstash's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Upstash in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Upstash sells serverless data infrastructure billed per request — Redis, a vector database, and QStash for queues and scheduling — all reachable over HTTP so they work from edge and serverless runtimes that cannot hold a TCP connection.
The status page separates the products and reports regionally, which matters because an Upstash database is created in one region and global replication is an option rather than the default. QStash and the Redis REST API are reported separately, so scheduled jobs can be failing while reads and writes are entirely healthy.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Upstash's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Upstash was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Upstash's status endpoint.
Upstash has published 27 incidents in the last 12 months, the 20 most recent shown here. Only what Upstash posted itself — not every problem users hit.
resolved · Sep 9, 12:00 PM (10d ago)
resolved · Sep 3, 08:00 AM (16d ago)
resolved · Aug 28, 10:20 PM (22d ago)
resolved · Jul 22, 08:50 AM (59d ago)
resolved · Jul 16, 06:30 AM (65d ago)
resolved · Jun 25, 03:23 PM (86d ago)
postmortem · Jun 23, 04:22 PM (88d ago)
resolved · Jun 23, 06:05 AM (89d ago)
postmortem · Jun 19, 09:11 AM (92d ago)
resolved · Jun 4, 10:10 AM (107d ago)
resolved · May 29, 08:18 PM (113d ago)
resolved · May 22, 11:27 PM (120d ago)
resolved · May 14, 03:47 PM (128d ago)
postmortem · May 12, 09:49 AM (130d ago)
postmortem · May 11, 03:05 PM (131d ago)
postmortem · May 8, 09:46 AM (134d ago)
postmortem · May 5, 02:24 PM (137d ago)
resolved · Apr 2, 06:45 PM (170d ago)
resolved · Mar 27, 03:30 PM (176d ago)
postmortem · Mar 6, 01:50 PM (197d ago)
Free and pay-as-you-go tiers have hard request and bandwidth limits that throttle or reject with errors resembling an outage. Latency from a serverless function in one region to a database in another is physics, not degradation — check where each one lives. QStash retries failed deliveries on a schedule, so a webhook that has not arrived yet may simply be mid-backoff.
