Databases & data infrastructure
Is Upstash down?
Live Upstash status, measured independently. We probe 5 Upstash endpoints from monitoring regions on every continent and record every outage we detect.
Upstash is up
Our probes are reaching Upstash normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website99.99% uptime, 30 days5 regions, 86 to 202 msCheckingp50124 msMedian responsep95264 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- Management API99.95% uptime, 30 days6 regions, 292 to 1230 msCheckingp50779 msMedian responsep95965 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- QStash API99.99% uptime, 30 days6 regions, 38 to 1278 msCheckingp50661 msMedian responsep95806 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Console99.99% uptime, 30 days6 regions, 52 to 209 msCheckingp50120 msMedian responsep95270 msSlowest 5% of checks200 ms100024 h ago12 h agonow
- Documentation99.98% uptime, 30 days5 regions, 266 to 502 msCheckingp50387 msMedian responsep95581 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Upstash goes down
Follow these 5 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Upstash goes down. They don't count against your monitor quota. Free plan, no card required.
About Upstash outages
Upstash offers Redis and messaging over HTTP, which makes it the default cache and queue for edge functions and serverless apps. Rate limiting, sessions, and background job scheduling via QStash all go through it, so an Upstash incident degrades many apps in subtle ways rather than taking them fully down.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website upstash.com is unreachable. | httpupstash.com | HTTP 200 | 1 min |
Management API The management API is not answering. | httpapi.upstash.com/v2/redis/databases | HTTP 401 | 2 min |
QStash API The QStash API is not answering its normal authentication challenge. Scheduled and queued messages are affected. | httpqstash.upstash.io/v2/schedules | HTTP 401 | 2 min |
Console The Upstash console is unreachable. | httpconsole.upstash.com | HTTP 200 | 1 min |
Documentation Upstash's documentation is unreachable. | httpupstash.com/docs | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Upstash's official status page.
Embed a live Upstash badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/upstash?utm_source=badge)HTML
<a href="https://www.upti.my/status/upstash?utm_source=badge"><img src="https://www.upti.my/status/upstash/badge.svg" alt="Upstash status"></a>Recent Upstash outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Upstash is up. Is your Upstash integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Upstash and fail quietly. Here is what teams that rely on Upstash monitor on their side.
Your Redis database endpoint
Probe your own database's REST endpoint with a PING and your token. Regional Redis incidents show up there, not on the marketing site.
HTTP monitoring with headersQStash schedules
A schedule that stops firing is silent. A heartbeat on the receiving endpoint tells you when deliveries stop.
Heartbeat monitoringUpstash status: frequently asked questions
Yes. Many rate-limiting libraries fail open when Redis is unreachable, so an Upstash incident can look like rate limits simply not applying. Probe your database endpoint and alert on failures.
Look at the per-region results above. If our probes fail from every region, Upstash has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Upstash may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Upstash" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Upstash: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other databases & data infrastructure
Uptimy is not affiliated with Upstash. Upstash and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.