Appcues Outage History
10 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Appcues Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 14, 2026 | Scheduled US Region DB MaintenanceWe will be performing scheduled maintenance to upgrade one of our core databases in our US region. We’ve timed this window for our lowest period of Studio and Builder usage to keep the impact on your team as small as… | 6h 0m | Scheduled |
| Oct 30, 2026 | Appcues SDK performance degredationAll systems are showing stable metrics. Incident is over. During the incident, response time to SDK sent messages increased by 200% causing delays for content delivery. | 19 min | Resolved |
| Oct 6, 2026 | Email Sending DelayDelayed messages have been processed. All systems operating normally. | 9h 32m | Resolved |
| Jun 7, 2026 | Scheduled System MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Apr 21, 2026 | EU Studio login issueThe issue has been resolved | 58 min | Resolved |
| Mar 16, 2026 | Appcues Studio Unavailable in the EUWe've addressed the underlying issue and Studio in the EU is now available. | 18 min | Resolved |
| Feb 9, 2026 | Appcues Studio UnavailableThe Appcues Studio is available and fully functional. | 7 min | Resolved |
| Dec 15, 2025 | Appcues Studio UnavailableWe'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. | 0 min | Resolved |
| Nov 6, 2025 | Studio Analytics DegredationThe root cause has been identified and the query pattern that caused the issue has been mitigated. | 1h 2m | Resolved |
| Nov 5, 2025 | Appcues Studio and Builder OutageA 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. | -48 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Appcues incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Appcues Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Appcues acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Appcues outage in this window ran 9h 32m, against a mean recovery of 2h 15m. If you depend on Appcues in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.