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

    15th July 2023

    No incidents reported

    14th July 2023

    No incidents reported

    13th July 2023

    No incidents reported

    12th July 2023

    No incidents reported

    11th July 2023

    Video & Audio DNS related malfunction

    An issue occurred today, while migrating the auvious.video DNS zone to Google Cloud DNS. A missing DNS alias entry caused our European service to malfunction for several minutes. This was not detected by the monitoring system, because it uses a different (not an alias) DNS entry to check the liveness of the system. The missing alias was added, but also the system configuration was updated to not use the alias, in order to avoid any more downtime due to DNS caching of missing entries.

    We're sorry for any inconvenience, and we're currently making sure to update our systems in order to avoid any similar situations in the future.