Incidents and maintenance reported on status page for VAEV https://status.vaev.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/a86727a52aa29ab3064ec3548a355dc6.png https://status.vaev.ai/ en https://status.vaev.ai/incident/1085817 Fri, 09 Oct 2026 11:28:00 -0000 https://status.vaev.ai/incident/1085817#ddbe0b9e3e524a452920a86052d341bb5c51d6e40e1f9cfa253b5e15367adb1a Incident Between 12:44 and 13:28 today, the platform, published apps and our website were unavailable. The cause was a change on our side, which we have reverted. Everything is working normally again. https://status.vaev.ai/incident/1085817 Fri, 09 Oct 2026 11:13:00 -0000 https://status.vaev.ai/incident/1085817#20698860f5bfb87f8a0c2b4cfe3b1fab07804771c791cb1cbe911cffb5611b21 Incident We have identified the issue and is applying a fix. The issue affects all workspaces and apps. No customer data of code is lost and operation will soon return to normal. Thank you for your patience. Next update will be within the next 30 mins or as event warrants. https://status.vaev.ai/incident/1085817 Fri, 09 Oct 2026 10:48:00 -0000 https://status.vaev.ai/incident/1085817#d0d4bfd1f4c5a92e18023b28ed257946105290216f1710a3024aa9a69e93e048 Incident The platform and our website are currently unavailable for all customers. We have found the cause and are working on a fix. We will post the next update here by 13:15 CEST. https://status.vaev.ai/incident/1068194 Fri, 18 Sep 2026 13:23:00 -0000 https://status.vaev.ai/incident/1068194#d07368230c3b208bb38feb311d0b3d01f169ba5954e698fd16972b2ed016462e Incident Between 15:17 and 15:23 today, published sites returned errors for about six minutes. The cause was a bad deploy on our side, which we have rolled back. Everything is serving normally again, and no data was affected. https://status.vaev.ai/incident/1068194 Fri, 18 Sep 2026 13:21:00 -0000 https://status.vaev.ai/incident/1068194#afdfcf235c1a60a4660eb1910396625693921eb0db684b460f54946ee42b4c40 Incident Our website and some apps are returning errors. We have found the cause and are working on a fix. We will post an update here as soon as it is in place. https://status.vaev.ai/incident/1050618 Fri, 04 Sep 2026 12:40:00 -0000 https://status.vaev.ai/incident/1050618#04a37712bee890828d18f8663c1beb22c8f57251db82cf6d79adb08f8b425456 Incident Email delivery to Outlook.com, Hotmail and Microsoft 365 addresses returned to normal at 14:40 CEST, and the messages that were held up have since been delivered. Sign-in codes are arriving without delay again. Nothing is needed from you. https://status.vaev.ai/incident/1050618 Fri, 04 Sep 2026 10:06:00 -0000 https://status.vaev.ai/incident/1050618#11e6d2b45ae674f74a7215e414a2bb051520ba9916aaade10675d6d8eb94bd1c Incident Sign-in codes and verification emails sent to Outlook.com, Hotmail and Microsoft 365 addresses are arriving up to several minutes late. Microsoft is rate limiting incoming mail today, and this affects many senders, not only VAEV. No emails are lost, and email to other providers is unaffected. If a code has not arrived, requesting a new one is the fastest way in. Our authentication provider has identified the cause and is monitoring delivery. We will update here when delivery times are back to normal. https://status.vaev.ai/incident/1032181 Tue, 25 Aug 2026 10:15:00 -0000 https://status.vaev.ai/incident/1032181#27ad2b735800989f2f2a0b983c026d5be981fe42b175b42ae65f6d45c2a3778f Incident New workspaces are being created normally again. We are monitoring to confirm this is stable. https://status.vaev.ai/incident/1032181 Tue, 25 Aug 2026 08:52:00 -0000 https://status.vaev.ai/incident/1032181#36843768c43ae29b0369b41fd8bed63656aacbdf74bb83eb0524039c8f6b4ab1 Incident Some new workspaces are failing to complete setup. Existing workspaces and their applications are unaffected. We have identified the cause and are working on a fix. https://status.vaev.ai/incident/1030255 Fri, 21 Aug 2026 11:00:00 -0000 https://status.vaev.ai/incident/1030255#ef0c9205ee84a9087d4b9c62ac754a31333e47036d111cadd97d044f84cbc2fb Incident Workspaces was intermittently slow on 20 and 21 August, and some chat sessions needed a reload. Resolved on 21 August at 12:54 CEST.