Jun <var data-var='date'>25</var>, <var data-var='time'>16:36</var> UTC Resolved - This incident has been resolved, we will publish RCA soon. Jun <var data-var='date'>25</var>, <var data-var='time'>15:31</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>25</var>, <var data-var='time'>15:23</var> UTC Investigating - We are currently experiencing a partial service disruption affecting Upstash Redis in the following regions: * eu-central-1 * us-east-1 * us-west-1 Our team is investigating the issue and working to restore full service as soon as possible. We will share updates as more information becomes available.

Upstash Redis Partial Service Disruption

Jun <var data-var='date'>23</var>, <var data-var='time'>17:14</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>23</var>, <var data-var='time'>16:32</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>23</var>, <var data-var='time'>16:22</var> UTC Investigating - We are currently investigating this issue.

QStash EU Region — Degraded Performance

Jun <var data-var='date'>23</var>, <var data-var='time'>06:05</var> UTC Resolved - Between 01:18 and 04:03 UTC, customers were unable to access running boxes or perform create, read, update, or delete operations. Running containers were not affected and continued operating throughout. The issue has been fully resolved and all box operations are functioning normally. We are taking all necessary measures to prevent this from happening again. We apologize for the disruption.

Box Access and Management Operations Unavailable

Jun <var data-var='date'>19</var>, <var data-var='time'>09:11</var> UTC Resolved - We identified an outbound networking issue affecting a subset of QStash server instances in the EU region between 2026-06-19 09:11 UTC and 2026-06-19 09:45 UTC. During this period, some requests dispatched by QStash may have failed. The issue has been resolved, and QStash is currently operating normally. We will publish a postmortem with additional details as soon as it is available. Update: We identified that one QStash server had been assigned an outbound IP address outside of the configured QStash IP range. This remained the case until 2026-06-19 11:24 UTC. Endpoints that restrict access based on QStash outbound IP allowlists may have rejected requests from this server during this period.

QStash Service Disruption in the EU Region

Jun <var data-var='date'> 4</var>, <var data-var='time'>14:09</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 4</var>, <var data-var='time'>12:56</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'> 4</var>, <var data-var='time'>10:10</var> UTC Investigating - We are currently experiencing a service disruption affecting Upstash Vector in the IAD region. Initial investigation indicates that the issue is related to a Fly.io networking/routing problem impacting connectivity in the region. The Fly.io team is actively investigating the underlying cause. We will continue to monitor the situation and provide updates as more information becomes available.

Fly.io - Upstash Vector service disruption on IAD region

May <var data-var='date'>30</var>, <var data-var='time'>07:51</var> UTC Resolved - The issue affecting some Upstash Vector indexes in the US-EAST-1 region has been resolved. Our team investigated the incident and identified the conditions that were contributing to elevated memory pressure on the affected servers. We mitigated those conditions by reducing memory utilization on the impacted nodes, rebalancing affected workloads where needed, and increasing available headroom capacity across the region. All affected indexes should now be operating normally, and based on the mitigations applied, we do not expect this issue to recur. We apologize for any inconvenience this may have caused. May <var data-var='date'>29</var>, <var data-var='time'>23:44</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>29</var>, <var data-var='time'>20:18</var> UTC Investigating - Some Upstash Vector indexes in the US-EAST-1 region may be experiencing intermittent slowness. Initial investigation indicates this may be related to memory pressure on the affected servers. Our team is actively investigating the root cause and working to restore normal performance. We will provide updates as soon as more information is available.

Intermittent slowness in Vector US-EAST-1 region

May <var data-var='date'>23</var>, <var data-var='time'>00:00</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>22</var>, <var data-var='time'>23:48</var> UTC Monitoring - Upstream issue resolved — new database creation is working again. We're monitoring to confirm full recovery. May <var data-var='date'>22</var>, <var data-var='time'>23:27</var> UTC Investigating - New database provisioning is currently failing due to an ongoing upstream provider issue affecting DNS. Existing databases and connections are unaffected — only the creation flow is impacted. We're monitoring the situation and will update once the upstream issue is resolved.

