<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:isms-copilot.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://isms-copilot.instatus.com/history.atom"/>
  <title>ISMS Copilot Status - Incident history</title>
  <updated>2025-10-07T12:30:26.227+00:00</updated>
  <author>
    <name>ISMS Copilot</name>
  </author>
  
<entry>
  <id>tag:isms-copilot.instatus.com,2005:Incident/cmggmk0j200erh23yk9ea87hr</id>
  <published>2025-10-07T12:30:26.227+00:00</published>
  <updated>2025-10-07T14:07:11.601+00:00</updated>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com/incident/cmggmk0j200erh23yk9ea87hr"/>
  <title>API provider issue - Answers might have delays</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 37 minutes</p>
    <p><strong>Affected Components:</strong> ISMS Copilot</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>
<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'>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'>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. &lt;https://app.ismscopilot.com/dashboard&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:isms-copilot.instatus.com,2005:Incident/cmf46hvs8002e13pidoqyq3v7</id>
  <published>2025-09-03T12:00:00.000+00:00</published>
  <updated>2025-09-03T18:32:38.211+00:00</updated>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com/incident/cmf46hvs8002e13pidoqyq3v7"/>
  <title>Undue Stripe Charges Due to API incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> ISMS Copilot</p>
    <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&#039;ve reviewed API configurations and took measures to make sure this can&#039;t occur again. We also removed the payment methods of past customers without active subscriptions to ensure they can&#039;t be charged in the future. .</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>
<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'>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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:isms-copilot.instatus.com,2005:Incident/cmb5789bk001234geks3c65tl</id>
  <published>2025-05-26T14:44:18.691+00:00</published>
  <updated>2025-05-26T15:48:36.429+00:00</updated>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com/incident/cmb5789bk001234geks3c65tl"/>
  <title>ISMS Copilot assistants not issues responding.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 4 minutes</p>
    <p><strong>Affected Components:</strong> ISMS Copilot, ISMS Policy Generator</p>
    <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&#039;ll update you asap. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:isms-copilot.instatus.com,2005:Incident/cm99yod79003z13iya8yw03h0</id>
  <published>2025-04-09T13:24:45.166+00:00</published>
  <updated>2025-04-09T14:04:54.694+00:00</updated>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com/incident/cm99yod79003z13iya8yw03h0"/>
  <title>Unavailability of EU chatbots </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> ISMS Copilot</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 &quot;moustacheai.com&quot; cookies in the navigator. Please, if affected, reset cookies and you won&#039;t experience issues with the EU assistants anymore..</p>
<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&#039;s trained on all main frameworks. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:isms-copilot.instatus.com,2005:Incident/cm73hn5zm000qqj15f9qweho4</id>
  <published>2025-02-13T15:21:36.987+00:00</published>
  <updated>2025-02-13T15:21:36.987+00:00</updated>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com/incident/cm73hn5zm000qqj15f9qweho4"/>
  <title>UI bug affecting ISMS Copilot EU</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> ISMS Copilot</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:isms-copilot.instatus.com,2005:Incident/cm6plybmy001bh2vgiqchckw5</id>
  <published>2025-02-03T22:13:30.862+00:00</published>
  <updated>2025-02-03T22:13:30.862+00:00</updated>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com/incident/cm6plybmy001bh2vgiqchckw5"/>
  <title>Loss of conversation history in user interface.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> ISMS Copilot</p>
    <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&#039;re working on a way to prevent this from happening in the future. 

In the meantime, know that your conversations are not lost, they&#039;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&#039;ll retrieve it for you. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:isms-copilot.instatus.com,2005:Incident/cm0zfm0cw00gct2jmewvxv0zd</id>
  <published>2024-09-12T15:15:47.398+00:00</published>
  <updated>2024-09-12T15:17:39.581+00:00</updated>
  <link rel="alternate" type="text/html" href="https://isms-copilot.instatus.com/incident/cm0zfm0cw00gct2jmewvxv0zd"/>
  <title>ISMS Copilot outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 53 minutes</p>
    <p><strong>Affected Components:</strong> ISMS Copilot</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>
<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>

        ]]>
  </content>
</entry>

</feed>