Upstash incident: QStash US Region: Schedule Degradation

Affected components

• US-EAST-1

1. postmortemMay 6, 2026, 08:55 UTC

   # **Incident Postmortem: Scheduled Jobs Inconsistency in US Region** On May 1, 2026, we experienced an incident affecting a subset of schedules in the US region following a recent infrastructure update. The issue has been resolved, and all affected schedules have been restored. ## **Summary** As part of an ongoing scalability improvement, we recently updated scheduling infrastructure in the US region to a new architecture. During this transition, a legacy execution path remained in the codebase as a fallback mechanism. On May 1, a bug caused the system to revert to the legacy path. This resulted in inconsistent state between the old and new scheduling systems for some users. ## **Impact** The incident affected a limited number of users in the US region. **Most users were not affected**, and the vast majority of schedules continued operating normally throughout the incident. Users who did not update schedules during the transition window continued operating normally throughout

2. resolvedMay 6, 2026, 08:05 UTC

   This incident has been resolved.

3. monitoringMay 5, 2026, 21:31 UTC

   Main schedule functionality is back to normal. We are currently checking if previously created schedules are delivered as expected before marking the incident as resolved.

4. monitoringMay 5, 2026, 15:44 UTC

   A fix has been implemented and we are monitoring the results.

5. identifiedMay 5, 2026, 14:29 UTC

   We are continuing to work on a fix for this issue.

6. identifiedMay 5, 2026, 14:24 UTC

   We are currently experiencing issues in the US region. - Duplicate Deliveries: During this period, some scheduled jobs may be executed twice. - Schedule Disruption: Schedules created between April 24, 2026 and May 2, 2026 are currently not running. Our team is actively working on a fix. Once the migration is complete, affected schedules will resume normal operation. We will provide updates as progress continues.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Upstash's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Netlify: Agent Runner failures on new projectsCritical · May 5, 2026, 20:53 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: (Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]Minor · May 1, 2026, 17:51 UTC
• Contentful: Audit logs incomplete for days ranging between 30 of April and 4th of May.Minor · May 5, 2026, 13:13 UTC
• Datadog: Delays in APM-based Monitor NotificationsMinor · May 5, 2026, 18:14 UTC
• Mux: Elevated rebuffering and startup times for some on-demand assets and live streamsMinor · May 5, 2026, 18:52 UTC
• Amplitude: Ingestion lag in our batch pipelineMinor · May 5, 2026, 19:13 UTC
• Expo: Increased EAS jobs wait times for free tier usersMinor · May 5, 2026, 21:04 UTC
• LaunchDarkly: Elevated Streaming Errors in APAC regionMinor · May 6, 2026, 03:58 UTC

How often does Upstash have incidents?

Upstash reported 3 incidents in the last 90 days, 1 of them major or critical. See Upstash's uptime and incident history