Upstash Outage History
Upstash is up right nowPingoru has recorded 51 incidents for Upstash: 26 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 4 of 720 (1%) |
| May 2026 | 7 | 39 of 744 (5%) |
| June 2026 | 5 | 11 of 720 (2%) |
| July 2026 | 2 | 1 of 744 (0%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 3 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 586 (0%) |
Incidents, newest first
Minor December 1, 2025 QStash - Message delays for Flow Control configurations –
Started Dec 01, 2025, 07:00 AM UTC· resolved Dec 01, 2025, 07:00 AM UTC
- resolved Dec 12, 2025, 02:34 PM UTC
We identified and fixed a bug that could cause messages with Flow Control enabled to be delayed longer than their configured delay, resulting in unexpectedly long pending times. The fix is in place and the issue should not recur. If you’re still seeing unusually long-delayed messages, please contact [email protected] and we can help with remediation.
Major October 20, 2025 Upstash Console issues 3h 58m Upstash Console
Started Oct 20, 2025, 02:52 PM UTC· resolved Oct 20, 2025, 06:50 PM UTC
- investigating Oct 20, 2025, 02:52 PM UTC
We are currently experiencing errors in the Upstash Console due to issues with one of our upstream providers. This may affect access to the dashboard and related operations. Our team is actively monitoring the situation and working to mitigate the impact. We will provide updates as soon as more information becomes available.
- monitoring Oct 20, 2025, 03:05 PM UTC
Console is back to normal again. We are currently monitoring.
- monitoring Oct 20, 2025, 06:07 PM UTC
Developer API (api.upstash.com) is having availability issues alongside Upstash Console. While we are monitoring the underlying cloud provider's status updates, we are also working on a remediation.
- resolved Oct 20, 2025, 06:50 PM UTC
A fix has been deployed as a workaround so that our systems are not affected from the ongoing incident of the cloud provider
Critical October 20, 2025 Login Issues on Upstash Console 2h 23m
Started Oct 20, 2025, 07:00 AM UTC· resolved Oct 20, 2025, 09:23 AM UTC
- resolved Oct 20, 2025, 10:29 AM UTC
As a side effect of an incident on the underlying cloud provider, Upstash Console has had availability issues between 07:00UTC and 09:23UTC. Only Upstash Console is impacted, Upstash products remained operational.
Minor October 10, 2025 Connectivity issue on us-east-1 9m
Started Oct 10, 2025, 03:46 PM UTC· resolved Oct 10, 2025, 03:55 PM UTC
- resolved Oct 10, 2025, 04:47 PM UTC
Between 15:46–15:55 UTC, some client connection attempts to databases in us-east-1 timed out due to unexpected high load on a server. The node was recovered at 15:50 UTC, and the updated DNS record propagated by 15:55 UTC. Services are operating normally.
Minor September 9, 2025 Temporary Database Routing Issue –
Started Sep 09, 2025, 12:00 PM UTC· resolved Sep 09, 2025, 12:00 PM UTC
- resolved Sep 09, 2025, 03:48 PM UTC
Impact: A subset of clients connecting through the eu-central-1 region experienced increased error rates and timeouts when accessing certain databases. Clients in us-west-2 were also briefly affected. The issue was limited in scope and did not impact other regions. Root Cause: During an ongoing migration to improve database routing reliability, a configuration step was applied inconsistently across regions. Resolution: Our monitoring alerted us within minutes, and the migration was promptly rolled back for the affected regions. Service definitions were restored, and normal database connectivity resumed by 15:08 UTC. Next Steps: We are reviewing our migration process to ensure consistency across all regions and adding additional safeguards to prevent similar issues in the future.
Minor August 18, 2025 Connectivity Issues in us-east-1 13m N. Virginia, USA (us-east-1)
Started Aug 18, 2025, 12:37 PM UTC· resolved Aug 18, 2025, 12:50 PM UTC
- resolved Aug 18, 2025, 01:30 PM UTC
Between 12:37 UTC and 12:50 UTC, an overload in the connection proxying system resulted in instability for a subset of databases. The root cause was identified as a misconfiguration in the routing rules, which caused certain requests to experience timeouts during the initial phase of a gradual deployment. Upon detection, the deployment was immediately rolled back, restoring normal service. We are reviewing our deployment and configuration validation processes to prevent similar issues in the future.
- postmortem Aug 18, 2025, 01:30 PM UTC
Between 12:37 UTC and 12:50 UTC, an overload in the connection proxying system resulted in instability for a subset of databases. The root cause was identified as a misconfiguration in the routing rules, which caused certain requests to experience timeouts during the initial phase of a gradual deployment. Upon detection, the deployment was immediately rolled back, restoring normal service. We are reviewing our deployment and configuration validation processes to prevent similar issues in the future.
Major June 26, 2025 Login problems on Upstash Console 41m Upstash Console
Started Jun 26, 2025, 06:53 AM UTC· resolved Jun 26, 2025, 07:34 AM UTC
- identified Jun 26, 2025, 06:53 AM UTC
Some users may experience login issues due to a disruption in our authentication provider. We’re actively monitoring the situation.
- monitoring Jun 26, 2025, 07:12 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 26, 2025, 07:34 AM UTC
This incident has been resolved.
Minor June 12, 2025 QStash: Degraded performance 1h 39m EU-CENTRAL-1
Started Jun 12, 2025, 02:28 PM UTC· resolved Jun 12, 2025, 04:07 PM UTC
- investigating Jun 12, 2025, 02:28 PM UTC
We are currently investigating this issue.
- monitoring Jun 12, 2025, 02:40 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 12, 2025, 04:07 PM UTC
This incident has been resolved.
Critical June 11, 2025 Degraded Performance 3h 10m N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Oregon, USA (us-west-2), Frankfurt, Germany (eu-central-1) and 8 more
Started Jun 11, 2025, 06:51 AM UTC· resolved Jun 11, 2025, 10:02 AM UTC
- investigating Jun 11, 2025, 06:51 AM UTC
We are currently investigating this issue.
- investigating Jun 11, 2025, 08:24 AM UTC
We are continuing to investigate this issue.
- monitoring Jun 11, 2025, 09:20 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 11, 2025, 10:02 AM UTC
This incident has been resolved.
- postmortem Jun 11, 2025, 11:49 AM UTC
A routine system maintenance operation at the OS level led to the application of system updates across multiple EC2 instances in our clusters in several AWS regions. These updates included changes to networking components, which inadvertently triggered restarts. As a result, several EC2 nodes failed health checks and temporarily dropped out of the cluster, disrupting high availability and causing partial connectivity issues for some clients and operations. We have since reproduced the issue in a controlled environment and verified the root cause. To prevent a recurrence, we are updating our node maintenance strategy to ensure greater control over the timing and impact of system-level changes and excluding networking components from automated upgrades.
Minor June 10, 2025 Performance Degradation 4h 45m N. Virginia, USA (us-east-1)
Started Jun 10, 2025, 07:23 AM UTC· resolved Jun 10, 2025, 12:08 PM UTC
- investigating Jun 10, 2025, 07:23 AM UTC
We are currently investigating this issue.
- monitoring Jun 10, 2025, 07:45 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 10, 2025, 12:08 PM UTC
This incident has been resolved.
- postmortem Jun 11, 2025, 11:37 AM UTC
A routine system maintenance operation at the OS level led to the application of system updates across multiple EC2 instances in our clusters in several AWS regions. These updates included changes to networking components, which inadvertently triggered restarts. As a result, several EC2 nodes failed health checks and temporarily dropped out of the cluster, disrupting high availability and causing partial connectivity issues for some clients and operations. We have since reproduced the issue in a controlled environment and verified the root cause. To prevent a recurrence, we are updating our node maintenance strategy to ensure greater control over the timing and impact of system-level changes and excluding networking components from automated upgrades.
Minor May 22, 2025 Global Ireland (eu-west-1) Degraded Performance 56m Ireland (eu-west-1)
Started May 22, 2025, 04:44 PM UTC· resolved May 22, 2025, 05:41 PM UTC
- monitoring May 22, 2025, 04:44 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 22, 2025, 05:41 PM UTC
This incident has been resolved.
Minor April 2, 2025 QStash: Degraded performance in request processing and event logs 13h 57m EU-CENTRAL-1
Started Apr 02, 2025, 07:15 AM UTC· resolved Apr 02, 2025, 09:12 PM UTC
- investigating Apr 02, 2025, 07:35 AM UTC
We are currently investigating this issue.
- monitoring Apr 02, 2025, 08:20 AM UTC
A fix has been implemented and we are monitoring the results.
- investigating Apr 02, 2025, 04:21 PM UTC
We are currently investigating this issue.
- investigating Apr 02, 2025, 04:29 PM UTC
We are continuing to investigate this issue.
- investigating Apr 02, 2025, 04:33 PM UTC
We are continuing to investigate this issue.
- monitoring Apr 02, 2025, 05:33 PM UTC
Main QStash service is back to normal. Event logs are still temporarily unavailable.
- monitoring Apr 02, 2025, 08:20 PM UTC
Monitoring: Main QStash service is back to normal. Event logs service is back online but events will be lagging a few mins.
- resolved Apr 02, 2025, 09:12 PM UTC
QStash service and Event logs are fully functional without any remaning issues.
- postmortem Apr 03, 2025, 03:49 PM UTC
### Product: QStash ### Incident Summary Due to high load, the volume of QStash event logs reached to a point which caused latency in the underlying data store operations. Event log creation was slowed down and lead to performance degradation in QStash request processing. In order to resolve the performance degradation in QStash requests, event logging module was turned off temporarily. After deploying a hot fix and configuration changes, we eventually turned on event logging and system went back to stable state again. ### Root Cause At 07:15 UTC we received alerts on the performance degradation and started the investigation. We discovered long running queries for synching event logs from main QStash servers to QStash event server. In order to resolve performance degradation, we turned off event logging functionality as an immediate action. This action turned the performance back to normal levels for QStash requests but left event log processing disabled. We deployed a hotfix during the day to remove some redundant calls and alleviate the impact. Around 16:20 UTC, we observed another performance degradation on QStash requests due to a load increase, and disabled event log processing again. In the following hours, we deployed a configuration change to relax the job interval durations for event log tasks and turned on event logging again. This configuration change helped to resolve the performance issues without any further issues. ### Impact During the problematic timeframes, when the slow event log processing was observed, QStash requests experienced high latency and caused timeouts for customers. No events were lost. Duplicate event deliveries were observed due to a number of restarts during the incident. ### Resolution Improvements are applied to the event logging module to prevent the same issue from happening again. Also, we have planned to upgrade underlying disks to stronger models.
Minor March 12, 2025 Performance degradation on QStash 33m EU-CENTRAL-1
Started Mar 12, 2025, 09:43 AM UTC· resolved Mar 12, 2025, 10:16 AM UTC
- investigating Mar 12, 2025, 09:43 AM UTC
We are currently investigating this issue.
- monitoring Mar 12, 2025, 10:08 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 12, 2025, 10:16 AM UTC
This incident has been resolved.
- postmortem Mar 12, 2025, 12:26 PM UTC
On 09:43 UTC, QStash experienced degraded service when a high number of requests to a specific domain were throttled, resulting in timeouts during an unexpected phase of the TCP connection establishment. These requests and resulting retries triggered excessive consumption of network resources and negatively impacted all users. We have added more resources to QStash as a quick remediation and as for the resolution, we have improved the timeout mechanism to detect and fail-faster in such cases.
Minor February 25, 2025 Regional AWS eu-west-1 Cluster Performance Degradation Issue 7h 19m AWS EU-WEST-1
Started Feb 25, 2025, 02:03 PM UTC· resolved Feb 25, 2025, 09:23 PM UTC
- identified Feb 25, 2025, 08:03 PM UTC
Regional AWS eu-west-1 cluster is experiencing performance degradation, and we are adding more resources to the cluster.
- monitoring Feb 25, 2025, 08:54 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 25, 2025, 09:23 PM UTC
This incident has been resolved.
- postmortem Feb 26, 2025, 12:29 PM UTC
### Incident Summary During a maintenance update to the regional Upstash Redis databases in AWS eu-west-1, several databases hosted in that region has unnecessarily triggered a full synchronisation between their primary and backup replicas. ### Root Cause A full synchronisation is the invalidation of the whole data in the target replica and starting a fresh re-population from the source replica. Under normal circumstances, full synchronisation is required only in cases where the data integrity is lost in one of the replicas, which was not the case here. ### Impact This incident impacted the performance of regional databases on AWS eu-west-1 only. Full synchronisation has caused a very high CPU load and caused a performance degradation on some of the databases that has a replica in this region. Moreover, our system throttles the databases that are going through this operation to allocate more CPU to the synchronisation to finish it sooner. No data or consistency has been lost. ### Resolution As a quick remediation, we have unthrottled affected databases on 15:06UTC and enabled more throughput, however high latency has still been observed until the full synchronisation is completed on 21:23UTC. A fix has been prepared to avoid this unnecessary full synchronisation on regional databases, and will be deployed shortly. This issue is not present on Upstash Global databases, which is our new generation infrastructure and is now our default offering. We will reach out to our regional users on how to migrate to Upstash Global going forward.
Notice February 20, 2025 We experienced a very short period of API downtime for the incoming requests to QStash due to urgent maintenance to ensure the stability and performance of our services. Our team acted quickly to address the issue, and everything is now fully operational. –
Started Feb 20, 2025, 08:00 AM UTC· resolved Feb 20, 2025, 08:00 AM UTC
- resolved Feb 20, 2025, 08:58 AM UTC
We experienced a very short period of API downtime for the incoming requests to QStash due to urgent maintenance to ensure the stability and performance of our services. Our team acted quickly to address the issue, and everything is now fully operational.
Notice February 6, 2025 QStash Workflow Run Failure 3h 10m
Started Feb 06, 2025, 07:00 AM UTC· resolved Feb 06, 2025, 10:10 AM UTC
- resolved Feb 06, 2025, 11:48 AM UTC
Latest QStash release caused some Workflow runs to fail due to a bug in Workflow URL detection mechanism. Affected workflows did not start at all and moved directly to DLQ. These workflow runs, which show "detected non-workflow destination" message in the response body, can be retried from DLQ. This was a partial failure, lasted from 10:10 to 11:00 UTC, not all users' workflows were affected.
Major January 29, 2025 Disk failure in some Regional Databases 21m AWS US-EAST-1
Started Jan 29, 2025, 04:52 PM UTC· resolved Jan 29, 2025, 05:13 PM UTC
- resolved Jan 29, 2025, 06:03 PM UTC
We observed a disk failure on some instances on 16:52 UTC and restarted affected components to bring them back online. Issue is resolved on 17:13 UTC. During the time of the issue databases reachability are affected, no data is lost.