<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Instatus Status - Incident history</title>
    <link>https://instat.us</link>
    <description>Instatus</description>
    <pubDate>Fri, 5 Dec 2025 08:48:00 +0000</pubDate>
    
<item>
  <title>Issues with login to our private pages and dashboard</title>
  <description>
    Type: Incident
    Duration: 24 minutes

    Affected Components: Private status pages, Dashboard
    Dec 5, 08:48:00 GMT+0 - Investigating - We faced issues affecting our private pages and dashboard logins caused by a [Cloudflare incident.](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) Dec 5, 09:12:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 24 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:48:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We faced issues affecting our private pages and dashboard logins caused by a [Cloudflare incident.](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:12:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 5 Dec 2025 08:48:00 +0000</pubDate>
  <link>https://instat.us/incident/cmiszy2uv0cnw11ttp2znawe8</link>
  <guid>https://instat.us/incident/cmiszy2uv0cnw11ttp2znawe8</guid>
</item>

<item>
  <title>Issues accessing our dashboard and private status pages</title>
  <description>
    Type: Incident
    Duration: 1 hour and 46 minutes

    Affected Components: Incident response, On-call, Slack app, API, Discord, Public status pages, RSS &amp; Atom, Webhooks, Email, Public status pages, Slack, Microsoft Teams, SMS, Dashboard, Maintenance Automations, Google Chat, Private status pages, Uptime monitoring
    Nov 18, 12:00:00 GMT+0 - Identified - There&#039;s an outage in Cloudflare that resulted in a major outage to our API and dashboard.  Nov 18, 13:46:23 GMT+0 - Resolved - We re-routed from Cloudflare, and now our services should be accessible.

We&#039;ll make sure we have a quicker system of re-routing in the future. Sorry for the outage! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 46 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  There&#039;s an outage in Cloudflare that resulted in a major outage to our API and dashboard. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:46:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We re-routed from Cloudflare, and now our services should be accessible.

We&#039;ll make sure we have a quicker system of re-routing in the future. Sorry for the outage!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 12:00:00 +0000</pubDate>
  <link>https://instat.us/incident/cmi4npx040016hqzhau7rscip</link>
  <guid>https://instat.us/incident/cmi4npx040016hqzhau7rscip</guid>
</item>

<item>
  <title>Switching our AWS region</title>
  <description>
    Type: Maintenance
    Duration: 13 minutes

    Affected Components: Incident response, Slack, On-call, API, Webhooks, Email, Microsoft Teams, Discord, SMS, RSS &amp; Atom, Dashboard, Maintenance Automations, Google Chat, Private status pages, Uptime monitoring, , 
Notifications →
    Oct 25, 15:12:48 GMT+0 - Completed - Maintenance has completed successfully. Oct 25, 15:00:00 GMT+0 - Identified - We&#039;ll switch our backend and API location to us-east-2 because it&#039;s usually more stable. 

We expect a 10 minute downtime that will affect our dashboard and API. 

Public status pages will continue to be available for your users. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:12:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ll switch our backend and API location to us-east-2 because it&#039;s usually more stable. 

We expect a 10 minute downtime that will affect our dashboard and API. 

Public status pages will continue to be available for your users..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 25 Oct 2025 15:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/cmh3hskw9000hkjter7ww42vl</link>
  <guid>https://instat.us/maintenance/cmh3hskw9000hkjter7ww42vl</guid>
</item>

<item>
  <title>Outages with some of our services</title>
  <description>
    Type: Incident
    Duration: 2 hours

    Affected Components: Incident response, Private status pages, Maintenance Automations
    Oct 20, 07:35:00 GMT+0 - Identified - We faced issues with some of our services, including scheduled maintenance periods, private status pages, and adding incidents for some customes. This was caused by outages to our providers including AWS and Vercel. Oct 20, 09:35:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We faced issues with some of our services, including scheduled maintenance periods, private status pages, and adding incidents for some customes. This was caused by outages to our providers including AWS and Vercel..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 20 Oct 2025 07:35:00 +0000</pubDate>
  <link>https://instat.us/incident/cmgz3lvoe014sap0lxn7eorbg</link>
  <guid>https://instat.us/incident/cmgz3lvoe014sap0lxn7eorbg</guid>
</item>

<item>
  <title>Unavailable RSS &amp; JSON endpoints</title>
  <description>
    Type: Incident
    Duration: 1 hour and 14 minutes

    Affected Components: API, RSS &amp; Atom
    Oct 5, 17:32:27 GMT+0 - Investigating - Public endpoints like /rss, /atom, /components.json, etc are unavailable due to a faulty release.

We&#039;re currently fixing it and we will update you. Oct 5, 18:46:13 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 14 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:32:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Public endpoints like /rss, /atom, /components.json, etc are unavailable due to a faulty release.

We&#039;re currently fixing it and we will update you..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:46:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 5 Oct 2025 17:32:27 +0000</pubDate>
  <link>https://instat.us/incident/cmgdzcbit00b92mhm3a88mbjh</link>
  <guid>https://instat.us/incident/cmgdzcbit00b92mhm3a88mbjh</guid>
</item>

<item>
  <title>Data migration</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 6 minutes

    Affected Components: Public status pages, Incident response, Slack, Public status pages, Slack app, On-call, Private status pages, API, Maintenance Automations, Webhooks, Email, Microsoft Teams, Discord, SMS, Google Chat, RSS &amp; Atom, Dashboard, Uptime monitoring
    Oct 5, 17:06:06 GMT+0 - Completed - Maintenance has completed successfully. Oct 5, 16:00:00 GMT+0 - Identified - We&#039;ll be having a data migration in order to improve our performance.

We expect no downtime, but we&#039;re scheduling this maintenance just in case. Oct 5, 16:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 6 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:06:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ll be having a data migration in order to improve our performance.

We expect no downtime, but we&#039;re scheduling this maintenance just in case..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 5 Oct 2025 16:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/cmgduootl059qe02dwac2qfpd</link>
  <guid>https://instat.us/maintenance/cmgduootl059qe02dwac2qfpd</guid>
</item>

<item>
  <title>Data migration</title>
  <description>
    Type: Maintenance
    Duration: 1 minute

    Affected Components: Public status pages, Incident response, Slack, Public status pages, Slack app, On-call, Private status pages, Dashboard, API, Maintenance Automations, Webhooks, Email, Microsoft Teams, Discord, RSS &amp; Atom, SMS, Google Chat, Uptime monitoring
    Oct 4, 19:00:00 GMT+0 - Identified - We&#039;ll be having a data migration in order to improve our performance. 

We expect no downtime, but we&#039;re scheduling this maintenance just in case. Oct 4, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 4, 19:01:25 GMT+0 - Completed - We&#039;ll postpone the migration to Sunday once we&#039;re fully ready. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ll be having a data migration in order to improve our performance. 

We expect no downtime, but we&#039;re scheduling this maintenance just in case..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:01:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  We&#039;ll postpone the migration to Sunday once we&#039;re fully ready..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 4 Oct 2025 19:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/cmgc9kytg0075mfmzwhntcw9r</link>
  <guid>https://instat.us/maintenance/cmgc9kytg0075mfmzwhntcw9r</guid>
</item>

<item>
  <title>Incorrect degraded checks</title>
  <description>
    Type: Incident
    Duration: 1 hour and 10 minutes

    Affected Components: Uptime monitoring
    Aug 10, 14:20:00 GMT+0 - Resolved - Issue is now fixed. We removed the incorrect records added during the incident. Aug 10, 13:10:00 GMT+0 - Identified - We had a buggy release that resulted in checks incorrectly marked as degraded 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue is now fixed. We removed the incorrect records added during the incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We had a buggy release that resulted in checks incorrectly marked as degraded.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 10 Aug 2025 13:10:00 +0000</pubDate>
  <link>https://instat.us/incident/cme5tn6ez000dxp1apv9d22zs</link>
  <guid>https://instat.us/incident/cme5tn6ez000dxp1apv9d22zs</guid>
</item>

<item>
  <title>Some issues with SSO auth and Directory Sync</title>
  <description>
    Type: Incident
    Duration: 49 minutes

    Affected Components: Private status pages, Dashboard
    Jun 12, 20:03:00 GMT+0 - Resolved - The issue is now resolved by them applying a fix that mitigated their upstream outage.

Please feel free to continue monitoring [their incident](https://status.workos.com/). Jun 12, 19:13:40 GMT+0 - Identified - There&#039;s a current issue with our upstream provider, WorkOS. Here&#039;s their [incident report.](https://status.workos.com/incidents/k9s870cktcsf)

We use it for login via SSO as well as Directory Sync. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 49 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:03:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue is now resolved by them applying a fix that mitigated their upstream outage.

Please feel free to continue monitoring [their incident](https://status.workos.com/)..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:13:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  There&#039;s a current issue with our upstream provider, WorkOS. Here&#039;s their [incident report.](https://status.workos.com/incidents/k9s870cktcsf)

We use it for login via SSO as well as Directory Sync..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 12 Jun 2025 19:13:40 +0000</pubDate>
  <link>https://instat.us/incident/cmbtrbj9a0064k408lacbqeid</link>
  <guid>https://instat.us/incident/cmbtrbj9a0064k408lacbqeid</guid>
</item>

<item>
  <title>Outage affecting dashboard and API</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Public status pages, Private status pages, Dashboard, Maintenance Automations, Discord, Google Chat, Slack, Webhooks, SMS, RSS &amp; Atom, Microsoft Teams, Email, API
    Apr 29, 17:25:00 GMT+0 - Resolved - Sorry for the trouble. Issue is now resolved!  Apr 29, 17:15:00 GMT+0 - Identified - We had an issue affecting your ability to update your status pages via the dashboard or API. Private pages were also affected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:25:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Sorry for the trouble. Issue is now resolved! .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We had an issue affecting your ability to update your status pages via the dashboard or API. Private pages were also affected..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 29 Apr 2025 17:15:00 +0000</pubDate>
  <link>https://instat.us/incident/cma2scjq10002nhh0xf82wonk</link>
  <guid>https://instat.us/incident/cma2scjq10002nhh0xf82wonk</guid>
</item>

<item>
  <title>Data migration (2)</title>
  <description>
    Type: Maintenance
    Duration: 10 minutes

    Affected Components: Public status pages, Private status pages, Dashboard, Maintenance Automations, Discord, Google Chat, Slack, Webhooks, SMS, RSS &amp; Atom, Microsoft Teams, Email, API
    Apr 20, 21:00:00 GMT+0 - Identified - We&#039;re planning a data migration during the weekend. 

Status pages will continue to be accessible, but you won&#039;t be able to do updates during the migration. Apr 20, 21:10:00 GMT+0 - Completed - Maintenance is now complete! Apr 20, 21:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re planning a data migration during the weekend. 

Status pages will continue to be accessible, but you won&#039;t be able to do updates during the migration..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance is now complete!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 20 Apr 2025 21:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/cm9pqbdu800422qx1hppv4yta</link>
  <guid>https://instat.us/maintenance/cm9pqbdu800422qx1hppv4yta</guid>
</item>

<item>
  <title>Planned data migration</title>
  <description>
    Type: Maintenance
    Duration: 29 minutes

    Affected Components: Public status pages, Private status pages, Dashboard, API, Maintenance Automations, Discord, Google Chat, Slack, Webhooks, SMS, RSS &amp; Atom, Microsoft Teams, Email
    Apr 19, 21:28:37 GMT+0 - Completed - Maintenance is completed successfully. Thank you for your patience! Apr 19, 21:00:00 GMT+0 - Identified - We&#039;re doing an update during the weekend that requires data migration. 

We expect a downtime of 10 minutes on updates only. 

Status pages will continue to be available, but you won&#039;t be able to update them until maintenance ends. Apr 19, 21:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:28:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance is completed successfully. Thank you for your patience!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re doing an update during the weekend that requires data migration. 

We expect a downtime of 10 minutes on updates only. 

Status pages will continue to be available, but you won&#039;t be able to update them until maintenance ends..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 19 Apr 2025 21:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/cm9lrmfo00002pnrz08k1i99v</link>
  <guid>https://instat.us/maintenance/cm9lrmfo00002pnrz08k1i99v</guid>
</item>

<item>
  <title>Dashboard not available</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Dashboard
    Mar 3, 15:30:00 GMT+0 - Resolved - It&#039;s now been resolved. Was due to a project transfer that went wrong. Mar 3, 15:20:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  It&#039;s now been resolved. Was due to a project transfer that went wrong..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 3 Mar 2025 15:20:00 +0000</pubDate>
  <link>https://instat.us/incident/cm7uo4y8g003elusf24kkm759</link>
  <guid>https://instat.us/incident/cm7uo4y8g003elusf24kkm759</guid>
</item>

<item>
  <title>Issue with accessing subdomains of public pages</title>
  <description>
    Type: Incident
    Duration: 14 minutes

    Affected Components: Public status pages
    Nov 10, 18:09:00 GMT+0 - Resolved - Issue should be fixed now. It was caused by faulty transfer of project on our frontend provider. Nov 10, 17:55:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:09:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue should be fixed now. It was caused by faulty transfer of project on our frontend provider..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 10 Nov 2024 17:55:00 +0000</pubDate>
  <link>https://instat.us/incident/cm3bwxnqi00574jsigoz6iosu</link>
  <guid>https://instat.us/incident/cm3bwxnqi00574jsigoz6iosu</guid>
</item>

<item>
  <title>Issues accessing the dashboard</title>
  <description>
    Type: Incident
    Duration: 15 minutes

    Affected Components: Dashboard
    Sep 26, 15:40:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 26, 15:55:00 GMT+0 - Resolved - The issue has been resolved! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been resolved!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Sep 2024 15:40:00 +0000</pubDate>
  <link>https://instat.us/incident/cm1jhth7200i16r0cbhv726lu</link>
  <guid>https://instat.us/incident/cm1jhth7200i16r0cbhv726lu</guid>
</item>

<item>
  <title>Status pages unavailable</title>
  <description>
    Type: Incident
    Duration: 27 minutes

    Affected Components: Public status pages, Private status pages
    Aug 7, 19:24:00 GMT+0 - Resolved - Everything should be working now! Aug 7, 19:54:03 GMT+0 - Postmortem - Seems like all services are back to normal. 

Here&#039;s our provider&#039;s [incident. ](https://www.vercel-status.com/incidents/f6b2blrl5f5f)We&#039;re sorry for the downtime.

In the upcoming days, we&#039;ll investigate alternatives that we can switch to in case this happens in the future. Aug 7, 19:29:00 GMT+0 - Monitoring - Services became unavailable again Aug 7, 19:43:00 GMT+0 - Resolved - Issue was resolved again Aug 7, 19:18:00 GMT+0 - Monitoring - All our components were unavailable due to an outage with our frontend hosting provider. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:24:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Everything should be working now!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:54:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  Seems like all services are back to normal. 

Here&#039;s our provider&#039;s [incident. ](https://www.vercel-status.com/incidents/f6b2blrl5f5f)We&#039;re sorry for the downtime.

In the upcoming days, we&#039;ll investigate alternatives that we can switch to in case this happens in the future..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:29:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Services became unavailable again.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:43:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue was resolved again.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:18:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  All our components were unavailable due to an outage with our frontend hosting provider..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 7 Aug 2024 19:18:00 +0000</pubDate>
  <link>https://instat.us/incident/clzk8s4kf569466hioom9a38k00</link>
  <guid>https://instat.us/incident/clzk8s4kf569466hioom9a38k00</guid>
</item>

<item>
  <title>Issues with new logins to dashboard and private pages</title>
  <description>
    Type: Incident
    Duration: 1 hour and 30 minutes

    Affected Components: Dashboard, Private status pages
    Jul 16, 07:00:00 GMT+0 - Resolved - Issue is now resolved Jul 16, 05:30:00 GMT+0 - Monitoring - We did a faulty release that resulted in problems with new logins to Instatus dashboard as well as status pages. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue is now resolved.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We did a faulty release that resulted in problems with new logins to Instatus dashboard as well as status pages..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 16 Jul 2024 05:30:00 +0000</pubDate>
  <link>https://instat.us/incident/clyp2qqk81685oioqe7r0cayp</link>
  <guid>https://instat.us/incident/clyp2qqk81685oioqe7r0cayp</guid>
</item>

<item>
  <title>Many private pages returning 404</title>
  <description>
    Type: Incident
    Duration: 1 hour and 55 minutes

    Affected Components: Private status pages
    Jun 26, 05:15:00 GMT+0 - Investigating - We had an issue were many private pages were returning 404 Not found page Jun 26, 07:10:00 GMT+0 - Resolved - This was resolved earlier. This likely happened because of our frontend hosting provider. We&#039;re still investigating it with them. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 55 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We had an issue were many private pages were returning 404 Not found page.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This was resolved earlier. This likely happened because of our frontend hosting provider. We&#039;re still investigating it with them..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 26 Jun 2024 05:15:00 +0000</pubDate>
  <link>https://instat.us/incident/clxw5qdsa119707b1ofd4bsj47v</link>
  <guid>https://instat.us/incident/clxw5qdsa119707b1ofd4bsj47v</guid>
</item>

<item>
  <title>Issue with SSL certificates</title>
  <description>
    Type: Incident
    Duration: 29 minutes

    Affected Components: Public status pages, Private status pages
    Mar 31, 05:21:03 GMT+0 - Monitoring - The fix caused a temporary issue with custom domains, but we managed to solve it within a few minutes Mar 31, 05:30:12 GMT+0 - Resolved - Issue is now resolved!

We&#039;ll follow up with a post-mortem later in the day. Mar 31, 05:07:42 GMT+0 - Monitoring - We just fixed the issue temporarily via creating certificates from Cloudflare. Mar 31, 05:01:28 GMT+0 - Investigating - Status pages using a subdomain are currently facing an issue with SSL certificates.

We&#039;re currently working on fixing the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:21:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The fix caused a temporary issue with custom domains, but we managed to solve it within a few minutes.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:30:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue is now resolved!

We&#039;ll follow up with a post-mortem later in the day..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:07:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We just fixed the issue temporarily via creating certificates from Cloudflare..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:01:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Status pages using a subdomain are currently facing an issue with SSL certificates.

We&#039;re currently working on fixing the issue..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 31 Mar 2024 05:01:28 +0000</pubDate>
  <link>https://instat.us/incident/cluf20j1c42867kslnlooxj6te</link>
  <guid>https://instat.us/incident/cluf20j1c42867kslnlooxj6te</guid>
</item>

<item>
  <title>Issues updating status pages using the API</title>
  <description>
    Type: Incident
    Duration: 1 hour and 13 minutes

    Affected Components: API
    Mar 13, 22:06:11 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 13, 22:23:20 GMT+0 - Identified - We&#039;re still working on fixing the issue.

The issue caused by new encryption and migration of API keys. Mar 13, 22:54:01 GMT+0 - Identified - We&#039;re in the process of releasing a fix for all user accounts.

This is still in progress, so depending on your account, you maybe fixed or not. Mar 13, 23:19:09 GMT+0 - Resolved - Issue is fixed now! We&#039;re sorry for the long duration! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:06:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:23:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re still working on fixing the issue.

The issue caused by new encryption and migration of API keys..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:54:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re in the process of releasing a fix for all user accounts.

This is still in progress, so depending on your account, you maybe fixed or not..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:19:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue is fixed now! We&#039;re sorry for the long duration!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 13 Mar 2024 22:06:11 +0000</pubDate>
  <link>https://instat.us/incident/cltqcozc912852z2n5lq48brw2</link>
  <guid>https://instat.us/incident/cltqcozc912852z2n5lq48brw2</guid>
</item>

<item>
  <title>Issues with creating and updating incidents</title>
  <description>
    Type: Incident
    Duration: 25 minutes

    Affected Components: API, Dashboard
    Feb 23, 19:30:00 GMT+0 - Resolved - We had issues creating and updating incidents due to a release that had bugs.

We rolled back these changes. Incident creation should be working normally now. Feb 23, 19:05:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We had issues creating and updating incidents due to a release that had bugs.

We rolled back these changes. Incident creation should be working normally now..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 23 Feb 2024 19:05:00 +0000</pubDate>
  <link>https://instat.us/incident/clsz1p0uy13590k8ohswcq43l0</link>
  <guid>https://instat.us/incident/clsz1p0uy13590k8ohswcq43l0</guid>
</item>

<item>
  <title>Incorrect validation emails</title>
  <description>
    Type: Incident
    Duration: 51 minutes

    Affected Components: Dashboard, Email
    Feb 20, 10:05:15 GMT+0 - Identified - Our system sent incorrect custom domain validation emails.

If it&#039;s the first alert you get for a while, then your domain is correctly configured.

The false alarms and incorrect domain status on your dashboard seems to be caused by an incorrect CAA validation by our provider (Vercel)

We&#039;re still investigating the issue, and opened a support case with them. 

But rest assured, your domains are correctly configured and there won&#039;t be any disruptions. Feb 20, 10:56:01 GMT+0 - Resolved - The issue is now resolved. Your custom domain setup on your dashboard should look ok.

Vercel informed us that they rolled back a recent change they did, which should fix the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 51 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:05:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our system sent incorrect custom domain validation emails.

If it&#039;s the first alert you get for a while, then your domain is correctly configured.

The false alarms and incorrect domain status on your dashboard seems to be caused by an incorrect CAA validation by our provider (Vercel)

We&#039;re still investigating the issue, and opened a support case with them. 

But rest assured, your domains are correctly configured and there won&#039;t be any disruptions..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:56:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue is now resolved. Your custom domain setup on your dashboard should look ok.

Vercel informed us that they rolled back a recent change they did, which should fix the issue..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 20 Feb 2024 10:05:15 +0000</pubDate>
  <link>https://instat.us/incident/clsu7948i54182c0osxxerdolh</link>
  <guid>https://instat.us/incident/clsu7948i54182c0osxxerdolh</guid>
</item>

<item>
  <title>Inaccessible status pages</title>
  <description>
    Type: Incident
    Duration: 1 day and 5 hours

    Affected Components: Public status pages
    Jan 2, 21:14:00 GMT+0 - Resolved - Issue is now fixed! Jan 2, 20:45:00 GMT+0 - Identified - We had an issue that showed a 404 error for public status pages 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 5 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:14:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue is now fixed!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We had an issue that showed a 404 error for public status pages.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 2 Jan 2024 20:45:00 +0000</pubDate>
  <link>https://instat.us/incident/clqwxqkpz19833broj80g386af</link>
  <guid>https://instat.us/incident/clqwxqkpz19833broj80g386af</guid>
</item>

<item>
  <title>Issues with email login and updates</title>
  <description>
    Type: Incident
    Duration: 12 hours and 1 minute

    Affected Components: Dashboard, Email, Private status pages
    Dec 21, 00:20:00 GMT+0 - Identified - We had issues with sending emails for some parts of the system, including login and some incident updates. Dec 21, 12:20:39 GMT+0 - Resolved - We had issues with sending emails for some parts of the system, including login and some incident updates. The issue should be resolved now! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We had issues with sending emails for some parts of the system, including login and some incident updates..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:20:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We had issues with sending emails for some parts of the system, including login and some incident updates. The issue should be resolved now!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 Dec 2023 00:20:00 +0000</pubDate>
  <link>https://instat.us/incident/clqf66s355799b8n4e2j1junr</link>
  <guid>https://instat.us/incident/clqf66s355799b8n4e2j1junr</guid>
</item>

<item>
  <title>Difficulties logging in to the dashboard</title>
  <description>
    Type: Incident
    Duration: 45 minutes

    Affected Components: Dashboard
    Oct 10, 00:50:00 GMT+0 - Identified - Issues with new logins to the dashboard. Oct 10, 01:35:00 GMT+0 - Resolved - Issue is now resolved! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Issues with new logins to the dashboard..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue is now resolved!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 10 Oct 2023 00:50:00 +0000</pubDate>
  <link>https://instat.us/incident/clnjnwj3a1676bgob4s06wrtv</link>
  <guid>https://instat.us/incident/clnjnwj3a1676bgob4s06wrtv</guid>
</item>

<item>
  <title>Issue with adding new custom domains</title>
  <description>
    Type: Incident
    Duration: 3 hours and 1 minute

    Affected Components: Dashboard
    Sep 21, 19:30:00 GMT+0 - Identified - We&#039;re facing an issue where newly added custom domains won&#039;t be correctly setup.
We&#039;ll make sure to correctly setup your custom domains for you once the incident is resolved. Sep 21, 22:31:15 GMT+0 - Resolved - Issue is now resolved! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re facing an issue where newly added custom domains won&#039;t be correctly setup.
We&#039;ll make sure to correctly setup your custom domains for you once the incident is resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:31:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue is now resolved!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 Sep 2023 19:30:00 +0000</pubDate>
  <link>https://instat.us/incident/clmtlf2fx4293bpoo0myhfxz3</link>
  <guid>https://instat.us/incident/clmtlf2fx4293bpoo0myhfxz3</guid>
</item>

<item>
  <title>Issues accessing the dashboard and API</title>
  <description>
    Type: Incident
    Duration: 1 hour and 13 minutes

    Affected Components: Dashboard, API, Discord, Slack, Webhooks, SMS, RSS &amp; Atom, Maintenance Automations, Email, Microsoft Teams
    Aug 24, 16:40:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 24, 17:52:40 GMT+0 - Resolved - There was a downtime with dashboard and API. It was caused by a Redis configuration issue. We fixed the issue now! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 13 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:52:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  There was a downtime with dashboard and API. It was caused by a Redis configuration issue. We fixed the issue now!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 24 Aug 2023 16:40:00 +0000</pubDate>
  <link>https://instat.us/incident/cllpgmzpy9869c1o9h7276bkd</link>
  <guid>https://instat.us/incident/cllpgmzpy9869c1o9h7276bkd</guid>
</item>

<item>
  <title>Database Migration (2)</title>
  <description>
    Type: Maintenance
    Duration: 23 minutes

    Affected Components: Dashboard, API, Discord, Slack, Webhooks, SMS, RSS &amp; Atom, Maintenance Automations, Email, Private status pages, Microsoft Teams
    Jul 17, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 17, 01:22:54 GMT+0 - Completed - Maintenance is complete! Jul 17, 01:00:00 GMT+0 - Identified - We&#039;re changing our database structure to allow for new features.

We&#039;re aiming for 10-mins of downtime, but the maintenance window is 1-hour just in case.
The maintenance window is outside working hours, in a weekend.

Your public status pages will remain available for visitors. You won&#039;t be able to update them during the maintenance period, though. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:22:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance is complete!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re changing our database structure to allow for new features.

We&#039;re aiming for 10-mins of downtime, but the maintenance window is 1-hour just in case.
The maintenance window is outside working hours, in a weekend.

Your public status pages will remain available for visitors. You won&#039;t be able to update them during the maintenance period, though..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 17 Jul 2023 01:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/clk5mzzg0137150o1ofgdmuakwe</link>
  <guid>https://instat.us/maintenance/clk5mzzg0137150o1ofgdmuakwe</guid>
</item>

<item>
  <title>Database Migration</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 5 minutes

    Affected Components: Dashboard, API, Discord, Slack, Webhooks, SMS, RSS &amp; Atom, Maintenance Automations, Email, Private status pages, Microsoft Teams
    Jul 16, 01:00:00 GMT+0 - Identified - We&#039;re changing our database structure to allow for new features. 

We&#039;re aiming for 10-mins of downtime, but the maintenance window is 1-hour just in case.
The maintenance window is outside working hours, in a weekend.

Your public status pages will remain available for visitors. You won&#039;t be able to update them during the maintenance period, though. Jul 16, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 16, 02:05:17 GMT+0 - Completed - Maintenance complete! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 5 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re changing our database structure to allow for new features. 

We&#039;re aiming for 10-mins of downtime, but the maintenance window is 1-hour just in case.
The maintenance window is outside working hours, in a weekend.

Your public status pages will remain available for visitors. You won&#039;t be able to update them during the maintenance period, though..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:05:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance complete!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 16 Jul 2023 01:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/clk46plx0243764bboavnfn7xwg</link>
  <guid>https://instat.us/maintenance/clk46plx0243764bboavnfn7xwg</guid>
</item>

<item>
  <title>Partial outage to the dashboard, API and private pages</title>
  <description>
    Type: Incident
    Duration: 30 minutes

    Affected Components: Dashboard, Discord, API, Slack, Webhooks, SMS, RSS &amp; Atom, Maintenance Automations, Email, Private status pages, Microsoft Teams
    Jul 7, 13:20:00 GMT+0 - Resolved - Issues are now resolved Jul 7, 12:50:00 GMT+0 - Monitoring - There was a partial outage to our dashboard, API and private pages 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issues are now resolved.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  There was a partial outage to our dashboard, API and private pages.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 7 Jul 2023 12:50:00 +0000</pubDate>
  <link>https://instat.us/incident/cljsng54g12299p2nakme751cp</link>
  <guid>https://instat.us/incident/cljsng54g12299p2nakme751cp</guid>
</item>

<item>
  <title>Difficulty updating status pages</title>
  <description>
    Type: Incident
    Duration: 40 minutes

    Affected Components: Dashboard, Discord, API, Slack, Webhooks, SMS, RSS &amp; Atom, Maintenance Automations, Email, Private status pages, Microsoft Teams
    Jun 13, 18:50:00 GMT+0 - Monitoring - Outages affecting two of our providers [AWS](https://health.aws.amazon.com/health/status) and [Vercel](https://www.vercel-status.com/incidents/cqkdqrzqkspm) caused difficulty updating status pages Jun 13, 19:30:00 GMT+0 - Resolved - Issue was resolved after about an 40 mins.

It was caused by an [AWS outage in us-east-1](https://health.aws.amazon.com/health/status) that in turn caused a [Vercel serverless function outage](https://www.vercel-status.com/incidents/cqkdqrzqkspm).

We use Vercel&#039;s functions to update your status pages. So we went on and changed our Vercel serverless functions to a more stable region to avoid issues like that in the future. 
We&#039;ll also make sure to monitor issues like these more closely, so that we&#039;re able to make switching regions quicker. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Outages affecting two of our providers [AWS](https://health.aws.amazon.com/health/status) and [Vercel](https://www.vercel-status.com/incidents/cqkdqrzqkspm) caused difficulty updating status pages.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Issue was resolved after about an 40 mins.

It was caused by an [AWS outage in us-east-1](https://health.aws.amazon.com/health/status) that in turn caused a [Vercel serverless function outage](https://www.vercel-status.com/incidents/cqkdqrzqkspm).

We use Vercel&#039;s functions to update your status pages. So we went on and changed our Vercel serverless functions to a more stable region to avoid issues like that in the future. 
We&#039;ll also make sure to monitor issues like these more closely, so that we&#039;re able to make switching regions quicker..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 13 Jun 2023 18:50:00 +0000</pubDate>
  <link>https://instat.us/incident/clivu8eip98859b4oiezzbi2sv</link>
  <guid>https://instat.us/incident/clivu8eip98859b4oiezzbi2sv</guid>
</item>

<item>
  <title>Groups Migration (2)</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 2 minutes

    Affected Components: Dashboard, API, Discord, Public status pages, Slack, Webhooks, SMS, RSS &amp; Atom, Maintenance Automations, Email, Private status pages, Microsoft Teams
    Jun 1, 02:00:00 GMT+0 - Identified - We&#039;re planning to do a migration for groups, so that can support multiple levels.

We&#039;re aiming to cause zero downtime, but we&#039;re creating this maintenance just in case.

 Jun 1, 03:02:17 GMT+0 - Completed - We just completed the migration! Multi-level groups feature is now out! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 2 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re planning to do a migration for groups, so that can support multiple levels.

We&#039;re aiming to cause zero downtime, but we&#039;re creating this maintenance just in case.

.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:02:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  We just completed the migration! Multi-level groups feature is now out!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 1 Jun 2023 02:00:00 +0000</pubDate>
  <link>https://instat.us/maintenance/clibscdjs195278booiikwfw05c</link>
  <guid>https://instat.us/maintenance/clibscdjs195278booiikwfw05c</guid>
</item>

<item>
  <title>Components Migration</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 21 minutes

    Affected Components: Public status pages, Dashboard, Slack, API, Discord, Webhooks, SMS, RSS &amp; Atom, Maintenance Automations, Email, Private status pages, Microsoft Teams
    May 24, 02:30:01 GMT+0 - Identified - Maintenance is now in progress May 24, 02:30:00 GMT+0 - Identified - We&#039;re planning to do a migration for components, so that can support multiple levels. 
You&#039;ll be able to put components under components, under components, under components!

We&#039;re planning to cause zero downtime, but we&#039;re creating this maintenance just in case. May 24, 03:51:21 GMT+0 - Completed - Maintenance completed! Feature will be released soon. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re planning to do a migration for components, so that can support multiple levels. 
You&#039;ll be able to put components under components, under components, under components!

We&#039;re planning to cause zero downtime, but we&#039;re creating this maintenance just in case..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:51:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance completed! Feature will be released soon..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 24 May 2023 02:30:00 +0000</pubDate>
  <link>https://instat.us/maintenance/clhz52vss97470p1oa2sb1o3gr</link>
  <guid>https://instat.us/maintenance/clhz52vss97470p1oa2sb1o3gr</guid>
</item>

<item>
  <title>Outage to our dashboard, API and private pages</title>
  <description>
    Type: Incident
    Duration: 9 minutes

    Affected Components: Dashboard, Slack, Microsoft Teams, API, Discord, Webhooks, Email, SMS, Private status pages, RSS &amp; Atom, Maintenance Automations
    Apr 10, 12:34:00 GMT+0 - Monitoring - We&#039;re doing a big launch tomorrow!
While releasing updates and doing migrations, we triggered a 10-minute outage. 
Stay tuned! Apr 10, 12:43:00 GMT+0 - Resolved - The issue has been resolved! 
Super pumped for tomorrow&#039;s launch! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:34:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We&#039;re doing a big launch tomorrow!
While releasing updates and doing migrations, we triggered a 10-minute outage. 
Stay tuned!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:43:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been resolved! 
Super pumped for tomorrow&#039;s launch!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 10 Apr 2023 12:34:00 +0000</pubDate>
  <link>https://instat.us/incident/clgatxwug093248n1x81ift7h</link>
  <guid>https://instat.us/incident/clgatxwug093248n1x81ift7h</guid>
</item>

<item>
  <title>Upgrading backend technology</title>
  <description>
    Type: Maintenance
    Duration: 39 minutes

    Affected Components: Dashboard, API, SMS, Webhooks, Email, RSS &amp; Atom
    Jan 30, 23:00:00 GMT+0 - Identified - Will perform a necessary upgrade of our backend tech from Prisma 1 to 2. 
This will take about 30 minutes. Your status pages will continue to load normally, but you won&#039;t be able to update them during that time. Jan 30, 23:40:00 GMT+0 - Completed - Maintenance has been completed.
Still doing some maintenance tasks behind the scenes, but there shouldn&#039;t be any problems with accessing services. Jan 30, 23:01:00 GMT+0 - Identified - Maintenance is now in progress. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 39 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Will perform a necessary upgrade of our backend tech from Prisma 1 to 2. 
This will take about 30 minutes. Your status pages will continue to load normally, but you won&#039;t be able to update them during that time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has been completed.
Still doing some maintenance tasks behind the scenes, but there shouldn&#039;t be any problems with accessing services..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:01:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 30 Jan 2021 23:01:00 +0000</pubDate>
  <link>https://instat.us/maintenance/ckkk4nm9e1gme0748mi1miyij</link>
  <guid>https://instat.us/maintenance/ckkk4nm9e1gme0748mi1miyij</guid>
</item>

  </channel>
  </rss>