Appcues 장애 기록

1. 2026년 10월 6일 오전 10:16 UTCidentified

   Appcues Workflow에 대한 이메일 전송은 지연됩니다. 우리는 문제점을 확인하고 고침에 일하고 있습니다.

2. 2026년 10월 6일 오전 10:48 UTCmonitoring

   아래 문제점은 수정 및 이메일이 다시 처리됩니다. 우리는 지연된 메시지의 backlog를 통해 일하고 있습니다.

3. 2026년 10월 6일 오후 1:09 UTCresolved

   지연된 메시지가 처리되었습니다. 일반적으로 작동하는 모든 시스템.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 4월 21일 오후 1:47 UTCidentified

   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.

2. 2026년 4월 21일 오후 2:45 UTCresolved

   The issue has been resolved

1. 2026년 3월 16일 오후 10:01 UTCinvestigating

   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.

2. 2026년 3월 16일 오후 10:19 UTCresolved

   We've addressed the underlying issue and Studio in the EU is now available.

1. 2026년 2월 9일 오후 6:49 UTCidentified

   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.

2. 2026년 2월 9일 오후 6:56 UTCresolved

   The Appcues Studio is available and fully functional.

1. 2025년 12월 15일 오후 6:08 UTCresolved

   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.

1. 2025년 11월 6일 오후 6:57 UTCinvestigating

   We're investigating delays returning analytics data in Studio.

2. 2025년 11월 6일 오후 8:00 UTCresolved

   The root cause has been identified and the query pattern that caused the issue has been mitigated.

1. 2025년 11월 5일 오후 3:11 UTCresolved

   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.

1. 2025년 10월 30일 오후 7:49 UTCresolved

   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.

1. 2025년 10월 14일 오후 9:43 UTCresolved

   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.

1. 2025년 10월 10일 오전 1:59 UTCresolved

   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.

1. 2025년 5월 27일 오후 1:42 UTCinvestigating

   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.

2. 2025년 5월 27일 오후 1:59 UTCidentified

   Our team has identified a potential root cause related to a third-party provider. The provider is actively working on a fix.

3. 2025년 5월 27일 오후 2:34 UTCmonitoring

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

4. 2025년 5월 27일 오후 2:56 UTCresolved

   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.

1. 2023년 12월 6일 오후 4:52 UTCinvestigating

   We are experiencing an issue with the Appcues API that is causing a slowdown in end user content delivery. We are investigating.

2. 2023년 12월 6일 오후 5:57 UTCinvestigating

   The incident is resolved.

3. 2023년 12월 6일 오후 6:38 UTCinvestigating

   We are seeing a new instance of degraded performance and are investigating.

4. 2023년 12월 6일 오후 6:58 UTCresolved

   We have identified the root cause for this issue. The issue is now cleared.

1. 2023년 10월 11일 오후 2:19 UTCinvestigating

   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.

2. 2023년 10월 11일 오후 2:47 UTCidentified

   We've identified the issue and are working on a fix.

3. 2023년 10월 11일 오후 2:53 UTCmonitoring

   A fix is in place and we are monitoring the recovery

4. 2023년 10월 11일 오후 3:03 UTCresolved

   This incident has been resolved.

1. 2023년 9월 18일 오후 8:33 UTCmonitoring

   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.

2. 2023년 9월 18일 오후 10:16 UTCmonitoring

   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.

3. 2023년 9월 19일 오전 12:30 UTCmonitoring

   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.

4. 2023년 9월 19일 오전 3:14 UTCmonitoring

   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.

5. 2023년 9월 19일 오전 7:01 UTCresolved

   This incident has ended. All systems are operatinal.

1. 2023년 4월 5일 오후 6:35 UTCinvestigating

   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.

2. 2023년 4월 5일 오후 7:51 UTCidentified

   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

3. 2023년 4월 5일 오후 8:20 UTCmonitoring

   A fix has been implemented and we are monitoring performance.

4. 2023년 4월 5일 오후 8:42 UTCresolved

   This issue has been resolved

1. 2023년 1월 3일 오후 5:58 UTCinvestigating

   We're investigating an issue affecting end-user flow delivery.

2. 2023년 1월 3일 오후 6:49 UTCidentified

   We identified an issue and are implementing a fix.

3. 2023년 1월 3일 오후 6:59 UTCmonitoring

   A fix is in place and we are monitoring the recovery.

4. 2023년 1월 3일 오후 7:11 UTCresolved

   This incident is resolved.

1. 2022년 12월 12일 오후 2:41 UTCinvestigating

   We are investigating an issue causing degraded performance in the Appcues Studio. End user content delivery is unaffected.

2. 2022년 12월 12일 오후 3:02 UTCinvestigating

   We have mitigated the impact of this issue and continue to investigate a root cause. End user content deliver continues to be unaffected.

3. 2022년 12월 12일 오후 3:20 UTCresolved

   We have identified an are addressing a root cause. The incident is resolved.

1. 2022년 11월 14일 오후 3:47 UTCresolved

   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.

1. 2022년 4월 27일 오후 6:49 UTCidentified

   We've identified an issue loading the Appcues Studio. A fix is being implemented. End user flow delivery is not affected.

2. 2022년 4월 27일 오후 7:59 UTCmonitoring

   A fix has been implemented and we are monitoring results.

3. 2022년 4월 27일 오후 8:41 UTCresolved

   This issue has been resolved.

1. 2022년 2월 14일 오전 9:27 UTCinvestigating

   We are investigating an issue affecting flow delivery.

2. 2022년 2월 14일 오전 9:46 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2022년 2월 14일 오전 9:49 UTCresolved

   This incident has been resolved.