<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:focsec.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://focsec.instatus.com/history.atom"/>
  <title>Focsec Status - Incident history</title>
  <updated>2025-10-18T06:17:00.000+00:00</updated>
  <author>
    <name>Focsec</name>
  </author>
  
<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cmgvwk9it006q2a6bu37b3yut</id>
  <published>2025-10-18T06:17:00.000+00:00</published>
  <updated>2025-10-18T06:17:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cmgvwk9it006q2a6bu37b3yut"/>
  <title>API errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> API, Account management</p>
    <p><small>Oct <var data-var='date'> 18</var>, <var data-var='time'>06:17:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing a increase in API errors resulting in error 500 and 503\. We are currently investigating this incident..</p>
<p><small>Oct <var data-var='date'> 18</var>, <var data-var='time'>06:22:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. The root cause was a short (&lt; 20 second) internal network outage on our hosting infrastructure. We apologize for any inconvenience caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Maintenance/cmcxw6d7702uxrpxpktw1hx1l</id>
  <published>2025-07-11T07:00:00.000+00:00</published>
  <updated>2025-07-11T07:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/maintenance/cmcxw6d7702uxrpxpktw1hx1l"/>
  <title>Email system upgrade</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 days</p>
    <p><strong>Affected Components:</strong> Billing, invoices and payments, Account management</p>
    <p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Over the next few days, we are upgrading our email configuration to improve deliverability. During this time, emails from Focsec may arrive with a delay or may be flagged as spam. If you are missing any emails, please check for spam folder. API operations are not affected..</p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cmamc9epy0033d64gwe20o64c</id>
  <published>2025-05-13T09:58:03.494+00:00</published>
  <updated>2025-05-13T09:58:03.494+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cmamc9epy0033d64gwe20o64c"/>
  <title>TOR detection and database issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 38 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>09:58:03</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating a issue that prevents detecting TOR IPs and downloading the TOR database. .</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>10:12:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. The cause was a misconfiguration during a update. We apologize for an inconvenience this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cm3yom81c000hwmstbkn9jt8c</id>
  <published>2024-11-26T16:39:14.438+00:00</published>
  <updated>2024-11-26T16:39:14.438+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cm3yom81c000hwmstbkn9jt8c"/>
  <title>API errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>16:39:14</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently seeing a small number of API requests resulting in error 500\. We are currently investigating this incident..</p>
<p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>16:44:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  The problem has been mitigated and users should no longer see any API errors. The error was caused by a faulty application update. We apologize for any inconvenience this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cm3nkmkjo000vic87mnk02isg</id>
  <published>2024-11-18T22:02:04.210+00:00</published>
  <updated>2024-11-18T22:02:04.210+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cm3nkmkjo000vic87mnk02isg"/>
  <title>Temporary API outage </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>22:02:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  A small percentage (&lt;1%) of API requests are resulting in error 502, error 503 or error 504\. We are currently investigating this incident..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>22:04:27</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. The root cause was a temporary network outage on one of our backend nodes. All API endpoints are back to normal now. We apologize for any inconvenience this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cly5vc6v097493hqn5i8fvx2z5</id>
  <published>2024-07-03T13:23:31.547+00:00</published>
  <updated>2024-07-03T13:23:31.547+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cly5vc6v097493hqn5i8fvx2z5"/>
  <title>Wrong API request counts</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>13:23:31</var> GMT+0</small><br /><strong>Investigating</strong> -
  The API request counts in the X-RequestLimit-RequestsMadeToday and X-RequestLimit-RequestsRemainingToday headers are not calculated correctly. As a result, the API request counts returned may be lower than your actual usage.

Your actual API request limits are not affected by this.

We are actively investigating this issue..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>13:38:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. API requests are now being counted correctly again. 

The overall API request count shown for today (2024-07-03) may be slightly lower than your actual usage. Your actual API request limits are not affected by this.

We apologize for any inconvenience this may have caused. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clwix2l34109707baoelxvkxqxa</id>
  <published>2024-05-23T07:13:39.607+00:00</published>
  <updated>2024-05-23T07:13:39.607+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clwix2l34109707baoelxvkxqxa"/>
  <title>Temporary API outage </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> API</p>
    <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>07:13:39</var> GMT+0</small><br /><strong>Investigating</strong> -
  A small number of requests received Error 500 when making API calls. The underlying issue was a misconfiguration on our backend. The estimated downtime was 1 minute..</p>
