ccaas-status - Notice history

This incident has been resolved.
We'll post the root cause shortly as the "postmortem" of this incident.

We've identified the source of the problem and are working to fix it as soon as we can.

The Graia SRE team has completed the infrastructure mitigation and migrated the affected services to a secondary Azure Service Bus namespace.

Following the migration, no further Agent UI delays have been observed and the platform has remained stable during testing and monitoring.

We will continue to monitor service latency and overall platform health overnight while Microsoft continues its investigation into the underlying Azure issue.

This incident is now resolved.

Thank you for your patience.

Microsoft has reviewed the issue and is continuing its investigation into the observed delays with Azure services. They have requested some additional technical and diagnostic information from our side to help identify the underlying cause.

We are gathering the required details and will provide them to Microsoft. We’ll keep you updated as soon as we receive further findings or guidance.

We have opened a high-priority support case with Microsoft regarding the reported Agent UI slowness affecting services hosted on Azure. We are continuing to investigate the issue with Microsoft.

We have identified a component that could be contributing to the reported Agent UI slowness and are currently performing additional checks around this area. We are continuing our investigation.

We will provide another update as soon as more information is available.

Customers confirmed service was operational.

This incident has been resolved.

Recording Manager service restored and operational. Internal voice test successful. Stuck-call recovery initiated.

Third automatic restart of the Recording Manager service initiated.

Customers confirmed service was operational.

Recording Manager service restored and operational. Internal voice test successful. Stuck-call recovery initiated.

Second automatic restart of the Recording Manager service initiated.

Slowness identified in the Recording Manager service.

Customers confirmed service was operational.

Recording Manager service restored and operational. Internal voice test successful. Stuck-call recovery initiated.