ISMS Copilot Status - Incident history https://isms-copilot.instatus.com ISMS Copilot Tue, 7 Oct 2025 12:30:26 +0000 API provider issue - Answers might have delays Type: Incident Duration: 1 hour and 37 minutes Affected Components: ISMS Copilot Oct 7, 12:30:26 GMT+0 - Investigating - We are currently investigating this incident. In the meantime, use ISMS Copilot v1 for any need. <https://app.ismscopilot.com/dashboard> Oct 7, 13:26:26 GMT+0 - Resolved - This incident has been resolved. Oct 7, 13:58:11 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 7, 14:07:11 GMT+0 - Resolved - This incident has been resolved. From our end everything looks back to normal. Contact support if issues. Type: Incident

Duration: 1 hour and 37 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>12:30:26</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. In the meantime, use ISMS Copilot v1 for any need. <https://app.ismscopilot.com/dashboard>.</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>13:26:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>13:58:11</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>14:07:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. From our end everything looks back to normal. Contact support if issues. .</p> ]]> Tue, 7 Oct 2025 12:30:26 +0000 https://isms-copilot.instatus.com/incident/cmggmk0j200erh23yk9ea87hr https://isms-copilot.instatus.com/incident/cmggmk0j200erh23yk9ea87hr Undue Stripe Charges Due to API incident Type: Incident Duration: 4 hours and 15 minutes Affected Components: ISMS Copilot Sep 3, 18:32:38 GMT+0 - Resolved - We've reviewed API configurations and took measures to make sure this can't occur again. We also removed the payment methods of past customers without active subscriptions to ensure they can't be charged in the future. Sep 3, 12:00:00 GMT+0 - Investigating - An incicent affecting our API, causing Stripe to unexpectedly charge hundreds of current and past customers €163 each. All refunds have been triggered, and the incident is now contained. We are actively investigating how this attack bypassed configuration checks to prevent future occurrences. Our support team is progressively responding to hundreds of customer inquiries. Refunds are expected to process within 5 days, though this may vary depending on individual banks. We are deeply sorry for the inconvenience and are committed to ensuring this does not happen again. Sep 3, 15:32:30 GMT+0 - Monitoring - \* \_Initial Update (1 hour after incident)\_: Identified unauthorized charges of customers via Stripe. Refunds initiated, and investigation into the root cause underway. \* \_Final Update (2 hours after incident)\_: Incident contained, all refunds triggered, and ongoing investigation to strengthen API security. Sep 3, 16:14:58 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 hours and 15 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>18:32:38</var> GMT+0</small><br><strong>Resolved</strong> - We've reviewed API configurations and took measures to make sure this can't occur again. We also removed the payment methods of past customers without active subscriptions to ensure they can't be charged in the future. .</p> <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Investigating</strong> - An incicent affecting our API, causing Stripe to unexpectedly charge hundreds of current and past customers €163 each. All refunds have been triggered, and the incident is now contained. We are actively investigating how this attack bypassed configuration checks to prevent future occurrences. Our support team is progressively responding to hundreds of customer inquiries. Refunds are expected to process within 5 days, though this may vary depending on individual banks. We are deeply sorry for the inconvenience and are committed to ensuring this does not happen again..</p> <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>15:32:30</var> GMT+0</small><br><strong>Monitoring</strong> - \* \_Initial Update (1 hour after incident)\_: Identified unauthorized charges of customers via Stripe. Refunds initiated, and investigation into the root cause underway. \* \_Final Update (2 hours after incident)\_: Incident contained, all refunds triggered, and ongoing investigation to strengthen API security..</p> <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>16:14:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 3 Sep 2025 12:00:00 +0000 https://isms-copilot.instatus.com/incident/cmf46hvs8002e13pidoqyq3v7 https://isms-copilot.instatus.com/incident/cmf46hvs8002e13pidoqyq3v7 ISMS Copilot assistants not issues responding. Type: Incident Duration: 1 hour and 4 minutes Affected Components: ISMS Copilot, ISMS Policy Generator May 26, 15:48:36 GMT+0 - Resolved - This incident has been resolved. One of our AI providers had an outage, which impacted us. We switched to another AI provider and it solved the problem. May 26, 14:44:18 GMT+0 - Investigating - We are currently investigating this incident. All non-EU assistants seem to be affected. In the meantime, you can use ISMS Copilot EU for simpler requests. Support is on it, we'll update you asap. Type: Incident

Duration: 1 hour and 4 minutes