<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>07:13:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. If you are still seeing errors please contact support@focsec.com.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clw1y0fwr118182blmz1da36epv</id>
  <published>2024-05-11T10:00:00.000+00:00</published>
  <updated>2024-05-11T10:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clw1y0fwr118182blmz1da36epv"/>
  <title>API and account management outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> Account management, API</p>
    <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  You may see network timeouts, error 502 or error 503 on some requests. .</p>
<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>10:04:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  All API and account management systems have been restored. The underlying issue was a fault on one of our cloud nodes. The total partial outage period was &lt;4 minutes. If you are still seeing errors please contact [support@focsec.com](mailto:support@focsec.com) .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clrl1j2dw17411b4ob5730eym3</id>
  <published>2024-01-19T19:35:27.724+00:00</published>
  <updated>2024-01-19T19:35:27.724+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clrl1j2dw17411b4ob5730eym3"/>
  <title>Email deliverability issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 days, 12 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> Account management, Billing, invoices and payments</p>
    <p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>19:35:27</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating email deliverability issues. This may result in emails from Focsec being wrongly flagged as spam.

While we work on resolving this issue, please check your spam box for emails regarding registration, password recovery or support requests..</p>
<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The email delivery issues have been resolved. If continue to see our emails being wrongly flagged as spam, kindly notify us at [support@focsec.com](mailto:support@focsec.com).</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clrjatar320419cloch44ns3mc</id>
  <published>2024-01-18T13:58:00.000+00:00</published>
  <updated>2024-01-18T13:58:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clrjatar320419cloch44ns3mc"/>
  <title>API outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 minutes</p>
    <p><strong>Affected Components:</strong> Account management, API, Billing, invoices and payments</p>
    <p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>13:58:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing a high level of 502 errors being returned and currently investigating this incident..</p>
<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>14:20:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clqmim43r78269b4ohhlicqbba</id>
  <published>2023-12-26T15:41:47.235+00:00</published>
  <updated>2023-12-26T15:41:47.235+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clqmim43r78269b4ohhlicqbba"/>
  <title>API outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Dec <var data-var='date'> 26</var>, <var data-var='time'>15:41:47</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Dec <var data-var='date'> 26</var>, <var data-var='time'>15:46:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident, caused by a internal networking error, has been resolved and all APIs should be working again. We apologize for any inconvenience this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clhyojjf8192354bjoawodqhrfp</id>
  <published>2023-05-22T10:03:37.822+00:00</published>
  <updated>2023-05-22T10:03:37.822+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clhyojjf8192354bjoawodqhrfp"/>
  <title>API returning 500 errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 43 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:03:37</var> GMT+0</small><br /><strong>Investigating</strong> -
  From 2023-05-22 09:50 UTC to approximately 2023-05-22 10:00 UTC there was a small number of API requests receiving HTTP 500 server errors. We are actively investigating the cause..</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:46:34</var> GMT+0</small><br /><strong>Resolved</strong> -
  This problem has been resolved. Only a If you are still receiving any 500 response errors, please contact support@focsec.com.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clhh00iln19265873mzgl5v0gtt</id>
  <published>2023-05-10T01:04:54.632+00:00</published>
  <updated>2023-05-10T01:04:54.632+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clhh00iln19265873mzgl5v0gtt"/>
  <title>Degraded API performance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>May <var data-var='date'> 10</var>, <var data-var='time'>01:04:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing high latency response times on the API. We are actively investigating this issue..</p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>02:06:37</var> GMT+0</small><br /><strong>Identified</strong> -
  This issue has been identified and we are working on a solution. Most API response times are back to normal, but we are still seeing some high latency spikes. Our team is working on additional fixed to fully restore performance. 

We are also seeing a small number of API errors (502) related to this issue..</p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>02:20:42</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are seeing API response times further improving and you should see normal performance on all API endpoints.

We continue to monitor our systems for any latency spikes.

If you are still seeing slow response times, please contact technical support at [support@focsec.com](mailto:support@focsec.com).</p>
<p><small>May <var data-var='date'> 10</var>, <var data-var='time'>13:01:22</var> GMT+0</small><br /><strong>Resolved</strong> -
  This issue has been resolved and API response times are fully back to expected levels. We apologize for any inconvenience this incident may have caused

