Upstash Status: How to Check If Upstash Is Down (2026)
Updated June 2026 · 5 min read · By API Status Check
Quick Answer: Check Upstash Status Now
Upstash is a serverless data platform for Redis, Kafka, and QStash (a serverless message queue). Unlike traditional Redis providers, Upstash uses an HTTP-based API model — meaning every Redis command is an HTTP request rather than a persistent TCP connection. This makes Upstash ideal for Vercel serverless functions, Cloudflare Workers, and Next.js API routes that can't maintain persistent connections. When Upstash goes down, all apps depending on Redis caching, rate limiting, session storage, or Kafka event streaming via Upstash are affected. This guide explains how to check Upstash's status and distinguish a genuine platform outage from a quota or configuration issue.
Understanding Upstash's Status Page (status.upstash.com)
Upstash operates status.upstash.com — its official status page. Because Upstash runs multiple distinct products (Redis, Kafka, QStash, Vector), incidents are tracked per product. An Upstash Redis incident doesn't necessarily mean QStash or Kafka are affected.
Upstash Redis
Serverless Redis via HTTP REST API and Redis protocol. Redis incidents affect caching, session storage, rate limiting, leaderboards, and any feature using Redis commands. Upstash Redis supports both standard Redis protocol (port 6379) and HTTP REST API — an outage affects both.
Upstash Kafka
Serverless Apache Kafka for event streaming and message queues. Kafka incidents affect producer/consumer connections and topic message delivery. Upstash Kafka retains messages — an outage delays delivery but typically doesn't lose messages.
QStash
Upstash's serverless message queue and scheduler for background jobs, webhook delivery, and scheduled tasks (cron). QStash incidents affect job scheduling and message delivery. Messages are durable — delivery resumes automatically when the service recovers.
Upstash Vector
Upstash's serverless vector database for AI/ML similarity search and embeddings storage. Vector incidents affect semantic search features and AI embedding queries. Tracked separately from Redis and Kafka.
Upstash Console
console.upstash.com — the web dashboard for managing databases, viewing metrics, and managing credentials. Console incidents prevent browser-based management but don't affect database connectivity from your application.
Upstash API
The management API for creating and managing Upstash databases programmatically. API incidents prevent database provisioning via Terraform, Vercel integrations, and other IaC tools — running databases are unaffected.
What Upstash Status Colors Mean
⚠️ Upstash Platform Issue vs. Quota/Config Issue — Know the Difference
A significant number of "Upstash is down" reports are actually quota limit or configuration issues, not platform outages. Before checking the status page:
- Free tier daily command limit: Upstash free tier has 10,000 commands/day per database. Once hit, all commands fail until midnight UTC reset.
- Database size limit: Upstash free tier limits database size. If your Redis database hits the limit, write commands fail.
- Wrong region endpoint: Upstash Redis databases are region-specific. Verify you're using the correct endpoint URL from the console.
- Incorrect password: Check the UPSTASH_REDIS_REST_TOKEN (for HTTP API) vs. Redis password (for redis:// protocol) — they're different credentials.
Monitor your Upstash-powered app with independent uptime monitoring
Upstash's status page shows platform health — not your app's Redis connection health. Better Stack monitors your actual app endpoints and alerts you when Redis caching or rate limiting failures cause downtime. Free plan available.
Try Better Stack Free →5 Ways to Check If Upstash Is Down
status.upstash.com (Official)
Upstash's official status page, showing real-time status for Upstash Redis, Kafka, QStash, Vector, and the console. Incidents are tracked per product. Subscribe to email notifications to receive updates automatically.
Check status.upstash.com →Upstash Console Data Browser
Log into console.upstash.com and use the Data Browser for your Redis database to run a test command (e.g., PING). If the console can execute commands, your Redis database is accessible. If it can't connect, check the platform status.
Open Upstash Console →redis-cli or curl (REST API)
For Redis: run `redis-cli -u <redis-url> PING` to test TCP connectivity. For the HTTP REST API: curl -X POST `https://<endpoint>/ping` with the Authorization header. If PING returns PONG, Redis is up. For QStash, curl the `/v2/topics` endpoint to verify API connectivity.
Upstash troubleshooting docs →@upstash on X
Upstash's official X account posts incident updates, maintenance announcements, and platform news from @upstash. The team is active and typically acknowledges incidents quickly on X.
Follow @upstash →X / Twitter (Search)
Search 'upstash down' or 'upstash redis outage' on X. The Next.js, Vercel, and serverless developer communities that use Upstash heavily report issues quickly.
Search X for 'upstash down' →Common Upstash Issues and What They Mean
"ERR max daily request limit exceeded"You've hit Upstash's free tier daily command limit (10,000 commands/day per database). Commands resume automatically at midnight UTC. Upgrade to a paid plan for higher or unlimited daily commands, or implement request deduplication and caching in your app to reduce Redis command volume."WRONGPASS invalid username-password pair"The Redis password in your connection string is incorrect. Upstash Redis has two different credentials: the Redis password (for redis:// protocol connections) and the REST token (for HTTP API connections). Check the Upstash console for the correct credentials — they're different strings and often confused."OOM command not allowed when used memory > maxmemory"Your Upstash Redis database has exceeded its maximum memory limit. On free tier this is 256MB. Delete unused keys, enable key eviction policies, or upgrade to a higher-tier plan. Set an eviction policy (e.g., allkeys-lru) in the console to automatically evict old keys when memory is full."NOSCRIPT No matching script"A Lua script you're trying to run with EVALSHA hasn't been loaded into this Redis instance. Upstash Redis is serverless and may route to different instances — scripts loaded with SCRIPT LOAD aren't guaranteed to persist. Use EVAL with the full script instead of EVALSHA for serverless environments."QStash: Publish failed / 429 Too Many Requests"You've exceeded QStash rate limits. QStash enforces per-topic publish rates. Implement exponential backoff and retry logic in your publisher. Consider batching messages or upgrading to a plan with higher publish rate limits."Kafka: LEADER_NOT_AVAILABLE"A Kafka topic partition leader is temporarily unavailable. This is common during Upstash maintenance or when a new topic is created (leader election takes a few seconds). Retry the connection after a short delay. If it persists, check status.upstash.com for Kafka incidents.Upstash Outage History: What the Data Shows
Upstash runs on AWS infrastructure with multi-region replication for Redis databases (when enabled). Most incidents are service-specific — an Upstash Redis outage doesn't necessarily affect QStash or Kafka. The team is active on Discord and X and typically posts incident updates quickly. QStash is designed for durability: messages are stored persistently and will deliver after service recovery, making it more resilient to outages than real-time services like Redis. For critical Redis dependencies, enable global replication to multiple regions for automatic failover.
What to Do When Upstash Is Down
If Upstash Redis Is Down
- Check status.upstash.com for Redis incidents
- Verify daily command quota in the console
- Test with redis-cli PING or HTTP REST curl
- Add retry logic with exponential backoff
- Serve cached data from CDN/in-memory cache
If QStash Is Down
- Check status.upstash.com for QStash incidents
- Messages are durable — they will re-deliver when recovered
- Check QStash console for delivery failure logs
- Verify webhook endpoint is accessible to Upstash
- Use DLQ (dead letter queue) to catch failed deliveries
Frequently Asked Questions
Where is the official Upstash status page?
Upstash's official status page is at status.upstash.com. It shows real-time status for Upstash Redis, Upstash Kafka, QStash, Upstash Vector, and the console. Incidents are tracked per product — an Upstash Redis incident doesn't mean Kafka or QStash are affected. Subscribe to email notifications to receive updates when incidents are posted and resolved.
My Upstash Redis is returning errors but the status page shows operational — what should I check?
When the status page shows operational but your Redis is failing, the most common causes are: (1) daily command limit exceeded — check your usage in the Upstash console, resets at midnight UTC; (2) incorrect credentials — verify you're using the right password vs REST token; (3) database memory full — check if OOM errors are occurring. Run `redis-cli -u <url> PING` or curl the REST API to test connectivity directly.
What's the difference between Upstash Redis REST API and the Redis protocol?
Upstash Redis supports two connection methods: the native Redis protocol (redis:// URL, port 6379, uses ioredis/redis npm packages) and the HTTP REST API (UPSTASH_REDIS_REST_URL/TOKEN, uses @upstash/redis package). For serverless environments (Vercel Edge, Cloudflare Workers), always use the HTTP REST API — the native Redis protocol requires persistent TCP connections that aren't supported in edge runtimes.
How long do Upstash outages typically last?
Upstash incidents typically resolve within 15–60 minutes. Redis incidents can be shorter because the serverless architecture routes around failures more quickly. QStash incidents may take longer to fully clear because in-flight messages need to be retried after recovery. Upstash's team posts updates on status.upstash.com and @upstash on X throughout incidents.
How do I monitor my Upstash-powered app uptime independently?
Add a health check endpoint to your app that does a lightweight Redis operation (e.g., PING or GET on a test key) and returns HTTP 200 if successful. Monitor that endpoint with Better Stack or API Status Check Alert Pro. This catches Upstash issues not yet on the status page, plus catches your own connection configuration problems (wrong credentials, quota exceeded) that wouldn't show as a platform incident.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Upstash goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Upstash + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial