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 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 Dashboard recovered https://status.open.cx/ Sun, 20 Apr 2025 11:51:30 +0000 https://status.open.cx/#088d39d86375f9c97b6aef8c2dbb4c7f497fc05e7815aba88e38c80cf18f98c6 Dashboard recovered Dashboard went down https://status.open.cx/ Sun, 20 Apr 2025 11:37:28 +0000 https://status.open.cx/#088d39d86375f9c97b6aef8c2dbb4c7f497fc05e7815aba88e38c80cf18f98c6 Dashboard went down [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. [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. [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. 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. 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: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: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. 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. 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: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: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: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: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. 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. 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.