Upstash Outage History

Upstash Redis experienced intermittent connection issues in us-east-1, us-west-1, ap-southeast-2, and ap-south-1 regions due to unexpected load on their proxies, causing connection timeouts and elevated error rates for some clients. The team quickly identified the root cause and applied workarounds to relieve pressure on the affected proxies. The incident lasted 1.8 hours before all systems returned to normal operation.

Upstash Redis service experienced connectivity issues in some regions due to network problems, lasting approximately 4 hours. The incident affected users' ability to connect to Redis instances in the impacted regions. The issue was identified and fixed, with the service fully restored after monitoring confirmed the resolution.

Upstash Redis databases in Fly.io's FRA region experienced increased latency and timeouts for 3.3 hours. The service disruption affected database performance and connectivity for users in that region. The incident was resolved through collaboration with the Fly.io team, with a root cause analysis to follow.

Upstash's QStash service in the US region experienced a major service disruption lasting 24 minutes. The incident affected QStash functionality for users in that region. The service has been resolved and a root cause analysis will be published.

Upstash's QStash service in the US region experienced schedule degradation for 17.7 hours, causing some scheduled jobs to execute twice and preventing schedules created between April 24-May 2, 2026 from running. The team implemented a fix and restored main schedule functionality, with all affected schedules resuming normal operation after monitoring confirmed proper delivery.

Upstash's QStash service in the US region experienced scheduling issues that affected some users for 3.1 hours. The incident was identified, a fix was implemented, and the service was restored to normal operation. The issue has been resolved and is no longer impacting users.

Upstash Redis servers in the iad region experienced unexpected disk load, causing elevated latencies and temporarily forcing databases into read-only state. The service team resolved the issue by migrating replicas to new instances. The incident lasted 1.2 hours and was fully resolved once replication completed.

Upstash experienced a major outage in the ap-northeast-1 region that lasted approximately 1 hour. The incident affected services in that geographic region, preventing normal operations. The issue was resolved after implementing a fix and monitoring the results.