Dixa status history
Current state: operational — “All Systems Operational” per https://status.dixa.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Dixa incidents last?
From 23 incidents with a vendor-posted start and resolve time. Longest on record: Mim Data Source Sync Failures — 40.4 h (2025-08-26 14:30 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 (23)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-28 10:47 UTC | Advanced Insight & Miuros: Degraded performance | postmortem | major | 28 min |
| 2026-07-28 07:00 UTC | Services not fully functioning | postmortem | none | 0 min |
| 2026-06-29 09:04 UTC | Advanced Insights unavailable | resolved | critical | 6 h 06 min |
| 2026-04-23 11:42 UTC | Update delays on Conversation view and Real-Time Dashboard | resolved | none | 8 min |
| 2026-04-08 16:32 UTC | Partial outage of Agent Interface connections | postmortem | major | 51 min |
| 2026-03-18 15:02 UTC | Degraded performance: AiCoPilot: Smart replies | postmortem | minor | 4 h 49 min |
| 2026-03-11 08:18 UTC | Degraded performance | postmortem | major | 3 h 12 min |
| 2026-03-10 12:38 UTC | Degraded performance | postmortem | major | 4 h 25 min |
| 2026-03-02 18:08 UTC | Degraded performance | postmortem | major | 2 h 13 min |
| 2026-02-20 14:24 UTC | Degraded performance | postmortem | major | 10 min |
| 2026-01-27 11:41 UTC | Degraded performance - AI Voice transcript | postmortem | minor | 55 min |
| 2026-01-06 15:24 UTC | Degraded performance - Contact Search in Outbound Calling | resolved | minor | 15 min |
| 2025-12-22 10:30 UTC | Degraded performance - AI voice transcriptions and delayed webhook events | postmortem | minor | 3 h 11 min |
| 2025-12-16 19:49 UTC | Intermittent issues with AI features | postmortem | minor | 44 min |
| 2025-12-08 13:30 UTC | Search - Partial Outage | resolved | none | 0 min |
| 2025-11-18 11:59 UTC | Degraded performance | postmortem | minor | 3 h 43 min |
| 2025-10-20 16:55 UTC | Degraded performance - telephony services | postmortem | minor | 6 h 01 min |
| 2025-10-20 07:16 UTC | Multiple services disruptions | postmortem | major | 6 h 02 min |
| 2025-10-14 08:24 UTC | Degraded performance - Translations not working | postmortem | major | 4 h 16 min |
| 2025-09-09 13:45 UTC | Degraded performance for Analytics and Real-time Dashboard | postmortem | minor | 2 h 03 min |
| 2025-08-26 14:30 UTC | Mim Data Source Sync Failures | postmortem | minor | 40 h 21 min |
| 2025-08-26 12:20 UTC | DNS Configuration Issue Impacting API Connectivity | postmortem | critical | 0 min |
| 2025-08-26 08:58 UTC | TrustPilot Queue Service Outage | postmortem | critical | 53 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 Dixa with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"dixa"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}