Knowledge Base Subscribe to updates
Some systems are experiencing issues

About This Site

This is the auvious status page where you can see the current status of our servers and get updates on how our system is doing. When we become aware of any issue with our systems, we will post an update here.

If you are having any troubles with auvious, please make sure to let our team know at support@auvious.com

Stickied Incidents

13th July 2026

Intermittent recording export failures

We are investigating intermittent issues affecting post-call recording exports across all regions. Some recordings may fail to export. Live video and audio sessions are not affected. Our engineering team is working to mitigate the issue and deploy a permanent fix. We will provide further updates as they become available.

  • Production monitoring confirms that recording exports have been operating normally since 25 July 2026. This incident is resolved.

  • The updated release has been deployed to production. Recording exports should now proceed normally while we monitor the results.

  • Final validation is underway, and we expect to deploy within the next couple of days. We will provide an update once deployment is complete.

  • A fix has been implemented and is pending QA validation. We expect to deploy the new version soon. The deployment will not retroactively change recording exports that have already failed; after it is deployed, subsequent export attempts should proceed normally. We will provide another update once deployment is complete.

    • Past Incidents

    5th June 2022

    No incidents reported

    4th June 2022

    No incidents reported

    3rd June 2022

    No incidents reported

    2nd June 2022

    No incidents reported

    1st June 2022

    Video & Audio High Latency

    Experiencing issues which so far are traced down to communication between Googles Cloud Http Load Balancer and Auvious Backend sevices. A workaround seems to work so far, but requires manual action periodically.

  • Issue was traced down yesterday, and fix was applied immediately since it came down to configuring correctly the maximum connection limits of the http stack of our core services. So this issue was not due to Google's Load Balancer, what initially lead us that way were the available logs and traces we had. By improving logs,instrumentation and taking more traces we were able to correctly identify and correct the issue.

  • System is back online since 2022-06-13 13:32:20.220 GMT. The partial outage of the service lasted for about 15 minutes, and it seems stable now. We're closely monitoring the service and investigating the cause with the assistance of Google Support.

  • Issue has appeared again at 2022-06-13 13:16:17.339 GMT. Users should experience disconnects or failures using the service. We're working on getting the system back in service. The issue cause is latency introduced Google Http Load balancer, so we're working closely with Google's support in order to resolve this and avoid similar issues in the future.

  • Issue has occured again today between 2022-06-02 16:08:10.678 GMT and 2022-06-02 16:17:58.131 GMT and it affected a small percentage of users. The related ticket at Google has been upgraded to P1 Critical and escalated in order to resolve this faster.

  • Issue has not been detected again since yesterday, we're still investigating with the help of Google support the root cause of yesterday's issues.