The incident is resolved. Error rates are back to normal, and stable service has been confirmed. We will publish a Root cause analysis once our review of the incident is complete.

After several hours of monitoring, our metrics show that error rate has remained at its stable baseline since 17:55 UTC; the increase in Dubbing platform latency and failure rate is now resolved.

We have monitored error metrics and have confirmed that as of 15:15 UTC, we do not see continuing Agent SIP conversation failures. We will conduct an internal investigation and post a full Root Cause Analysis upon conclusion.

Music had reduced availability after a latent infrastructure configuration issue was triggered by routine automated maintenance. This stopped new instances from starting and prevented automated recovery, and service was restored by manual intervention.

The service is now fully operational again.

The issue has been resolved, latency is back to normal.

We have not seen any further errors after the fix was applied. All services are fully operational and stable. We will post an RCA on our status page after further investigation.

Our engineers have confirmed that STT latency has fully recovered.

The issue has been fully resolved and everything is functional again.

Our engineers have deployed a fix that has fully restored Claude MCP functionality.

After completing the monitoring stage, we have confirmed that STT latency has returned to baseline stability.

We’ll mark this incident as resolved.

Our ticketing system is operational again, though the outage materially affected its setup. We’re working with the team to restore full functionality, but capacity is sufficient to consider the incident resolved.

The issue has been resolved. A root cause analysis will be shared shortly.

Our engineers have traced media loading error rates as they have returned to baseline. Studio, Audiobooks, Image & Video, Music and Dubbing products should now functional normally.

Inbound calls are currently operational.

The provider resolved the underlying issue at 07:13 UTC and error rates immediately returned to baseline.

After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.