Dubber incident
Incident impacting the availability of call playback
Dubber experienced a major incident on June 25, 2025 affecting United Kingdom (UK) - Call Playback and Europe (EU) - Call Playback and 1 more component, lasting 9d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 25, 2025, 01:09 PM UTC
We are aware that some customers are experiencing issues with playing calls back in the in the Dubber portal. We are working to resolve the incident as soon as possible and will provide regular updates.
- investigating Jun 25, 2025, 02:23 PM UTC
We are aware that some customers are experiencing issues with playing calls back in the in the Dubber portal. We are working to resolve the incident as soon as possible and will provide regular updates.
- investigating Jun 25, 2025, 03:28 PM UTC
We are aware that some customers are experiencing issues with playing calls back in the in the Dubber portal. We are working to resolve the incident as soon as possible and will provide regular updates.
- identified Jun 25, 2025, 05:35 PM UTC
The issue has been identified and Dubber is working to correct the problems, we will continue to work on this to return to normal operation. We will continue to provide updates as they are available.
- identified Jun 25, 2025, 07:35 PM UTC
Work continues on this playback issue, our team is working to fully resolve this problem and to return to normal service as soon as possible.
- identified Jun 26, 2025, 05:43 AM UTC
Dubber is continuing remediation work on this incident. We will continue to provide updates on this status page.
- identified Jun 26, 2025, 02:37 PM UTC
Dubber is continuing remediation work on this incident. We will continue to provide updates on this status page.
- monitoring Jun 26, 2025, 04:47 PM UTC
Dubber has identified the issue and we have taken corrective measures to return to a full operational mode across the impacted regions. Dubber will be monitoring the performance to verify this issue is fully resolved and will provide additional information once we conclude our review.
- resolved Jul 04, 2025, 02:54 PM UTC
This incident has been resolved.