Incident detail

Customer Dashboard - Conversation API - Analytics Degradation

Resolved incidentMinor

Provider

Timeline window

Jun 10, 2026, 12:56 PM UTC to Jul 8, 2026, 8:05 AM UTC

Outage alerts

Get alerted the next time Sinch breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alerts How Sinch alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

Investigating
Jun 10, 2026, 12:56 PM UTC
We are currently facing a service degradation on dashboard analytics for a subset of Conversation API traffic sent.
Impact: Customers may notice an inaccurate status for a subset of Conversation API messages
For any inquiries, please contact support@sinch.com.
Investigating
Jun 10, 2026, 2:09 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 10, 2026, 6:18 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 11, 2026, 5:15 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 11, 2026, 2:15 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 12, 2026, 3:35 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 13, 2026, 4:15 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 14, 2026, 4:20 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 15, 2026, 5:14 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 16, 2026, 6:13 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 17, 2026, 7:05 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 18, 2026, 10:19 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 19, 2026, 11:41 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 21, 2026, 4:09 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 22, 2026, 5:11 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 23, 2026, 5:59 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 24, 2026, 6:10 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 25, 2026, 8:44 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 26, 2026, 9:59 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 27, 2026, 10:09 AM UTC
We are continuing to investigate this issue.
Investigating
Jun 28, 2026, 1:32 PM UTC
We are continuing to investigate this issue.
Investigating
Jun 29, 2026, 1:43 PM UTC
We are continuing to investigate this issue.
Identified
Jun 30, 2026, 7:43 AM UTC
The issue has been identified and a fix is being implemented.
Identified
Jul 1, 2026, 12:29 PM UTC
We are continuing to work on a fix for this issue.
Identified
Jul 2, 2026, 12:46 PM UTC
We are continuing to work on a fix for this issue.
Identified
Jul 3, 2026, 1:53 PM UTC
We are continuing to work on a fix for this issue.
Identified
Jul 4, 2026, 5:44 PM UTC
We are continuing to work on a fix for this issue.
Identified
Jul 5, 2026, 7:27 PM UTC
We are continuing to work on a fix for this issue.
Identified
Jul 6, 2026, 9:22 PM UTC
We are continuing to work on a fix for this issue.
Identified
Jul 7, 2026, 11:58 PM UTC
We are continuing to work on a fix for this issue.
Resolved
Jul 8, 2026, 8:05 AM UTC
This incident has been resolved.