Telesmart incident
Tendfor Contact Centre - Degraded Performance
Telesmart experienced a minor incident on February 1, 2022 affecting Cloud Calling for Microsoft Teams and Dubber Recording, lasting 12d 17h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 01, 2022, 01:31 AM UTC
We are aware of an issue, where some callers can not to be answered by an agent. Our engineering teams are investigating to identify the cause. A further update will occur in 30 Minutes.
- investigating Feb 01, 2022, 02:04 AM UTC
Our engineering teams are still investigating to determine the cause, a further update will occur in 30 minutes.
- investigating Feb 01, 2022, 03:10 AM UTC
We are continuing to investigate this issue.
- identified Feb 01, 2022, 07:04 PM UTC
We have identified a component that looks to be at fault, we are working with our external suppliers on a fix. A further update will occur at 11am today.
- monitoring Feb 01, 2022, 10:28 PM UTC
The degraded service has been resolved, we are currently monitoring.
- identified Feb 01, 2022, 11:35 PM UTC
The issue has reappeared late this morning and only affects customers with the Dubber recording service. Our service providers have logged a support ticket with Microsoft who are working toward a resolution. Next update approx. 2.30pm.
- identified Feb 02, 2022, 12:49 AM UTC
We are continuing to work on a fix for this issue.
- identified Feb 02, 2022, 02:56 AM UTC
Microsoft are working to fix the component that is causing the problem, we don't have an ETA from Microsoft of when it will be resolved. A further update will be provided once we receive an update from Microsoft.
- identified Feb 03, 2022, 03:17 AM UTC
Our service provider is still working with Microsoft on resolving this issue, a further update will be provided once we have an update from our service provider.
- monitoring Feb 03, 2022, 06:30 PM UTC
We have been advised that Microsoft implemented a fix yesterday evening, our initial testing looks positive. We will continue to monitor the service.
- resolved Feb 13, 2022, 07:19 PM UTC
This incident has been resolved.