The high latency was caused a combination of networking issues on our hosting infrastructure and a unusual high number of complex queries being executed in our database. We have provisioned more computing capacity for our database and further improved our auto-scaling capabilities to avoid this issue in the future..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/clbrluxd36813hnoprnbkxfx6</id>
  <published>2022-12-17T00:54:00.000+00:00</published>
  <updated>2022-12-17T06:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/clbrluxd36813hnoprnbkxfx6"/>
  <title>Account management pages unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> Account management</p>
    <p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>06:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue was resolved. If you still have problems accessing internal account pages please contact support@focsec.com.</p>
<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>00:54:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  The account management pages are currently not working. We are investigating this incident. API calls are not affected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Maintenance/cl9t35ng4112018hbobp4v7reje</id>
  <published>2022-11-01T12:00:00.000+00:00</published>
  <updated>2022-11-01T12:03:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/maintenance/cl9t35ng4112018hbobp4v7reje"/>
  <title>Critical security maintenance across all systems</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> API, Account management, Billing, invoices and payments</p>
    <p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>12:03:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  All systems, including the API, will experience a short (&lt;3 minute) downtime on 2022-11-01 at some time between 1300-1900 UTC.

This is for a forthcoming [emergency OpenSSL patch](https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html) expected to be released on the aforementioned date. Unfortunately we are unable to give a exact time frame since this depends on the public release of the OpenSSL team..</p>
<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cl8o20qxh1040iaojt7pr4ry6</id>
  <published>2022-09-30T05:38:06.785+00:00</published>
  <updated>2022-09-30T05:38:06.785+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cl8o20qxh1040iaojt7pr4ry6"/>
  <title>Partial API disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>05:38:06</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing a small number of server side errors (HTTP 502, HTTP 503 responses). We are currently investigating this incident..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>05:41:03</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue was resolved. The increased error rate was caused by a faulty database node. The node was automatically taken out of rotation. Less than 1% of API requests were affected by this API disruption..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cl6xj3tuf38819ijnbkl1lzqte</id>
  <published>2022-08-17T11:26:54.793+00:00</published>
  <updated>2022-08-17T11:26:54.793+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cl6xj3tuf38819ijnbkl1lzqte"/>
  <title>Minor network disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>11:26:54</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our hosting provider has notified us about a minor internal network routing disruption that started at 11:20 UTC and was resolved at 11:24 UTC. You may have seen a small number of requests resulting in a HTTP 500, 502 or 503 status..</p>
<p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>11:37:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue is now resolved. If you continue to experience issues, please email the support team at: support@focsec.com.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cl6lz2ah03152wqn3ptqxzz8l</id>
  <published>2022-08-09T03:18:00.000+00:00</published>
  <updated>2022-08-09T05:18:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cl6lz2ah03152wqn3ptqxzz8l"/>
  <title>API service disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> API, Account management</p>
    <p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>05:18:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>03:18:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing a significant increase in errors on the API and account dashboard. We are currently investigating this incident..</p>
<p><small>Aug <var data-var='date'> 9</var>, <var data-var='time'>09:20:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue was resolved and all services should be up and running again. The underlying issue was a faulty database node behaving in unexpected ways. Our operations team will analyze this issue further to ensure it will not happen again. If you are still experiencing any issues, please reach out to support..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/ckwxlggnl1495198n216b8xh2h</id>
  <published>2021-12-07T13:49:00.000+00:00</published>
  <updated>2021-12-07T13:49:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/ckwxlggnl1495198n216b8xh2h"/>
  <title>Checkout not possible</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Billing, invoices and payments</p>
    <p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>13:49:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  A outage on the side of our payment provider between 15:49 UTC and 00:09 UTC the following day affected the subscription checkout..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/ckwfkqimx214777rofeosx9w9y</id>
  <published>2021-11-24T14:22:00.000+00:00</published>
  <updated>2021-11-24T14:22:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/ckwfkqimx214777rofeosx9w9y"/>
  <title>Account settings can not be updated</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 20 hours</p>
    <p><strong>Affected Components:</strong> Account management</p>
    <p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>14:22:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue has been resolved..</p>
<p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>13:14:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing problems with updating account settings. The issue has been identified..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:focsec.instatus.com,2005:Incident/cku63iv91110481szk2nytivb35</id>
  <published>2021-09-30T13:43:00.000+00:00</published>
  <updated>2021-09-30T16:02:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://focsec.instatus.com/incident/cku63iv91110481szk2nytivb35"/>
  <title>Increased Latency</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 days, 6 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> API</p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>16:02:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue has been resolved..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>13:43:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are seeing increased latency on all API endpoints. We have identified the issue and it should be resolved within the next hours. .</p>

        ]]>
  </content>
</entry>

</feed>