# Customer Dashboard - Conversation API - Analytics Degradation

- Provider: [Sinch](https://down.guide/sinch)
- Level: confirmed
- Impact: Degraded
- lasted 27d 19h
- started 2026-06-10 12:56 UTC
- Analytics
- id: DWN-7280f20a0a
- Official page: https://stspg.io/z9b6q7rqzh59

## Updates from Sinch
### 2026-06-10 12:56 UTC: investigating
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.

### 2026-06-10 14:09 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-10 18:18 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-11 05:15 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-11 14:15 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-12 15:35 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-13 16:15 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-14 16:20 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-15 17:14 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-16 18:13 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-17 19:05 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-18 22:19 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-19 23:41 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-21 04:09 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-22 05:11 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-23 05:59 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-24 06:10 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-25 08:44 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-26 09:59 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-27 10:09 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-28 13:32 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-29 13:43 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-30 07:43 UTC: identified
The issue has been identified and a fix is being implemented.

### 2026-07-01 12:29 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-02 12:46 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-03 13:53 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-04 17:44 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-05 19:27 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-06 21:22 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-07 23:58 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-07-08 08:05 UTC: resolved
This incident has been resolved.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).