Chatwoot Outage History

6 incidents recorded over the last 365 days, 6 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 Chatwoot Incident

Chatwoot incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 26, 2026Service Degradation: Email Delivery Disruption1603h 32mResolved
Jul 24, 2026Service Degradation - Meta permissions affecting Instagram, Facebook Messenger, and WhatsApp1639h 41mResolved
Jul 20, 2026Service Degradation: Email Delivery Disruption1747h 23mResolved
Jul 19, 2026Scheduled DB maintenance on 19 July 20262h 0mResolved
Jul 6, 2026Service Degradation - Meta authorization affecting Instagram and Facebook Messenger2080h 46mResolved
Jun 17, 2026Chatwoot Cloud Service Disruption1813h 22mResolved

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 Chatwoot 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 Chatwoot 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 Chatwoot 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 Chatwoot outage in this window ran 86d 16h, against a mean recovery of 61d 17h. If you depend on Chatwoot 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.