Is Upstash Down?

No — Upstash is up

Upstash's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 142 ms

Right now

The verdict is the worse of these two. How we decide

Upstash's status page

status.upstash.com · read 4 minutes ago · checked every 3 minutes

Operational

Upstash's components, as its status page reports them
Component	Status
Upstash Console	Operational
Context7	Operational
Context7 Console	Operational
Box	Operational

28 locations All operational

Open their status page

FlareWarden checks

console.upstash.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 142 ms
Checked: 4 hours ago

By region

Amsterdam reachable, 146 ms
Dallas reachable, 198 ms
Frankfurt reachable, 57 ms
Newark reachable, 180 ms
Paris reachable, 137 ms
Stockholm reachable, 167 ms
Sydney reachable, 65 ms
Toronto reachable, 189 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	63 ms	5 ms	18 ms	146 ms
Dallas	107 ms	0 ms	53 ms	198 ms
Frankfurt	24 ms	2 ms	9 ms	57 ms
Newark	133 ms	1 ms	19 ms	180 ms
Paris	89 ms	10 ms	16 ms	137 ms
Stockholm	124 ms	1 ms	10 ms	166 ms
Sydney	43 ms	2 ms	6 ms	64 ms
Toronto	98 ms	16 ms	37 ms	189 ms

We check that console.upstash.com loads, not every feature behind it. Test it yourself

History

Incidents Upstash reported

Since Oct 22, 1 day · from status.upstash.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Upstash website availability

Measured by FlareWarden · console.upstash.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 171ms

Last 30 days

70-day clean streak

Sep 23 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of console.upstash.com from multiple regions every 6 hours. Upstash's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 70 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Upstash itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Upstash goes down

We check Upstash every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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