Vendor Status Watch

← all vendors

Dixa status history

Current state: operational — “All Systems Operational” per https://status.dixa.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
3incidents, last 90 days
23incidents on record
Incidents per week, last 12 weeks:

How long do Dixa incidents last?

2.0 hmedian incident duration23 measured
6.0 h90th percentile1 in 10 ran longer
2.2 hmedian, major/critical only11 incidents

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)

StartedIncidentStatusImpactDuration
2026-07-28 10:47 UTCAdvanced Insight & Miuros: Degraded performancepostmortemmajor28 min
2026-07-28 07:00 UTCServices not fully functioningpostmortemnone0 min
2026-06-29 09:04 UTCAdvanced Insights unavailableresolvedcritical6 h 06 min
2026-04-23 11:42 UTCUpdate delays on Conversation view and Real-Time Dashboardresolvednone8 min
2026-04-08 16:32 UTCPartial outage of Agent Interface connectionspostmortemmajor51 min
2026-03-18 15:02 UTCDegraded performance: AiCoPilot: Smart repliespostmortemminor4 h 49 min
2026-03-11 08:18 UTCDegraded performancepostmortemmajor3 h 12 min
2026-03-10 12:38 UTCDegraded performancepostmortemmajor4 h 25 min
2026-03-02 18:08 UTCDegraded performancepostmortemmajor2 h 13 min
2026-02-20 14:24 UTCDegraded performancepostmortemmajor10 min
2026-01-27 11:41 UTCDegraded performance - AI Voice transcriptpostmortemminor55 min
2026-01-06 15:24 UTCDegraded performance - Contact Search in Outbound Callingresolvedminor15 min
2025-12-22 10:30 UTCDegraded performance - AI voice transcriptions and delayed webhook eventspostmortemminor3 h 11 min
2025-12-16 19:49 UTCIntermittent issues with AI featurespostmortemminor44 min
2025-12-08 13:30 UTCSearch - Partial Outageresolvednone0 min
2025-11-18 11:59 UTCDegraded performancepostmortemminor3 h 43 min
2025-10-20 16:55 UTCDegraded performance - telephony servicespostmortemminor6 h 01 min
2025-10-20 07:16 UTCMultiple services disruptionspostmortemmajor6 h 02 min
2025-10-14 08:24 UTCDegraded performance - Translations not workingpostmortemmajor4 h 16 min
2025-09-09 13:45 UTCDegraded performance for Analytics and Real-time Dashboardpostmortemminor2 h 03 min
2025-08-26 14:30 UTCMim Data Source Sync Failurespostmortemminor40 h 21 min
2025-08-26 12:20 UTCDNS Configuration Issue Impacting API Connectivitypostmortemcritical0 min
2025-08-26 08:58 UTCTrustPilot Queue Service Outagepostmortemcritical53 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
}