Incidents and maintenance reported on status page for Autocalls https://status.autocalls.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/4d7126272dfedeb1602f83895496bc3d.png https://status.autocalls.ai/ en https://status.autocalls.ai/incident/1042945 Mon, 31 Aug 2026 12:02:00 -0000 https://status.autocalls.ai/incident/1042945#f618c3255830574138978fe1a93a92f2b45e7b4eb6920a7170678c19736daa9c Incident Fixed https://status.autocalls.ai/incident/1042945 Mon, 31 Aug 2026 11:56:00 -0000 https://status.autocalls.ai/incident/1042945#f91c29367c8a710407f40130405d815332f9c2c580c07a9d4dc1f4c12ce3aa5f Incident Upstream provider outage is cascading through our stack. Redis is down as a result, which is pushing load onto the database and degrading everything behind it. Services are partially working, not fully down. Requests complete but with heavy lag or intermittent origin timeouts. https://status.autocalls.ai/incident/851648 Tue, 17 Mar 2026 22:42:00 -0000 https://status.autocalls.ai/incident/851648#a89b562ef6ce830c0156e6fcd1017447eb1b1b31bebfe25459896a0ee02917d7 Incident A scheduled database schema update triggered a metadata lock on our read-replica database, which prevented all tenant identification queries from completing. This caused the white label platform dashboards to become unresponsive, returning timeout errors for all dashboard login and UI requests. **Calls, automations, and API services were not affected.** Only white label tenant dashboard access was impacted. **Root cause** A column addition migration executed successfully on the primary database but stalled on the read replica due to a pre-existing long-running query (1+ hours) that held a conflicting metadata lock. This created a cascading deadlock: the pending schema change blocked all subsequent read queries to the affected table, which is queried on every request for tenant resolution. The read replica was restarted to clear the deadlocked state. The schema migration then applied cleanly, and all services resumed normal operation. https://status.autocalls.ai/maintenance/804511 Wed, 14 Jan 2026 17:24:08 -0000 https://status.autocalls.ai/incident/804511#97b08a8cc5633e11cfd2110515a4dfbcd59e95917d64fd5d0d2e46930d7930ea Maintenance We will be performing scheduled maintenance to upgrade multiple components of our application in order to improve overall performance, speed, and reliability. These changes are designed to make the platform run faster and feel smoother. ### What to Expect During the maintenance window, you may occasionally experience: - Errors when loading the dashboard - Calls not going through or being temporarily unavailable - Short interruptions in specific features ### Availability During Maintenance The upgrade will be carried out using a **granular, rolling migration approach**, meaning the application will remain available most of the time. However, brief and unexpected downtimes may occur while individual modules are being migrated. We appreciate your patience and understanding as we work to enhance your experience. https://status.autocalls.ai/incident/784974 Fri, 12 Dec 2025 08:26:00 -0000 https://status.autocalls.ai/incident/784974#8d1bdb64a3afe71d99fc0600acb1e0f1ec41a06b73531239b34d9de477103a54 Incident Our Azure-hosted database experienced a brief outage lasting approximately 10 minutes due to an issue on Microsoft Azure’s side. This caused a short period of service unavailability on our platform. The issue has been fully resolved, and all services are operating normally. We’re monitoring the situation closely and appreciate your understanding. https://status.autocalls.ai/maintenance/743814 Wed, 15 Oct 2025 05:00:07 -0000 https://status.autocalls.ai/incident/743814#2a0a7ace526dc174d7cb37f643c0327d2aa436f3155f40cc3c621274405bd2c3 Maintenance Scheduled maintenance by Azure for updating database service. https://status.autocalls.ai/incident/738645 Mon, 06 Oct 2025 18:16:00 -0000 https://status.autocalls.ai/incident/738645#20a8ec02ad9bc4aace3781418ee774c65ebe84ada24b2efd2c9d0eb17e287c7f Incident Due to an automated and unexpected AWS server update main platform and workers went down. https://status.autocalls.ai/incident/711511 Sun, 24 Aug 2025 13:10:00 -0000 https://status.autocalls.ai/incident/711511#4e9866cfd87d46b3bba0f1b625cf6fafbc06b127ee76c6aa00f26196b182aa80 Incident During core platform updates we had a downtime on Sunday of 1 hour. https://status.autocalls.ai/incident/605633 Thu, 19 Jun 2025 08:11:00 -0000 https://status.autocalls.ai/incident/605633#c258902ac48428b38752a99d2690ba7da041a1d095b551de0779d52e54cd4a05 Incident Assistants in pipeline mode were not speaking. Fixed in less then 10 minutes. https://status.autocalls.ai/maintenance/548514 Sun, 20 Apr 2025 21:00:10 -0000 https://status.autocalls.ai/incident/548514#ae4f39727a114550155de96dae59c9759f969a0aa136e693382f2e74d932cea3 Maintenance Downtime for few hours while the deploy and migration of old data is being done. After release is done, please expect minor issues which can be reported to our team by live chat. https://status.autocalls.ai/incident/435621 Fri, 27 Sep 2024 08:52:00 -0000 https://status.autocalls.ai/incident/435621#394558de86f4442eb396043d8ca43e1fc207f8c8c0ff7bc0dd11785d49585d90 Incident All services have been fixed.