Stonly Outage History

17 incidents recorded over the last 365 days, 15 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.

Live Stonly status100.00% uptime history

Every Recorded Stonly Incident

Stonly incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 8, 2026Stonly editor not loadingThis incident has been resolved.30 minResolved
Aug 17, 2026Intermittent failures when loading guidesThis incident has been resolved.32 minResolved
Jul 28, 2026Changes to triggers are applied with a DelayAny modifications to the triggers, including enablement, disablement, and updates, are applied with a delay. This is due to widget servers losing an established connection to the main server and the self-healing process…-1628 minResolved
Jul 16, 2026Platform outageThis incident has been resolved.14 minResolved
Jun 9, 2026AI Answers partial outageThis incident has been resolved.24 minResolved
Jun 3, 2026Guide Summary generation and AI Agent assist issuesThis incident has been resolved.50h 33mResolved
May 28, 2026Infrastructure updatesThe scheduled maintenance has been completed.2h 0mScheduled
May 6, 2026Intermittent guide loading timeoutsBetween 12:29 and 13:27 we've seen increased amount of errors when loading guides.-183 minResolved
May 4, 2026Intermittent platform outagesThis incident has been resolved.1h 39mResolved
Apr 30, 2026Performance degradation on KBs and GuidesThis incident has been resolved.49 minResolved
Apr 28, 2026Due to service provider networking issues, Automation and Segment integration is downThis incident has been resolved.1h 41mResolved
Mar 30, 2026Problem with the Guide publish functionalityThis incident has been resolved.9 minResolved
Jan 27, 2026AI Answers not returning resultsThis incident has been resolved.3h 29mResolved
Jan 19, 2026Problem with new release packageThis incident has been resolved.23 minResolved
Dec 11, 2025Guide updates not reflected in AI Bot answersThis incident has been resolved.1h 37mResolved
Nov 6, 2025Upgrade of underlying infrastructureThe scheduled maintenance has been completed.2h 0mScheduled
Nov 5, 2025Increased error rate for embedded guidesThis incident has been fully resolved.2h 32mResolved

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 Stonly 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 Stonly 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 Stonly 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 Stonly outage in this window ran 2d 2h, against a mean recovery of 4h 34m. If you depend on Stonly 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.