New Database Creation Failing Due to Upstream Provider Issue

May <var data-var='date'>14</var>, <var data-var='time'>17:31</var> UTC Resolved - Earlier today, unexpected load on our proxies caused intermittent connection issues for Upstash Redis in the following regions: us-east-1, us-west-1, ap-southeast-2, and ap-south-1. During this period, some clients may have seen connection timeouts or elevated error rates when reaching their databases. Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally. We appreciate your patience and apologize for any disruption this may have caused. May <var data-var='date'>14</var>, <var data-var='time'>16:00</var> UTC Monitoring - A fix has been implemented and we are monitoring. May <var data-var='date'>14</var>, <var data-var='time'>15:49</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>14</var>, <var data-var='time'>15:47</var> UTC Monitoring - We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.

Upstash Redis – intermittent connection issues in some regions

May <var data-var='date'>12</var>, <var data-var='time'>13:48</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>12</var>, <var data-var='time'>12:05</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>12</var>, <var data-var='time'>10:50</var> UTC Identified - The issue has been identified and the fix is being implemented. May <var data-var='date'>12</var>, <var data-var='time'>09:49</var> UTC Investigating - Some regions are experiencing connectivity issues due to an ongoing network problem. We are currently investigating

Fly.io Upstash Redis Service Distruption

May <var data-var='date'>11</var>, <var data-var='time'>18:22</var> UTC Resolved - The incident has been resolved. We are working with Fly team on RCA. May <var data-var='date'>11</var>, <var data-var='time'>17:19</var> UTC Update - We are working with Fly team to investigate the root cause. May <var data-var='date'>11</var>, <var data-var='time'>15:07</var> UTC Update - We are continuing to investigate the issue. May <var data-var='date'>11</var>, <var data-var='time'>15:05</var> UTC Investigating - Some databases may experience increased latency or timeouts in Fly.io’s FRA region.

Fly.io Upstash Redis service distruption (FRA region)

May <var data-var='date'> 8</var>, <var data-var='time'>10:08</var> UTC Resolved - This incident has been resolved, we will publish RCA soon. May <var data-var='date'> 8</var>, <var data-var='time'>10:06</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 8</var>, <var data-var='time'>09:46</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'> 8</var>, <var data-var='time'>09:46</var> UTC Investigating - We are currently investigating the issue.

QStash US Region Service Disruption

May <var data-var='date'> 6</var>, <var data-var='time'>08:05</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>21:31</var> UTC Update - 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. May <var data-var='date'> 5</var>, <var data-var='time'>15:44</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 5</var>, <var data-var='time'>14:29</var> UTC Update - We are continuing to work on a fix for this issue. May <var data-var='date'> 5</var>, <var data-var='time'>14:24</var> UTC Identified - 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.

QStash US Region: Schedule Degradation

Apr <var data-var='date'> 2</var>, <var data-var='time'>19:53</var> UTC Resolved - Replication complete, incident resolved. Apr <var data-var='date'> 2</var>, <var data-var='time'>18:45</var> UTC Identified - Servers in the iad region experienced unexpected disk load, resulting in elevated latencies and a temporary read-only state. We are migrating replicas to new instances to mitigate the issue and expect to have it fully resolved shortly.

Fly.io Upstash Redis – iad Region Elevated Latency and Temporary Read-Only State

Mar <var data-var='date'>27</var>, <var data-var='time'>15:30</var> UTC Resolved - Due to a race condition in a process that attaches static IPs to nodes, some of the IPs in the dns were detached from the nodes, causing timeouts.

Upstash Redis: GCP Global Connectivity Problems

Mar <var data-var='date'> 6</var>, <var data-var='time'>14:49</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 6</var>, <var data-var='time'>14:08</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'> 6</var>, <var data-var='time'>13:50</var> UTC Investigating - We are currently investigating this issue.

Region ap-northeast-1 outage on Upstash Global

