Tidio status history
Current state: operational — “All Systems Operational” per https://status.tidio.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.
How long do Tidio incidents last?
From 8 incidents with a vendor-posted start and resolve time. Longest on record: Connectivity issues with Meta integrations — 4.6 days (2026-06-04 15:09 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (8)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-01 07:02 UTC | Issues with ticketing (emails) | resolved | major | 6 h 05 min |
| 2026-06-12 14:45 UTC | Outage of Meta business products | resolved | major | 3 h 40 min |
| 2026-06-04 15:09 UTC | Connectivity issues with Meta integrations | resolved | none | 4 d 15 h |
| 2026-04-17 16:07 UTC | Connectivity issues for some users | resolved | minor | 5 h 33 min |
| 2026-04-09 14:35 UTC | Degraded performance for some users | resolved | minor | 2 h 08 min |
| 2026-01-15 07:18 UTC | Connectivity issues for some users | resolved | major | 28 min |
| 2025-12-05 09:05 UTC | Connectivity issues for some users | resolved | major | 3 h 40 min |
| 2025-11-18 11:38 UTC | Connectivity issues for some users | resolved | none | 8 h 25 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Tidio with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"tidio"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
