Tidio Outage History
9 incidents recorded over the last 365 days, 9 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 Tidio Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Webhook events not being deliveredThis issue has been resolved, and webhook events are being delivered normally again. Events affected during the incident were delayed rather than lost, and they’ve now been processed. We’re sorry for the disruption… | 1h 53m | Resolved |
| Jul 1, 2026 | Issues with ticketing (emails)This incident has been resolved. | 6h 5m | Resolved |
| Jun 12, 2026 | Outage of Meta business productsMeta has resolved the issues affecting their business products, including WhatsApp, Facebook, and Instagram. All services are now fully restored and operating normally. | 3h 40m | Resolved |
| Jun 4, 2026 | Connectivity issues with Meta integrationsThis incident has been resolved. Meta restored the API access and all integrations (WhatsApp, Messenger, Instagram) are working on production. Thank you for your patience in this difficult moment. | 109h 57m | Resolved |
| Apr 17, 2026 | Connectivity issues for some usersEverything is back up and running. Thank you for your patience | 5h 33m | Resolved |
| Apr 9, 2026 | Degraded performance for some usersThis incident has been resolved, services are fully operational. | 2h 8m | Resolved |
| Jan 15, 2026 | Connectivity issues for some usersEverything is back up and running. Thank you for your patience | 28 min | Resolved |
| Dec 5, 2025 | Connectivity issues for some usersEverything is back up and running. | 3h 40m | Resolved |
| Nov 18, 2025 | Connectivity issues for some usersThis incident is now resolved. Thank you for your patience and understanding. | 8h 25m | 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 Tidio 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 Tidio 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 Tidio 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 Tidio outage in this window ran 4d 13h, against a mean recovery of 15h 45m. If you depend on Tidio 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.