Appcues Outage History

Appcues is up right now

Pingoru has recorded 59 incidents for Appcues: 14 in the last 12 months and 1 in the last 90 days.

Source: status.appcues.com

59incidents recorded
14last 12 months
1last 90 days
52 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct2%
Pingoru began tracking Appcues in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 2026110 of 528 (2%)

Incidents, newest first

Major October 6, 2026 Email Sending Delay 9h 32m Workflow Processing

Started Oct 06, 2026, 03:37 AM UTC· resolved Oct 06, 2026, 01:09 PM UTC

  1. identified Oct 06, 2026, 10:16 AM UTC

    Email sending for Appcues Workflows is delayed. We have identified the issue and are working on a fix.

  2. monitoring Oct 06, 2026, 10:48 AM UTC

    The underlying issue is fixed and emails are processing correctly again. We are working through a backlog of delayed messages.

  3. resolved Oct 06, 2026, 01:09 PM UTC

    Delayed messages have been processed. All systems operating normally.

Read the full incident report →

Major April 21, 2026 EU Studio login issue 58m Studio (EU)

Started Apr 21, 2026, 01:47 PM UTC· resolved Apr 21, 2026, 02:45 PM UTC

  1. identified Apr 21, 2026, 01:47 PM UTC

    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. resolved Apr 21, 2026, 02:45 PM UTC

    The issue has been resolved

Read the full incident report →

Minor March 16, 2026 Appcues Studio Unavailable in the EU –

Started Mar 16, 2026, 10:19 PM UTC· resolved Mar 16, 2026, 10:19 PM UTC

  1. monitoring Mar 16, 2026, 10:19 PM UTC

    Mar 16, 18:19 EDT Resolved - We've addressed the underlying issue and Studio in the EU is now available. Mar 16, 18:01 EDT Investigating - 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.

Read the full incident report →

Minor February 9, 2026 Appcues Studio Unavailable –

Started Feb 09, 2026, 06:56 PM UTC· resolved Feb 09, 2026, 06:56 PM UTC

  1. monitoring Feb 09, 2026, 06:56 PM UTC

    Feb 9, 13:56 EST Resolved - The Appcues Studio is available and fully functional. Feb 9, 13:49 EST Identified - 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.

Read the full incident report →

Minor November 6, 2025 Studio Analytics Degredation –

Started Nov 06, 2025, 08:00 PM UTC· resolved Nov 06, 2025, 08:00 PM UTC

  1. monitoring Nov 06, 2025, 08:00 PM UTC

    Nov 6, 15:00 EST Resolved - The root cause has been identified and the query pattern that caused the issue has been mitigated. Nov 6, 13:57 EST Investigating - We're investigating delays returning analytics data in Studio.

Read the full incident report →

Notice November 5, 2025 Appcues Studio and Builder Outage 10m

Started Nov 05, 2025, 02:23 PM UTC· resolved Nov 05, 2025, 02:33 PM UTC

  1. resolved Nov 05, 2025, 03:11 PM UTC

    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.

Read the full incident report →

Notice October 30, 2025 Appcues Studio and Builder Login Issue –

Started Oct 30, 2025, 07:00 PM UTC· resolved Oct 30, 2025, 07:00 PM UTC

  1. resolved Oct 30, 2025, 07:49 PM UTC

    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.

Read the full incident report →

Minor October 12, 2025 Scheduled DB Maintenance –

Started Oct 12, 2025, 04:00 AM UTC· resolved Oct 12, 2025, 04:00 AM UTC

  1. monitoring Oct 12, 2025, 04:00 AM UTC

    Oct 12, 00:00 EDT Completed - The scheduled maintenance has been completed. Oct 11, 22:00 EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 3, 10:27 EDT Scheduled - We will be performing maintenance on the Appcues platform starting at 10:00 PM EST on October 11th. While we do not expect service interruptions, some users may experience intermittent disruptions to our services. This maintenance is expected to be completed within two hours. We appreciate your understanding as we work to enhance the reliability of our services.

Read the full incident report →

Minor October 10, 2025 SDK Temporarily Unavailable –

Started Oct 10, 2025, 02:30 AM UTC· resolved Oct 10, 2025, 02:30 AM UTC

  1. monitoring Oct 10, 2025, 02:30 AM UTC

    Oct 9, 22:30 EDT Resolved - 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.

Read the full incident report →

Critical May 27, 2025 Some clients are unable to load Appcues Studio 1h 14m Studio (US)

Started May 27, 2025, 01:42 PM UTC· resolved May 27, 2025, 02:56 PM UTC

  1. investigating May 27, 2025, 01:42 PM UTC

    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. identified May 27, 2025, 01:59 PM UTC

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

  3. monitoring May 27, 2025, 02:34 PM UTC

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

  4. resolved May 27, 2025, 02:56 PM UTC

    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.

Read the full incident report →