Sep 29, 15:12 UTC Resolved - Between 15:12 and 15:16 UTC, we observed a brief increase in load on the connection proxy layer in us-east-1, which may have affected some existing and new connections.The team responded quickly and resolved the issue. All systems are now fully operational.
Sep 9, 12:00 UTC Resolved - Upstash Vector experienced a brief DNS resolution issue in the US East (us-east-1) region lasting approximately 20 minutes. During this period, new DNS resolution attempts may have failed.Existing connections and clients with cached DNS records were not affected.The issue has been resolved, and DNS resolution is operating normally.
Sep 3, 08:00 UTC Resolved - We experienced a brief issue affecting access to the Upstash Console. Our team quickly identified the cause and resolved the issue within minutes.The console is now operating normally.
Aug 28, 22:20 UTC Resolved - Between 22:20 and 22:33 UTC, QStash clients in us-east-1 experienced disruptions related to message persistence. The team applied a fix, and service has been restored.
Jul 22, 10:05 UTC Resolved - This incident has been resolved. Jul 22, 09:01 UTC Monitoring - The affected Fly.io-hosted machines recovered at 08:48 UTC, and service availability has been restored. We are monitoring the systems to confirm continued stability. Jul 22, 08:50 UTC Identified - We are investigating connectivity issues affecting a subset of Redis databases hosted on Fly.io. The issue is…
Jul 16, 06:30 UTC Resolved - Partial outage due to http parsing errors. Problem was resolved couple minutes later. If problem continues, refreshing the DNS cache is recommended.
Jun 25, 16:36 UTC Resolved - This incident has been resolved, we will publish RCA soon. Jun 25, 15:31 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 25, 15:23 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-1Our team is investigating the issue and w…
Jun 23, 17:14 UTC Resolved - This incident has been resolved. Jun 23, 16:32 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 23, 16:22 UTC Investigating - We are currently investigating this issue.
Jun 23, 06:05 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 apologiz…
Jun 19, 09:11 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…
Jun 4, 14:09 UTC Resolved - This incident has been resolved. Jun 4, 12:56 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 4, 10:10 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…
May 30, 07:51 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 increas…
May 23, 00:00 UTC Resolved - This incident has been resolved. May 22, 23:48 UTC Monitoring - Upstream issue resolved — new database creation is working again. We're monitoring to confirm full recovery. May 22, 23:27 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…
May 14, 17:31 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 rel…
May 12, 13:48 UTC Resolved - This incident has been resolved. May 12, 12:05 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 12, 10:50 UTC Identified - The issue has been identified and the fix is being implemented. May 12, 09:49 UTC Investigating - Some regions are experiencing connectivity issues due to an ongoing network problem. We are currently investigating
May 11, 18:22 UTC Resolved - The incident has been resolved. We are working with Fly team on RCA. May 11, 17:19 UTC Update - We are working with Fly team to investigate the root cause. May 11, 15:07 UTC Update - We are continuing to investigate the issue. May 11, 15:05 UTC Investigating - Some databases may experience increased latency or timeouts in Fly.io’s FRA region.
May 8, 10:08 UTC Resolved - This incident has been resolved, we will publish RCA soon. May 8, 10:06 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 8, 09:46 UTC Update - We are continuing to investigate this issue. May 8, 09:46 UTC Investigating - We are currently investigating the issue.
May 6, 08:05 UTC Resolved - This incident has been resolved. May 5, 21:31 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 5, 15:44 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 5, 14:29 UTC Update - We are continuing to wo…
Apr 2, 19:53 UTC Resolved - Replication complete, incident resolved. Apr 2, 18:45 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.
Mar 27, 15:30 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.
Mar 6, 14:49 UTC Resolved - This incident has been resolved. Mar 6, 14:08 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 6, 13:50 UTC Investigating - We are currently investigating this issue.
Jan 23, 15:30 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-l…
Dec 10, 12:08 UTC Resolved - Issue has been identified and replicas were successfully reconnected. Dec 10, 11:50 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.
Dec 5, 09:18 UTC Resolved - This incident has been resolved. Dec 5, 09:03 UTC Investigating - Upstream provider confirmed an incident. We are investigating the impact and potential resolutions.
Dec 1, 07:00 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.
Oct 20, 18:50 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 20, 18:07 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 20, 15:05 UTC Mo…
Oct 20, 07:00 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.
Oct 10, 15:46 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.
Sep 9, 12:00 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 app…
Aug 18, 12:37 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, resto…