Affected Components: ,

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:48:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. One of our AI providers had an outage, which impacted us. We switched to another AI provider and it solved the problem..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>14:44:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. All non-EU assistants seem to be affected. In the meantime, you can use ISMS Copilot EU for simpler requests. Support is on it, we'll update you asap. .</p> ]]> Mon, 26 May 2025 14:44:18 +0000 https://isms-copilot.instatus.com/incident/cmb5789bk001234geks3c65tl https://isms-copilot.instatus.com/incident/cmb5789bk001234geks3c65tl Unavailability of EU chatbots Type: Incident Duration: 40 minutes Affected Components: ISMS Copilot Apr 9, 13:24:45 GMT+0 - Investigating - We are currently investigating this incident. In the meantime, you can use the default ISMS Copilot assistant that's trained on all main frameworks. Apr 9, 14:04:54 GMT+0 - Resolved - This incident has been resolved. It affected a limited number of users and has been fixed by deleting "moustacheai.com" cookies in the navigator. Please, if affected, reset cookies and you won't experience issues with the EU assistants anymore. Type: Incident

Duration: 40 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>13:24:45</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. In the meantime, you can use the default ISMS Copilot assistant that's trained on all main frameworks. .</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>14:04:54</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. It affected a limited number of users and has been fixed by deleting "moustacheai.com" cookies in the navigator. Please, if affected, reset cookies and you won't experience issues with the EU assistants anymore..</p> ]]> Wed, 9 Apr 2025 13:24:45 +0000 https://isms-copilot.instatus.com/incident/cm99yod79003z13iya8yw03h0 https://isms-copilot.instatus.com/incident/cm99yod79003z13iya8yw03h0 UI bug affecting ISMS Copilot EU Type: Incident Affected Components: ISMS Copilot Feb 13, 15:21:36 GMT+0 - Resolved - We are currently investigating this incident. Signaled to support, investigation going on for a fix. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>15:21:36</var> GMT+0</small><br><strong>Resolved</strong> - We are currently investigating this incident. Signaled to support, investigation going on for a fix..</p> ]]> Thu, 13 Feb 2025 15:21:36 +0000 https://isms-copilot.instatus.com/incident/cm73hn5zm000qqj15f9qweho4 https://isms-copilot.instatus.com/incident/cm73hn5zm000qqj15f9qweho4 Loss of conversation history in user interface. Type: Incident Affected Components: ISMS Copilot Feb 3, 22:13:30 GMT+0 - Resolved - Our AI provider released a new capacity (creating multiple chats) but this removed from your visibility previous chats. We immediately told them doing this without warning us was a bad move, so we're working on a way to prevent this from happening in the future. In the meantime, know that your conversations are not lost, they're just not appearing to you anymore. Reach out to support, let us know what exactly your conversation was about and when it occurred, and we'll retrieve it for you. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>22:13:30</var> GMT+0</small><br><strong>Resolved</strong> - Our AI provider released a new capacity (creating multiple chats) but this removed from your visibility previous chats. We immediately told them doing this without warning us was a bad move, so we're working on a way to prevent this from happening in the future. In the meantime, know that your conversations are not lost, they're just not appearing to you anymore. Reach out to support, let us know what exactly your conversation was about and when it occurred, and we'll retrieve it for you. .</p> ]]> Mon, 3 Feb 2025 22:13:30 +0000 https://isms-copilot.instatus.com/incident/cm6plybmy001bh2vgiqchckw5 https://isms-copilot.instatus.com/incident/cm6plybmy001bh2vgiqchckw5 ISMS Copilot outage Type: Incident Duration: 1 hour and 53 minutes Affected Components: ISMS Copilot Sep 12, 15:15:47 GMT+0 - Investigating - ISMS Copilot cannot be accessed at the moment. This incident was created by an automated monitoring service. Sep 12, 15:17:39 GMT+0 - Resolved - ISMS Copilot is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 hour and 53 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>15:15:47</var> GMT+0</small><br><strong>Investigating</strong> - ISMS Copilot cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Sep <var data-var='date'> 12</var>, <var data-var='time'>15:17:39</var> GMT+0</small><br><strong>Resolved</strong> - ISMS Copilot is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 12 Sep 2024 15:15:47 +0000 https://isms-copilot.instatus.com/incident/cm0zfm0cw00gct2jmewvxv0zd https://isms-copilot.instatus.com/incident/cm0zfm0cw00gct2jmewvxv0zd