Is Upstash Down?

No — Upstash is up

Reachable from all 8 checked regions

Average response time: 119ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.upstash.com

Upstash uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

167ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

59-day clean streak

Sep 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra

55ms

DNS 30ms TCP 1ms TLS 8ms TTFB 54ms

gru

73ms

DNS 51ms TCP 1ms TLS 8ms TTFB 72ms

iad

58ms

DNS 21ms TCP 2ms TLS 9ms TTFB 56ms

jnb

170ms

DNS 24ms TCP 0ms TLS 78ms TTFB 169ms

lax

88ms

DNS 39ms TCP 1ms TLS 23ms TTFB 87ms

lhr

58ms

DNS 33ms TCP 4ms TLS 7ms TTFB 56ms

nrt

273ms

DNS 244ms TCP 2ms TLS 8ms TTFB 271ms

ord

179ms

DNS 128ms TCP 1ms TLS 23ms TTFB 178ms

What Upstash does

Upstash provides serverless data infrastructure billed per request rather than per hour: Redis for caching and sessions, a Vector database for embeddings, and QStash for messaging and scheduled jobs. It is aimed at serverless and edge applications that open a connection per invocation, which is why it is reachable over HTTP as well as the Redis protocol.

What an outage looks like

Cache reads fail or time out, pushing traffic through to the origin database and slowing everything behind it. Sessions held in Redis vanish, logging users out. Vector queries error, so search or recommendation features break while the rest of the application works. QStash messages stop being delivered, or scheduled jobs never fire at their appointed time.

What to do about it

Check status.upstash.com, which separates Redis Global from Redis Regional and lists Vector, QStash and the console individually, so identify the product and region your database sits in. Global databases replicate across regions and one region can fail alone. Anything using Redis purely as a cache should be written to fall through to the source of truth rather than fail.

Is it down for everyone, or just you?

If this page says Upstash is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Upstash outage FAQ

Is data lost if Upstash has an outage?

Redis used purely as a cache loses nothing that matters, since the values can be recomputed from the source of truth. Data held only in Redis, such as sessions or rate-limit counters, is a different matter and may not survive. The distinction is set by how the application uses Redis rather than by anything Upstash does during an incident.

What is the difference between Redis Global and Regional?

A regional database lives in one region; a global one replicates across several, with a primary region and read replicas. The status page tracks them separately because they fail differently: a global database can lose a read region and keep serving, while a regional one has nowhere to fail over to. Check which type yours is first.

Do scheduled QStash jobs run late or not at all?

QStash is its own component, so scheduling can fail while Redis stays healthy. A job that misses its scheduled time may still be delivered once the incident clears, so jobs should be written to tolerate arriving late or arriving twice. A job assuming exact timing will misbehave in ways the outage itself does not explain.

Why did a cache outage slow my whole application?

Because every request that would have been served from cache falls through to the origin database at once. A cache absorbing most reads is also hiding how much load the origin cannot take. That is the usual reason a cache incident looks far worse than losing a cache should, and it is worth load-testing for before it happens.

How we measure this

We request Upstash's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Upstash publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Upstash goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required