Incidents | OpenCX Incidents reported on status page for OpenCX https://status.open.cx/ https://d1lppblt9t2x15.cloudfront.net/logos/84ba2cd415ee701095b42e9f8b43dc97.jpeg Incidents | OpenCX https://status.open.cx/ en AI Agent recovered https://status.open.cx/ Tue, 09 Sep 2025 08:43:56 +0000 https://status.open.cx/#85c57c7ef939af476fd8facc427daa0aae44a472d651fc039718c9143b305d7a AI Agent recovered AI Agent went down https://status.open.cx/ Tue, 09 Sep 2025 08:42:04 +0000 https://status.open.cx/#85c57c7ef939af476fd8facc427daa0aae44a472d651fc039718c9143b305d7a AI Agent went down Dashboard recovered https://status.open.cx/ Wed, 03 Sep 2025 19:11:32 +0000 https://status.open.cx/#d2fd858bfb6ea17e0e0ef69c5522cb0acd34a0dcf1ce08e9060e973cda710851 Dashboard recovered Dashboard went down https://status.open.cx/ Wed, 03 Sep 2025 19:10:23 +0000 https://status.open.cx/#d2fd858bfb6ea17e0e0ef69c5522cb0acd34a0dcf1ce08e9060e973cda710851 Dashboard went down AI Agent recovered https://status.open.cx/ Sun, 31 Aug 2025 12:55:07 +0000 https://status.open.cx/#c3601ae1bc7af0420a628f7057d3a24f7fb70ab1ef49945a080cf2639b7c77cc AI Agent recovered AI Agent went down https://status.open.cx/ Sun, 31 Aug 2025 12:54:42 +0000 https://status.open.cx/#c3601ae1bc7af0420a628f7057d3a24f7fb70ab1ef49945a080cf2639b7c77cc AI Agent went down AI Agent recovered https://status.open.cx/ Fri, 29 Aug 2025 22:13:21 +0000 https://status.open.cx/#5f451b4d0ff855af3fbd5fd4c1ddbda445131a85da590e05bf61f18eb2ab450f AI Agent recovered AI Agent went down https://status.open.cx/ Fri, 29 Aug 2025 22:04:08 +0000 https://status.open.cx/#5f451b4d0ff855af3fbd5fd4c1ddbda445131a85da590e05bf61f18eb2ab450f AI Agent went down AI Agent recovered https://status.open.cx/ Thu, 28 Aug 2025 14:55:26 +0000 https://status.open.cx/#93d730eeaaec6943f08c0f11302e11699e85c22545b2b13a647aae2687a711c7 AI Agent recovered AI Agent went down https://status.open.cx/ Thu, 28 Aug 2025 14:52:20 +0000 https://status.open.cx/#93d730eeaaec6943f08c0f11302e11699e85c22545b2b13a647aae2687a711c7 AI Agent went down AI Agent recovered https://status.open.cx/ Wed, 27 Aug 2025 10:20:35 +0000 https://status.open.cx/#ff69ad85e31ce723b3e9e3ffa40edd9a91b772ec9e0863658c0d56a26c4e416b AI Agent recovered AI Agent went down https://status.open.cx/ Wed, 27 Aug 2025 10:12:19 +0000 https://status.open.cx/#ff69ad85e31ce723b3e9e3ffa40edd9a91b772ec9e0863658c0d56a26c4e416b AI Agent went down AI Agent recovered https://status.open.cx/ Wed, 13 Aug 2025 11:43:13 +0000 https://status.open.cx/#81c664da19ec615d4624b96e876571299c1750aab42f662223b864be39b146ae AI Agent recovered AI Agent went down https://status.open.cx/ Wed, 13 Aug 2025 11:32:13 +0000 https://status.open.cx/#81c664da19ec615d4624b96e876571299c1750aab42f662223b864be39b146ae AI Agent went down Our APIs were unavailable 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. Our APIs were unavailable 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. Our APIs were unavailable 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. AI Agent recovered https://status.open.cx/ Thu, 24 Jul 2025 10:26:33 +0000 https://status.open.cx/#521bcb295374449f9ce63772c31d528574abb4a6fd4a67afb56e2ba923a862e4 AI Agent recovered Public APIs recovered https://status.open.cx/ Thu, 24 Jul 2025 10:26:10 +0000 https://status.open.cx/#f1c5c68243a045bdd01ba8eee7c1789bf72cfc82c59c6563f4a995189ac55009 Public APIs recovered Internal APIs recovered https://status.open.cx/ Thu, 24 Jul 2025 10:26:10 +0000 https://status.open.cx/#f1c5c68243a045bdd01ba8eee7c1789bf72cfc82c59c6563f4a995189ac55009 Internal APIs recovered AI Agent went down https://status.open.cx/ Thu, 24 Jul 2025 10:05:24 +0000 https://status.open.cx/#521bcb295374449f9ce63772c31d528574abb4a6fd4a67afb56e2ba923a862e4 AI Agent went down Public APIs went down https://status.open.cx/ Thu, 24 Jul 2025 10:04:54 +0000 https://status.open.cx/#f1c5c68243a045bdd01ba8eee7c1789bf72cfc82c59c6563f4a995189ac55009 Public APIs went down Internal APIs went down https://status.open.cx/ Thu, 24 Jul 2025 10:04:54 +0000 https://status.open.cx/#f1c5c68243a045bdd01ba8eee7c1789bf72cfc82c59c6563f4a995189ac55009 Internal APIs went down Elevated OpenAI errors 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. Elevated OpenAI errors 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. The dashboard is unavailable. 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 [Intercom & WhatsApp] Partial service disruption 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. The dashboard might not be available for some users. https://status.open.cx/incident/523531 Thu, 06 Mar 2025 06:45:00 -0000 https://status.open.cx/incident/523531#66c95c807a34cf83138439106ac7be5bd7fcb741d0efc8f819c8683ca6496259 Migration done successfully. Zendesk Messages 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. The API is down 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. The API is down 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. Some user messages might not get stored 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. Some user messages might not get 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. Some user messages might not get stored 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.