Sinch incident

Customer Dashboard - Conversation API - Analytics Degradation

Minor Resolved View vendor source →

Sinch experienced a minor incident on June 10, 2026 affecting Analytics, lasting 27d 19h. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2026, 12:56 PM UTC
Resolved
Jul 08, 2026, 08:05 AM UTC
Duration
27d 19h
Detected by Pingoru
Jun 10, 2026, 12:56 PM UTC

Affected components

Analytics

Update timeline

  1. 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 [email protected].

  2. investigating Jun 10, 2026, 02:09 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 10, 2026, 06:18 PM UTC

    We are continuing to investigate this issue.

  4. investigating Jun 11, 2026, 05:15 AM UTC

    We are continuing to investigate this issue.

  5. investigating Jun 11, 2026, 02:15 PM UTC

    We are continuing to investigate this issue.

  6. investigating Jun 12, 2026, 03:35 PM UTC

    We are continuing to investigate this issue.

  7. investigating Jun 13, 2026, 04:15 PM UTC

    We are continuing to investigate this issue.

  8. investigating Jun 14, 2026, 04:20 PM UTC

    We are continuing to investigate this issue.

  9. investigating Jun 15, 2026, 05:14 PM UTC

    We are continuing to investigate this issue.

  10. investigating Jun 16, 2026, 06:13 PM UTC

    We are continuing to investigate this issue.

  11. investigating Jun 17, 2026, 07:05 PM UTC

    We are continuing to investigate this issue.

  12. investigating Jun 18, 2026, 10:19 PM UTC

    We are continuing to investigate this issue.

  13. investigating Jun 19, 2026, 11:41 PM UTC

    We are continuing to investigate this issue.

  14. investigating Jun 21, 2026, 04:09 AM UTC

    We are continuing to investigate this issue.

  15. investigating Jun 22, 2026, 05:11 AM UTC

    We are continuing to investigate this issue.

  16. investigating Jun 23, 2026, 05:59 AM UTC

    We are continuing to investigate this issue.

  17. investigating Jun 24, 2026, 06:10 AM UTC

    We are continuing to investigate this issue.

  18. investigating Jun 25, 2026, 08:44 AM UTC

    We are continuing to investigate this issue.

  19. investigating Jun 26, 2026, 09:59 AM UTC

    We are continuing to investigate this issue.

  20. investigating Jun 27, 2026, 10:09 AM UTC

    We are continuing to investigate this issue.

  21. investigating Jun 28, 2026, 01:32 PM UTC

    We are continuing to investigate this issue.

  22. investigating Jun 29, 2026, 01:43 PM UTC

    We are continuing to investigate this issue.

  23. identified Jun 30, 2026, 07:43 AM UTC

    The issue has been identified and a fix is being implemented.

  24. identified Jul 01, 2026, 12:29 PM UTC

    We are continuing to work on a fix for this issue.

  25. identified Jul 02, 2026, 12:46 PM UTC

    We are continuing to work on a fix for this issue.

  26. identified Jul 03, 2026, 01:53 PM UTC

    We are continuing to work on a fix for this issue.

  27. identified Jul 04, 2026, 05:44 PM UTC

    We are continuing to work on a fix for this issue.

  28. identified Jul 05, 2026, 07:27 PM UTC

    We are continuing to work on a fix for this issue.

  29. identified Jul 06, 2026, 09:22 PM UTC

    We are continuing to work on a fix for this issue.

  30. identified Jul 07, 2026, 11:58 PM UTC

    We are continuing to work on a fix for this issue.

  31. resolved Jul 08, 2026, 08:05 AM UTC

    This incident has been resolved.