Upstash

Upstash built its product around the insight that Redis and Kafka — two of the most widely adopted infrastructure components in modern applications — had a serverless gap. Traditional Redis deployment meant a persistently running instance that charged for idle time; Upstash's serverless Redis charges per request, scales to zero when inactive, and distributes data across a global network of points of presence so that reads can be served from the location closest to the caller. The addition of serverless Kafka and a durable QStash message queue product rounded out an offering aimed squarely at the edge computing and serverless developer audience.

The global replication architecture is central to Upstash's value proposition and also to its failure surface. A globally replicated Redis database must synchronise write operations across multiple regions, and the consistency model — strong consistency vs. eventual consistency — affects how write failures in one region impact reads in others. Upstash's REST API, which allows Redis commands to be issued over HTTP rather than the raw Redis protocol, enables access from JavaScript runtimes that cannot open persistent TCP connections. That REST layer is an additional service dependency that can degrade independently from the underlying Redis storage.

Developers encountering Upstash problems typically see Redis connection errors from the upstash/redis SDK, or HTTP errors from the REST API endpoint. Latency-sensitive applications that rely on Upstash for session storage or rate limiting surface incidents as slow response times before hard failures begin. QStash message delivery — which Upstash guarantees at-least-once with configurable retry logic — can be delayed when the delivery infrastructure is impaired, causing event-driven workflows to stall without visible error until the retry window is exhausted. The Upstash console, used for monitoring command throughput and managing database configuration, can be unavailable independently of the data path.

Outage.gg monitors Upstash service health using community-submitted reports from developers. If Redis commands are failing, QStash messages are not being delivered, or the REST API is returning errors, the live status page shows current incident data.