engati Outage History
3 incidents recorded over the last 365 days, 3 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 engati Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 13, 2026 | Issue with broadcast being stuck in Pending on WhatsApp state. | 23h 0m | Resolved |
| Sep 23, 2026 | Template Syncing Issue | 1h 52m | Resolved |
| Sep 23, 2026 | Template Creation Issue | 8h 30m | 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 engati 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 engati 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 engati 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 engati outage in this window ran 23h, against a mean recovery of 11h 7m. If you depend on engati 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.