51 Appcues incidents · 2019年7月 — official updates, affected components, duration and resolution details.
Appcues ワークフローのメール送信が遅延します。 問題を特定し、修正に取り組んでいます.
根本的な問題は修正され、メールが再び処理されます。 遅延したメッセージのバックログで作業しています.
遅延したメッセージが処理されました。 正常に動作するすべてのシステム.
公式のインシデント更新を自動翻訳しています。
We've identified an issue logging into the EU Appcues Studio and are working on a fix. End user experiences and data collection are not impacted.
The issue has been resolved
We're addressing an issue preventing access to studio.eu.appcues.com. US Appcues Studio is not impacted. End user content delivery and analytics data collection is not affected in either region.
We've addressed the underlying issue and Studio in the EU is now available.
We're currently addressing an issue that is causing the Appcues Studio to not load. End user content rendering and analytics event processing is not impacted.
The Appcues Studio is available and fully functional.
We've identified an issue in a new Studio release preventing the Appcues Studio from loading and rolled back to a stable version. End user content delivery and analytics data collection was not impacted.
We're investigating delays returning analytics data in Studio.
The root cause has been identified and the query pattern that caused the issue has been mitigated.
A service interruption due to a failure in a downstream service provider prevented Appcues Studio and Builder from loading for approximately 10 minutes. Resolution: Services automatically recovered.
At 12:45 PM ET, some users were unable to log into Appcues Studio and Builder using username/password. Our engineers identified the root cause, deployed a fix, and restored access by 2:41 PM ET. Existing sessions and SSO/Google auth were unaffected.
Date: October 14, 2025 Status: Resolved Duration: 16 minutes (3:21–3:37 PM EDT) Due to a failed process an API database became locked, which prevented Appcues Studio and Builder from loading. Resolution: Problematic process terminated, restoring services immediately.
On October 9, 2025, between 9:25 PM and 9:35 PM ET, the Appcues SDK was unavailable for approximately 10 minutes. During this period, end users received a 403 UNAUTHORIZED response to SDK load requests, preventing event capture and content display. Timeline: 9:25 PM ET: SDK unavailability began. 9:32 PM ET: Issue detected via alerting system. 9:35 PM ET: Systems fully restored. Impact: End users were unable to load the SDK, resulting in no events captured or content displayed during the outage. Resolution: The issue was identified and resolved promptly, with full SDK functionality restored by 9:35 PM ET.
Our team has received reports of the issue and is actively investigating to identify the root cause. We are working on a resolution as quickly as possible.
Our team has identified a potential root cause related to a third-party provider. The provider is actively working on a fix.
A fix has been implemented and we are monitoring the results.
The issue, caused by a third-party provider, has been fully resolved. Preventative measures have been implemented to reduce the risk of this dependency in the future.
We are experiencing an issue with the Appcues API that is causing a slowdown in end user content delivery. We are investigating.
The incident is resolved.
We are seeing a new instance of degraded performance and are investigating.
We have identified the root cause for this issue. The issue is now cleared.
We are investigating issues causing errors in Appcues Builder, Studio, and the Public API. There is some limited impact to end user content delivery and data collection.
We've identified the issue and are working on a fix.
A fix is in place and we are monitoring the recovery
This incident has been resolved.
We are monitoring the impact of an outage at a 3rd party service provider on our systems. The incident is causing delays with processing our Analytics and Integrations. Additionally, we are seeing longer than normal delivery times for some end-user content.
We are continuing to monitor the situation with our 3rd party provider. At this time we no longer any impact to end-user content delivery. Analytics and Integrations continue to be delayed.
We are continuing to monitor the impact of an outage at a 3rd party service provider on our systems. The incident is causing delays with processing analytics in Studio and generating data exports. End-user content delivery is not affected.
We are continuing to monitor the impact of an outage at a 3rd party service provider on our systems. The incident continues to cause delays with processing analytics in Studio and generating data exports. End-user content delivery is not affected.
This incident has ended. All systems are operatinal.
We are investigating an issue causing the Appcues Studio to intermittently fail to load. This issue appears to be related to a problem in a downstream provider. End user content delivery is unaffected. You can bypass this issue by reloading the Appcues Studio.
The downstream provider has located the issue and is working on a fix. They are tracking the incident here: https://status.firebase.google.com/incidents/k8Hj8EZMSMkQvoCCQWpA
A fix has been implemented and we are monitoring performance.
This issue has been resolved
We're investigating an issue affecting end-user flow delivery.
We identified an issue and are implementing a fix.
A fix is in place and we are monitoring the recovery.
This incident is resolved.
We are investigating an issue causing degraded performance in the Appcues Studio. End user content delivery is unaffected.
We have mitigated the impact of this issue and continue to investigate a root cause. End user content deliver continues to be unaffected.
We have identified an are addressing a root cause. The incident is resolved.
Our API experienced an elevated error rate creating websocket connections leading to transient flow delivery slowdowns on November 12, November 13 and November 14. This incident was resolved as of 6:36AM US ET on November 14th.
We've identified an issue loading the Appcues Studio. A fix is being implemented. End user flow delivery is not affected.
A fix has been implemented and we are monitoring results.
This issue has been resolved.
We are investigating an issue affecting flow delivery.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