Jan <var data-var='date'>23</var>, <var data-var='time'>15:30</var> UTC Resolved - We identified the cause of elevated latency impacting some databases in us-east-1 region between 15:30–15:35 UTC as a sudden surge of connection attempts that hit OS-level connection limits on our proxy layer. This resulted in slower new connection establishment and increased latency for some requests. Databases were not impacted. We are implementing additional proxy-level metrics and safeguards to detect and manage similar edge cases earlier.

Upstash Redis: Intermittent latency on us-east-1

Dec <var data-var='date'>10</var>, <var data-var='time'>12:08</var> UTC Resolved - Issue has been identified and replicas were successfully reconnected. Dec <var data-var='date'>10</var>, <var data-var='time'>11:50</var> UTC Investigating - We identified an issue in Regional Databases in US-East-1 where database replicase have connectivity issues with each other. Other regions are not impacted. Global databases are not impacted. We are working on the issue.

Connectivity issue impacting Regional Databases in US-East-1

Dec <var data-var='date'> 5</var>, <var data-var='time'>09:18</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'> 5</var>, <var data-var='time'>09:03</var> UTC Investigating - Upstream provider confirmed an incident. We are investigating the impact and potential resolutions.

Upstash Console and Context7 Console is Currently Experiencing issues

Dec <var data-var='date'> 1</var>, <var data-var='time'>07:00</var> UTC Resolved - 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 support@upstash.com and we can help with remediation.

QStash - Message delays for Flow Control configurations

Oct <var data-var='date'>20</var>, <var data-var='time'>18:50</var> UTC Resolved - A fix has been deployed as a workaround so that our systems are not affected from the ongoing incident of the cloud provider Oct <var data-var='date'>20</var>, <var data-var='time'>18:07</var> UTC Update - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>15:05</var> UTC Monitoring - Console is back to normal again. We are currently monitoring. Oct <var data-var='date'>20</var>, <var data-var='time'>14:52</var> UTC Investigating - 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.

Upstash Console issues

Oct <var data-var='date'>20</var>, <var data-var='time'>07:00</var> UTC Resolved - 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.

Login Issues on Upstash Console

Oct <var data-var='date'>10</var>, <var data-var='time'>15:46</var> UTC Resolved - 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.

Connectivity issue on us-east-1

Sep <var data-var='date'> 9</var>, <var data-var='time'>12:00</var> UTC Resolved - 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.

Temporary Database Routing Issue

Aug <var data-var='date'>18</var>, <var data-var='time'>12:37</var> UTC Resolved - 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.

Connectivity Issues in us-east-1

Jun <var data-var='date'>26</var>, <var data-var='time'>07:34</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>26</var>, <var data-var='time'>07:12</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>26</var>, <var data-var='time'>06:53</var> UTC Identified - Some users may experience login issues due to a disruption in our authentication provider. We’re actively monitoring the situation.

Is Upstash down?

Upstash status is UP

Lastest published events

Upstash Redis Partial Service Disruption

QStash EU Region — Degraded Performance

Box Access and Management Operations Unavailable

Upstash Services, Components and Regions

Recent Upstash events

Upstash Redis Partial Service Disruption

QStash EU Region — Degraded Performance

Box Access and Management Operations Unavailable

QStash Service Disruption in the EU Region

Fly.io - Upstash Vector service disruption on IAD region

Intermittent slowness in Vector US-EAST-1 region

Get your FREE account now,
5 monitors included!

Is Upstash down?

Upstash status is UP

Lastest published events

Upstash Redis Partial Service Disruption

QStash EU Region — Degraded Performance

Box Access and Management Operations Unavailable

Upstash Services, Components and Regions

Recent Upstash events

Upstash Redis Partial Service Disruption

QStash EU Region — Degraded Performance

Box Access and Management Operations Unavailable

QStash Service Disruption in the EU Region

Fly.io - Upstash Vector service disruption on IAD region

Intermittent slowness in Vector US-EAST-1 region

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!