Incidents reported on status page for OpenCX https://status.open.cx/ https://d1lppblt9t2x15.cloudfront.net/logos/84ba2cd415ee701095b42e9f8b43dc97.jpeg https://status.open.cx/ en https://status.open.cx/incident/1058072 Wed, 09 Sep 2026 20:29:51 -0000 https://status.open.cx/incident/1058072#36757d6897aabc751be2df472d411b108f3b928322a317787d3bd95343c3d9df AI Voice recovered. https://status.open.cx/incident/1058072 Wed, 09 Sep 2026 20:25:16 -0000 https://status.open.cx/incident/1058072#056df4d9dfbeea06597c4c6e7ec60b72813d63b2e1e66bde088bad8bcbd77771 AI Voice went down. https://status.open.cx/incident/1057934 Wed, 09 Sep 2026 15:56:00 -0000 https://status.open.cx/incident/1057934#ccacb3a3c4ad19d9cc97c08231fb3fa657278988f143b0035a544b8859a957a3 Dashboard access was restored at 15:56 UTC on September 9, 2026. The disruption lasted 12 minutes. https://status.open.cx/incident/1057934 Wed, 09 Sep 2026 15:44:00 -0000 https://status.open.cx/incident/1057934#276264f0034abc53bc6510608b37f4deb60baed56b672a9d284e79e0fb55370a The dashboard was unavailable starting at 15:44 UTC on September 9, 2026. https://status.open.cx/incident/827986 Wed, 18 Feb 2026 11:52:00 -0000 https://status.open.cx/incident/827986#c77188499afc621a3c7330e6517932a5f280edbf7d760ef537e03b2d75c1701d We are back to normal operation across all of our servers. Our team will continue to monitor the systems closely to ensure continued stability. https://status.open.cx/incident/827986 Wed, 18 Feb 2026 11:50:00 -0000 https://status.open.cx/incident/827986#3f1ca69eb5d541590effc9bcb4a542aab10b57149214e5a171f19c9159bbbb3f We have deployed a potential fix and are seeing full recovery across our EU and North America servers. GCC servers are still recovering. Our team is actively monitoring the situation and will provide further updates shortly. https://status.open.cx/incident/827986 Wed, 18 Feb 2026 11:47:00 -0000 https://status.open.cx/incident/827986#a0b7e02a6142fbc1e6cbecaeea47ea71df10458364c29060f6b659baf1e9da47 We are currently investigating elevated error rates affecting our AI services. Our team is actively working to identify the root cause and will share updates as soon as we have more information. https://status.open.cx/incident/817638 Tue, 03 Feb 2026 14:21:00 -0000 https://status.open.cx/incident/817638#3b8a5e3b0ffe0920db5dd4aeb8f9c06729cc2894ef3918f1e6aee98b66f48d4c We are seeing degraded performance failures to respond to some messages; our team is looking at it at the moment. https://status.open.cx/incident/807415 Mon, 19 Jan 2026 15:01:00 -0000 https://status.open.cx/incident/807415#2c4eb343d1a806514214f9edfdcda5f4e041e2f366ad6d0766f17ea479b1baa9 AI training is not accessible at the moment. We are performing a data migration, and our AI training features may be degraded, including third-party connections. https://status.open.cx/incident/625094 Thu, 24 Jul 2025 10:31:00 -0000 https://status.open.cx/incident/625094#61b76e2ae16f9ef5f3b10a6b7469f2e0aebbd5512413feb945eca3f312fe0896 Our APIs were unavailable due to a faulty database migration. During this time, our AI agents were unable to process any incoming support messages or tickets. Our team is working on adding the necessary mitigations to prevent this from happening in the future. https://status.open.cx/incident/612866 Wed, 02 Jul 2025 06:05:00 -0000 https://status.open.cx/incident/612866#8d5cfc45abb01e69fc610bb96980ddb1c4f0bdf371f21debcf0708dee8ed4dca We previously reported an elevated error rate from OpenAI, which caused some conversations to be handed off due to processing issues with our AI provider, OpenAI. Error rates have now significantly decreased, and operations are back to normal. We will continue to monitor the system closely to ensure ongoing stability. https://status.open.cx/incident/603942 Mon, 16 Jun 2025 14:18:00 -0000 https://status.open.cx/incident/603942#04a2d469198bc33efdbf344f679515e52b06241ee2033f6bfb26ee9d4c4711e6 We are receiving reports that the dashboard is unavailable, and we are pushing a fix. 2/2 https://status.open.cx/incident/542617 Wed, 09 Apr 2025 15:33:00 -0000 https://status.open.cx/incident/542617#f3e10df7f64c8599c6e1a12510171fab7867783fa0946d59e924702faa0d6b83 We are seeing a partial disruption in our Intercom WhatsApp integration; the AI agent might not respond to these messages. https://status.open.cx/incident/523531 Thu, 06 Mar 2025 06:45:00 -0000 https://status.open.cx/incident/523531#66c95c807a34cf83138439106ac7be5bd7fcb741d0efc8f819c8683ca6496259 Migration done successfully. https://status.open.cx/incident/514270 Mon, 17 Feb 2025 06:30:00 -0000 https://status.open.cx/incident/514270#0b6a462534c784f92a7e5056a4188cfc6320f39bac43d91e91fcc9eaa4af45c2 We are investigating a case in which messages sent by the human agent from Zendesk might not appear for the end customer via chat widget and email. https://status.open.cx/incident/505008 Fri, 31 Jan 2025 12:20:00 -0000 https://status.open.cx/incident/505008#1f39a9c94fd752d8aa22b55ee61710fae9b7a240a8cf8e5d772124a113957df8 We are back again. We are closely monitoring the recovered services. https://status.open.cx/incident/505008 Fri, 31 Jan 2025 12:14:00 -0000 https://status.open.cx/incident/505008#6d6eeda9611b8b6c895f3fdaaf42a5615a9bf6f9af0fd9f09c38b2d30c4fb1d8 Our API is down, and the team is looking into it. https://status.open.cx/incident/491917 Tue, 07 Jan 2025 10:49:00 -0000 https://status.open.cx/incident/491917#291f25e29092cd8c321f7c448a8d208ee8328a08c60c967b82c5c8205d072373 We have verified that the fix is working, and the team is now exploring ways to retrieve the messages that were not stored. https://status.open.cx/incident/491917 Tue, 07 Jan 2025 10:44:00 -0000 https://status.open.cx/incident/491917#a9260db60bdf056cd1f6e36076dad6418c6b03066b0d96b9fb9b377e0e4686f2 We have deployed a fix and are currently monitoring the situation. https://status.open.cx/incident/491917 Tue, 07 Jan 2025 10:33:31 -0000 https://status.open.cx/incident/491917#d365d1a9968721bdd7df348cfde731257aabe1a93feb2e2faa430afdb43a7099 We have identified an issue where some messages may fail to store correctly due to a malfunctioning code release. However, this does not affect end users. The impact is limited to the human agent side when they pick up tickets. the team Is working on it.