<?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>Brev Status - Incident history</title>
    <link>https://brev.instatus.com</link>
    <description>Brev</description>
    <pubDate>Sun, 22 Nov 2026 06:12:46 +0000</pubDate>
    
<item>
  <title>Elevated AuthKit errors</title>
  <description>
    Type: Incident
    

    Affected Components: AuthKit
    Nov 22, 06:12:46 GMT+0 - Resolved - For about 62 seconds, from 2026-11-22 05:31:27 to 2026-11-22 05:32:28 UTC, we experienced elevated error rates for AuthKit API requests. Error rates have since returned to normal. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>06:12:46</var> GMT+0</small><br><strong>Resolved</strong> -
  For about 62 seconds, from 2026-11-22 05:31:27 to 2026-11-22 05:32:28 UTC, we experienced elevated error rates for AuthKit API requests. Error rates have since returned to normal..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 22 Nov 2026 06:12:46 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwrfyrcn0fum0rprgnw62mv3</link>
  <guid>https://brev.instatus.com/incident/cmwrfyrcn0fum0rprgnw62mv3</guid>
</item>

<item>
  <title>Elevated errors for Claude Mythos 5.2 and Claude Fable 5.2</title>
  <description>
    Type: Incident
    Duration: 22 hours and 54 minutes

    Affected Components: Anthropic Claude API
    Nov 19, 09:33:18 GMT+0 - Resolved - The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 00:56 PT / 08:56 UTC to 01:11 PT / 09:11 UTC. Nov 19, 09:22:50 GMT+0 - Monitoring - A fix has been deployed for other Claude models and we are monitoring for recovery. Nov 19, 09:10:25 GMT+0 - Investigating - We are investigating elevated errors on requests to Claude Mythos 5.2 and Claude Fable 5.2. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>09:33:18</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 00:56 PT / 08:56 UTC to 01:11 PT / 09:11 UTC..</p>
<p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>09:22:50</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been deployed for other Claude models and we are monitoring for recovery..</p>
<p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>09:10:25</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to Claude Mythos 5.2 and Claude Fable 5.2. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 19 Nov 2026 09:10:24 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwnc2nly12hx0rp6t47sk4pw</link>
  <guid>https://brev.instatus.com/incident/cmwnc2nly12hx0rp6t47sk4pw</guid>
</item>

<item>
  <title>Email delivery delays</title>
  <description>
    Type: Incident
    Duration: 5 days, 22 hours and 6 minutes

    Affected Components: AuthKit
    Nov 18, 21:21:46 GMT+0 - Resolved - Email delivery metrics have returned to baseline, and recent checks show no elevated delivery delays. Nov 18, 19:26:00 GMT+0 - Monitoring - We&#039;ve remediated the issue and we&#039;re seeing email delays returning to normal levels. We&#039;ll continue monitoring. Nov 18, 18:59:40 GMT+0 - Investigating - Some WorkOS emails to Gmail and Google Workspace addresses, including sign-in codes, have been arriving several minutes late. Mail to other providers is not affected. Delayed messages are retried automatically, and we&#039;re working to restore normal delivery. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 22 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>21:21:46</var> GMT+0</small><br><strong>Resolved</strong> -
  Email delivery metrics have returned to baseline, and recent checks show no elevated delivery delays..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>19:26:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We&#039;ve remediated the issue and we&#039;re seeing email delays returning to normal levels. We&#039;ll continue monitoring..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>18:59:40</var> GMT+0</small><br><strong>Investigating</strong> -
  Some WorkOS emails to Gmail and Google Workspace addresses, including sign-in codes, have been arriving several minutes late. Mail to other providers is not affected. Delayed messages are retried automatically, and we&#039;re working to restore normal delivery..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 18 Nov 2026 18:59:40 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwmhplkg28uc0rqga1ukscbw</link>
  <guid>https://brev.instatus.com/incident/cmwmhplkg28uc0rqga1ukscbw</guid>
</item>

<item>
  <title>Degraded performance for Databricks connections</title>
  <description>
    Type: Incident
    Duration: 2 days, 18 hours and 31 minutes

    Affected Components: Analytics Dashboards
    Nov 17, 20:51:10 GMT+0 - Resolved - The incident affecting Databricks, which caused slow or failed loading of workbooks and input tables using Databricks connections, has been resolved. Databricks has confirmed their service is operational, and we have verified that workbooks using Databricks connections are loading normally again. If you are still seeing issues, please contact Sigma Support. Nov 17, 20:12:39 GMT+0 - Monitoring - Databricks has reported that the issue affecting their service has been mitigated. We are seeing workbooks and input tables that use Databricks connections recover, and we are continuing to monitor to confirm performance is back to normal. We will post another update once we have confirmed full recovery. Nov 17, 19:52:55 GMT+0 - Identified - Databricks has identified the issue and is rolling back a change to restore service. Our team is closely monitoring the situation and will provide updates as more information becomes available. Nov 17, 19:44:39 GMT+0 - Investigating - We are currently seeing degraded performance and query timeouts for workbooks and input tables that use Databricks connections. Affected content may load slowly or fail to load. This is related to an ongoing incident reported by Databricks. Our team is closely monitoring the situation and will provide updates as more information becomes available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 18 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>20:51:10</var> GMT+0</small><br><strong>Resolved</strong> -
  The incident affecting Databricks, which caused slow or failed loading of workbooks and input tables using Databricks connections, has been resolved. Databricks has confirmed their service is operational, and we have verified that workbooks using Databricks connections are loading normally again. If you are still seeing issues, please contact Sigma Support..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>20:12:39</var> GMT+0</small><br><strong>Monitoring</strong> -
  Databricks has reported that the issue affecting their service has been mitigated. We are seeing workbooks and input tables that use Databricks connections recover, and we are continuing to monitor to confirm performance is back to normal. We will post another update once we have confirmed full recovery..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>19:52:55</var> GMT+0</small><br><strong>Identified</strong> -
  Databricks has identified the issue and is rolling back a change to restore service. Our team is closely monitoring the situation and will provide updates as more information becomes available..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>19:44:39</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently seeing degraded performance and query timeouts for workbooks and input tables that use Databricks connections. Affected content may load slowly or fail to load. This is related to an ongoing incident reported by Databricks. Our team is closely monitoring the situation and will provide updates as more information becomes available..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 17 Nov 2026 19:44:38 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwl3q7e90edw0rqgrsofwqr3</link>
  <guid>https://brev.instatus.com/incident/cmwl3q7e90edw0rqgrsofwqr3</guid>
</item>

<item>
  <title>Turnstile verification failures</title>
  <description>
    Type: Incident
    Duration: 15 days, 12 hours and 11 minutes

    Affected Components: Bot Protection (CAPTCHA)
    Nov 17, 16:37:10 GMT+0 - Resolved - This incident has been resolved. Nov 17, 10:42:45 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Nov 17, 10:24:59 GMT+0 - Investigating - We are investigating reports of Turnstile verification failures affecting some users with browser fingerprinting protection enabled, including Helium. We are assessing the impact and potential mitigations. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 days, 12 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>16:37:10</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>10:42:45</var> GMT+0</small><br><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>10:24:59</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating reports of Turnstile verification failures affecting some users with browser fingerprinting protection enabled, including Helium. We are assessing the impact and potential mitigations..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 17 Nov 2026 10:24:59 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwkjvla50sf30kmw4fnhpyq6</link>
  <guid>https://brev.instatus.com/incident/cmwkjvla50sf30kmw4fnhpyq6</guid>
</item>

<item>
  <title>Elevated errors for Claude Sonnet 5.5 and Claude Fable 5.2</title>
  <description>
    Type: Incident
    Duration: 3 days, 2 hours and 44 minutes

    Affected Components: Anthropic Claude API
    Nov 16, 09:04:39 GMT+0 - Resolved - The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 23:32 PT on November 15 / 07:32 UTC on November 16 to 00:45 PT / 08:45 UTC on November 16. Nov 16, 08:02:25 GMT+0 - Monitoring - A fix has been deployed for Claude Sonnet 5.5 and other Claude models and we are monitoring for recovery. Nov 16, 07:49:55 GMT+0 - Investigating - We are currently investigating this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 2 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>09:04:39</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 23:32 PT on November 15 / 07:32 UTC on November 16 to 00:45 PT / 08:45 UTC on November 16..</p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>08:02:25</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been deployed for Claude Sonnet 5.5 and other Claude models and we are monitoring for recovery..</p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>07:49:55</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this issue..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 16 Nov 2026 07:49:55 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwiyw8ao23vy0kmgf99qmw2l</link>
  <guid>https://brev.instatus.com/incident/cmwiyw8ao23vy0kmgf99qmw2l</guid>
</item>

<item>
  <title>Elevated errors on claude.ai, the Claude API, and Claude Code</title>
  <description>
    Type: Incident
    Duration: 6 days, 4 hours and 59 minutes

    Affected Components: Anthropic Claude API
    Nov 13, 15:38:49 GMT+0 - Resolved - The issue affecting multiple surfaces has been resolved. Nov 13, 15:33:14 GMT+0 - Monitoring - Errors on claude.ai, including the mobile apps, the Claude API and Claude Code have returned to normal levels, and we are continuing to monitor. Existing connectors, including Docs and Sheets, are working again, and Claude Managed Agents and Claude Meetings are recovering. Adding a new connector on claude.ai is temporarily unavailable. Scheduled tasks and routines can run more than two hours late and some runs have been skipped, and Claude Security scans, reviews and project setup remain delayed. We&#039;ll share another update soon. Nov 13, 14:36:13 GMT+0 - Investigating - We&#039;re seeing recovery on claude.ai and the Claude API, though errors may return while we continue working on this. Connectors, including Docs and Sheets, remain degraded, as do Claude in Meetings, Claude Managed Agents, Claude Security and connector use in Claude Code. Mobile apps are affected in the same way as claude.ai. We&#039;ll share another update soon. Nov 13, 14:03:47 GMT+0 - Investigating - We are investigating reports of degraded performance affecting a variety of surfaces including claude.ai, the Claude API, Claude Code, connectors (including Claude Docs and Claude Sheets), Claude Security and Claude Managed Agents. Nov 13, 13:52:05 GMT+0 - Investigating - We are investigating reports of degraded performance affecting claude.ai, the Claude API, Claude Code, and connectors (including Claude Docs and Claude Sheets). Nov 13, 13:09:50 GMT+0 - Investigating - We are investigating reports of degraded performance affecting claude.ai, the Claude API, and Claude Code. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 4 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>15:38:49</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting multiple surfaces has been resolved..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>15:33:14</var> GMT+0</small><br><strong>Monitoring</strong> -
  Errors on claude.ai, including the mobile apps, the Claude API and Claude Code have returned to normal levels, and we are continuing to monitor. Existing connectors, including Docs and Sheets, are working again, and Claude Managed Agents and Claude Meetings are recovering. Adding a new connector on claude.ai is temporarily unavailable. Scheduled tasks and routines can run more than two hours late and some runs have been skipped, and Claude Security scans, reviews and project setup remain delayed. We&#039;ll share another update soon..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>14:36:13</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re seeing recovery on claude.ai and the Claude API, though errors may return while we continue working on this. Connectors, including Docs and Sheets, remain degraded, as do Claude in Meetings, Claude Managed Agents, Claude Security and connector use in Claude Code. Mobile apps are affected in the same way as claude.ai. We&#039;ll share another update soon..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>14:03:47</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating reports of degraded performance affecting a variety of surfaces including claude.ai, the Claude API, Claude Code, connectors (including Claude Docs and Claude Sheets), Claude Security and Claude Managed Agents..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>13:52:05</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating reports of degraded performance affecting claude.ai, the Claude API, Claude Code, and connectors (including Claude Docs and Claude Sheets)..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>13:09:50</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating reports of degraded performance affecting claude.ai, the Claude API, and Claude Code. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 13 Nov 2026 13:09:50 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwf006ot20vu0krxkv527yb1</link>
  <guid>https://brev.instatus.com/incident/cmwf006ot20vu0krxkv527yb1</guid>
</item>

<item>
  <title>Degraded performance with Microsoft incoming emails</title>
  <description>
    Type: Incident
    Duration: 1 day, 6 hours and 2 minutes

    Affected Components: Jira
    Nov 14, 06:07:30 GMT+0 - Resolved - Incoming email processing for Microsoft-connected mailboxes in Jira and Jira Service Management has returned to normal. This incident is now resolved.

For more details on the service degradation reported by Microsoft, please refer to 
Microsoft service health status. Nov 13, 16:17:01 GMT+0 - Monitoring - We continue to see signs of improvement for incoming email processing with lower failure rates. Teams continue to monitor recovery from Microsoft, and we will share the next update when there is a significant change.

For more details on the service degradation reported by Microsoft, please refer to https://status.cloud.microsoft/ Nov 13, 12:34:05 GMT+0 - Identified - Incoming email processing is showing signs of improvement, but some failures continue. Teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change.

For more details on the service degradation reported by Microsoft, please refer to -https://status.cloud.microsoft/ Nov 13, 07:32:39 GMT+0 - Investigating - Incoming email processing is still experiencing failures, and teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change.

For more details on the service degradation reported by Microsoft, please refer - https://status.cloud.microsoft/ Nov 13, 06:01:27 GMT+0 - Investigating - Jira and JSM incoming emails are experiencing elevated failures when processing mail, resulting in a reduction in the number of emails handled and a noticeable drop in incoming email processing.

The issue is attributed to the ongoing global service degradation with Microsoft 365 services. More details can be referred on their status page - https://status.cloud.microsoft/ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 6 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>06:07:30</var> GMT+0</small><br><strong>Resolved</strong> -
  Incoming email processing for Microsoft-connected mailboxes in Jira and Jira Service Management has returned to normal. This incident is now resolved.

For more details on the service degradation reported by Microsoft, please refer to 
Microsoft service health status..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>16:17:01</var> GMT+0</small><br><strong>Monitoring</strong> -
  We continue to see signs of improvement for incoming email processing with lower failure rates. Teams continue to monitor recovery from Microsoft, and we will share the next update when there is a significant change.

For more details on the service degradation reported by Microsoft, please refer to https://status.cloud.microsoft/.</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>12:34:05</var> GMT+0</small><br><strong>Identified</strong> -
  Incoming email processing is showing signs of improvement, but some failures continue. Teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change.

For more details on the service degradation reported by Microsoft, please refer to -https://status.cloud.microsoft/.</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>07:32:39</var> GMT+0</small><br><strong>Investigating</strong> -
  Incoming email processing is still experiencing failures, and teams continue to monitor recovery from Microsoft. We will share the next update if there is any significant change.

For more details on the service degradation reported by Microsoft, please refer - https://status.cloud.microsoft/.</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>06:01:27</var> GMT+0</small><br><strong>Investigating</strong> -
  Jira and JSM incoming emails are experiencing elevated failures when processing mail, resulting in a reduction in the number of emails handled and a noticeable drop in incoming email processing.

The issue is attributed to the ongoing global service degradation with Microsoft 365 services. More details can be referred on their status page - https://status.cloud.microsoft/.</p>
]]>
  </content:encoded>
  <pubDate>Fri, 13 Nov 2026 06:01:27 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwekn7c5162o0rrxriiicgti</link>
  <guid>https://brev.instatus.com/incident/cmwekn7c5162o0rrxriiicgti</guid>
</item>

<item>
  <title>Elevated AuthKit API Error Rates</title>
  <description>
    Type: Incident
    Duration: 2 days, 20 hours and 24 minutes

    Affected Components: AuthKit
    Nov 13, 01:24:04 GMT+0 - Resolved - This incident has been resolved. Nov 13, 00:28:58 GMT+0 - Identified - We are continuing to work on a fix for this issue. Nov 13, 00:28:38 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Nov 13, 00:15:40 GMT+0 - Investigating - We are investigating elevated error rates affecting AuthKit endpoints. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 20 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>01:24:04</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>00:28:58</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this issue..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>00:28:38</var> GMT+0</small><br><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>00:15:40</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated error rates affecting AuthKit endpoints..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 13 Nov 2026 00:15:40 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwe8bkhv0nrp0rrxm3ojnrzx</link>
  <guid>https://brev.instatus.com/incident/cmwe8bkhv0nrp0rrxm3ojnrzx</guid>
</item>

<item>
  <title>Elevated latency and errors for AuthKit API requests</title>
  <description>
    Type: Incident
    Duration: 2 days, 11 hours and 52 minutes

    Affected Components: AuthKit
    Nov 12, 20:55:45 GMT+0 - Resolved - This incident has been resolved. Nov 12, 20:13:05 GMT+0 - Monitoring - From 19:35 to 19:49 UTC AuthKit API request latency and error rates were elevated. Service has since recovered fully and we are monitoring. Nov 12, 19:55:52 GMT+0 - Investigating - We are seeing elevated latency and error rates in AuthKit authentication flows. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 11 hours and 52 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>20:55:45</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>20:13:05</var> GMT+0</small><br><strong>Monitoring</strong> -
  From 19:35 to 19:49 UTC AuthKit API request latency and error rates were elevated. Service has since recovered fully and we are monitoring..</p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>19:55:52</var> GMT+0</small><br><strong>Investigating</strong> -
  We are seeing elevated latency and error rates in AuthKit authentication flows..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 12 Nov 2026 19:55:52 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmwdz1ex60e6i0krx30ncjqnb</link>
  <guid>https://brev.instatus.com/incident/cmwdz1ex60e6i0krx30ncjqnb</guid>
</item>

<item>
  <title>Increase in timeouts for some unauthenticated users</title>
  <description>
    Type: Incident
    Duration: 4 days, 20 hours and 30 minutes

    Affected Components: GitHub
    Nov 8, 12:32:35 GMT+0 - Resolved - On November 8, 2026, between 08:43 and 12:29 UTC, unauthenticated requests to github.com and the GitHub REST API experienced elevated error rates. During this period, 11.3% of unauthenticated requests and 46.1% of release asset download requests failed. Authenticated requests were largely unaffected.&lt;br /&gt;&lt;br /&gt;Initial errors occurred in a backend service handling unauthenticated web traffic. A subsequent traffic spike caused high CPU utilization on servers in our caching layer. Some servers remained unhealthy after the spike ended, prolonging the disruption. We restored service by restarting caching software and rebooting affected servers.&lt;br /&gt;&lt;br /&gt;We are improving monitoring to detect these failures sooner, investigating why affected servers did not recover automatically, and reviewing caching behavior to better protect backend services during failures. Nov 8, 12:29:30 GMT+0 - Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 8, 11:56:20 GMT+0 - Investigating - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability. Nov 8, 11:50:49 GMT+0 - Investigating - We&#039;ve identified a problematic component and are working to redeploy it. Nov 8, 11:20:57 GMT+0 - Investigating - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 8, 11:16:19 GMT+0 - Investigating - We are continuing to investigate degraded performance primarily for unauthenticated users. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 20 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>12:32:35</var> GMT+0</small><br><strong>Resolved</strong> -
  On November 8, 2026, between 08:43 and 12:29 UTC, unauthenticated requests to github.com and the GitHub REST API experienced elevated error rates. During this period, 11.3% of unauthenticated requests and 46.1% of release asset download requests failed. Authenticated requests were largely unaffected.&lt;br /&gt;&lt;br /&gt;Initial errors occurred in a backend service handling unauthenticated web traffic. A subsequent traffic spike caused high CPU utilization on servers in our caching layer. Some servers remained unhealthy after the spike ended, prolonging the disruption. We restored service by restarting caching software and rebooting affected servers.&lt;br /&gt;&lt;br /&gt;We are improving monitoring to detect these failures sooner, investigating why affected servers did not recover automatically, and reviewing caching behavior to better protect backend services during failures..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>12:29:30</var> GMT+0</small><br><strong>Monitoring</strong> -
  The degradation has been mitigated. We are monitoring to ensure stability..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>11:56:20</var> GMT+0</small><br><strong>Investigating</strong> -
  The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>11:50:49</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;ve identified a problematic component and are working to redeploy it..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>11:20:57</var> GMT+0</small><br><strong>Investigating</strong> -
  API Requests is experiencing degraded performance. We are continuing to investigate..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>11:16:19</var> GMT+0</small><br><strong>Investigating</strong> -
  We are continuing to investigate degraded performance primarily for unauthenticated users..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 8 Nov 2026 10:36:05 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmw7qvhk56naa0kp318wextxc</link>
  <guid>https://brev.instatus.com/incident/cmw7qvhk56naa0kp318wextxc</guid>
</item>

<item>
  <title>Degraded performance for Claude Fable 5.1</title>
  <description>
    Type: Incident
    Duration: 1 day, 2 hours and 10 minutes

    Affected Components: Anthropic Claude API
    Nov 8, 08:54:43 GMT+0 - Resolved - The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 00:18 PT / 08:18 UTC on Nov 8 to 00:32 PT / 08:32 UTC on Nov 8. Nov 8, 08:39:01 GMT+0 - Monitoring - A fix has been deployed for Claude Fable 5.1 and we are monitoring for recovery. Nov 8, 08:28:33 GMT+0 - Investigating - We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>08:54:43</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 00:18 PT / 08:18 UTC on Nov 8 to 00:32 PT / 08:32 UTC on Nov 8..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>08:39:01</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been deployed for Claude Fable 5.1 and we are monitoring for recovery..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>08:28:33</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 8 Nov 2026 08:28:32 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmw7kmj2d6cj60kp3nmkmcued</link>
  <guid>https://brev.instatus.com/incident/cmw7kmj2d6cj60kp3nmkmcued</guid>
</item>

<item>
  <title>Intermittent 503 errors in certain regions</title>
  <description>
    Type: Incident
    Duration: 10 days and 19 hours

    Affected Components: AuthKit
    Nov 8, 00:10:40 GMT+0 - Resolved - This incident has been resolved. Nov 8, 00:02:08 GMT+0 - Monitoring - Our upstream provider has mitigated the issue affecting those edge regions and 503 error rates have returned to normal. Nov 7, 23:24:30 GMT+0 - Identified - We continue to see intermittent 503 errors on a small fraction of requests routed through Ashburn, Virginia. We continue to work with the upstream provider. Nov 7, 21:24:14 GMT+0 - Identified - We continue to see intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We will provide updates as they become available while we work with our upstream provider. Nov 7, 19:51:40 GMT+0 - Identified - We&#039;re seeing intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We&#039;ve isolated this to an issue with an upstream provider and are working with them on a resolution. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 days and 19 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>00:10:40</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>00:02:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our upstream provider has mitigated the issue affecting those edge regions and 503 error rates have returned to normal..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>23:24:30</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to see intermittent 503 errors on a small fraction of requests routed through Ashburn, Virginia. We continue to work with the upstream provider..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>21:24:14</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to see intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We will provide updates as they become available while we work with our upstream provider..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>19:51:40</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;re seeing intermittent 503 errors on a small fraction of requests routed through certain regions, primarily Ashburn, Virginia. We&#039;ve isolated this to an issue with an upstream provider and are working with them on a resolution..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 7 Nov 2026 19:51:40 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmw6tnsw757210kp3nitvt7ig</link>
  <guid>https://brev.instatus.com/incident/cmw6tnsw757210kp3nitvt7ig</guid>
</item>

<item>
  <title>Planned Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Asana
    Nov 7, 07:03:49 GMT+0 - Completed - The scheduled maintenance has been completed. Nov 7, 07:00:11 GMT+0 - Completed - The scheduled maintenance has been completed. Nov 7, 04:00:04 GMT+0 - Planned - On Saturday, Nov 7th, 2026, between 4:00 AM and 7:00 AM UTC, users may experience interruptions or limited availability while we upgrade our databases. During this maintenance window, Asana web and mobile applications and API may be affected. Thank you for your understanding and patience. Please contact support for any questions. Nov 7, 03:55:24 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 7, 03:00:29 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>07:03:49</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>07:00:11</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>04:00:04</var> GMT+0</small><br><strong>Planned</strong> -
  On Saturday, Nov 7th, 2026, between 4:00 AM and 7:00 AM UTC, users may experience interruptions or limited availability while we upgrade our databases. During this maintenance window, Asana web and mobile applications and API may be affected. Thank you for your understanding and patience. Please contact support for any questions..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>03:55:24</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>03:00:29</var> GMT+0</small><br><strong>Planned</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 7 Nov 2026 04:00:00 +0000</pubDate>
  <link>https://brev.instatus.com/maintenance/cmva6dwjj0bj50knu480pprkr</link>
  <guid>https://brev.instatus.com/maintenance/cmva6dwjj0bj50knu480pprkr</guid>
</item>

<item>
  <title>Degraded performance in AWS US-WEST-2 hosted organizations</title>
  <description>
    Type: Incident
    Duration: 2 days, 14 hours and 29 minutes

    Affected Components: Analytics Dashboards
    Nov 7, 01:24:08 GMT+0 - Resolved - This incident has been resolved. AWS status page: https://health.aws.amazon.com/health/status Nov 7, 00:21:39 GMT+0 - Monitoring - At approximately 22:51 UTC on November 6, 2026, AWS reported elevated launch failures in the US-WEST-2 region (AWS status page: https://health.aws.amazon.com/health/status). Sigma organizations hosted on AWS US-WEST-2 may experience elevated latency during this time. We are monitoring AWS status. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 14 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>01:24:08</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. AWS status page: https://health.aws.amazon.com/health/status.</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>00:21:39</var> GMT+0</small><br><strong>Monitoring</strong> -
  At approximately 22:51 UTC on November 6, 2026, AWS reported elevated launch failures in the US-WEST-2 region (AWS status page: https://health.aws.amazon.com/health/status). Sigma organizations hosted on AWS US-WEST-2 may experience elevated latency during this time. We are monitoring AWS status..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 7 Nov 2026 00:21:39 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmw5nvu673e4w0kp39mkorz9u</link>
  <guid>https://brev.instatus.com/incident/cmw5nvu673e4w0kp39mkorz9u</guid>
</item>

<item>
  <title>Incident with Pull Requests, Git Operations and Issues</title>
  <description>
    Type: Incident
    Duration: 5 days and 10 minutes

    Affected Components: GitHub
    Nov 4, 11:50:06 GMT+0 - Resolved - n November 4, 2026, between 09:35 UTC and 11:43 UTC, customers experienced intermittent errors and timeouts across GitHub.com, primarily on actions that write data. At peak, about 20% of pull request write operations (such as merging, commenting, and reviewing) failed, along with about 10% of issue creates and edits and 10–15% of project item edits. Git pushes over SSH, REST and GraphQL API requests, code scanning uploads, releases, and package operations were also affected, and about 1% of Actions runs were delayed by more than five minutes or failed to start. Overall, nearly 4% of all requests to GitHub.com failed at the worst point. Reads were largely unaffected, and retrying a failed action a short time later usually succeeded.&lt;br /&gt;&lt;br /&gt;The incident was triggered by a burst of concurrent updates to the same database record, which tied up all available connections to one of our primary databases. Although that contention cleared, the backlog of waiting requests kept our database connection layer overloaded, and it did not recover on its own. We mitigated the incident by failing over to a new primary database host. Most services recovered by 11:31 UTC, and Actions recovered by 11:43 UTC.&lt;br /&gt;&lt;br /&gt;Since the incident, we have disabled the code path that triggered the contention, increased the processing capacity of our database connection layer by 50%, and added alerting to detect this type of overload earlier. We are also improving our procedures so we can fail over sooner in similar situations. Nov 4, 11:43:52 GMT+0 - Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 4, 11:30:42 GMT+0 - Investigating - The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 4, 11:17:52 GMT+0 - Investigating - We&#039;re currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We&#039;ll provide another update as more information becomes available. Nov 4, 11:11:30 GMT+0 - Investigating - API Requests is experiencing degraded performance. We are continuing to investigate. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>11:50:06</var> GMT+0</small><br><strong>Resolved</strong> -
  n November 4, 2026, between 09:35 UTC and 11:43 UTC, customers experienced intermittent errors and timeouts across GitHub.com, primarily on actions that write data. At peak, about 20% of pull request write operations (such as merging, commenting, and reviewing) failed, along with about 10% of issue creates and edits and 10–15% of project item edits. Git pushes over SSH, REST and GraphQL API requests, code scanning uploads, releases, and package operations were also affected, and about 1% of Actions runs were delayed by more than five minutes or failed to start. Overall, nearly 4% of all requests to GitHub.com failed at the worst point. Reads were largely unaffected, and retrying a failed action a short time later usually succeeded.&lt;br /&gt;&lt;br /&gt;The incident was triggered by a burst of concurrent updates to the same database record, which tied up all available connections to one of our primary databases. Although that contention cleared, the backlog of waiting requests kept our database connection layer overloaded, and it did not recover on its own. We mitigated the incident by failing over to a new primary database host. Most services recovered by 11:31 UTC, and Actions recovered by 11:43 UTC.&lt;br /&gt;&lt;br /&gt;Since the incident, we have disabled the code path that triggered the contention, increased the processing capacity of our database connection layer by 50%, and added alerting to detect this type of overload earlier. We are also improving our procedures so we can fail over sooner in similar situations..</p>
<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>11:43:52</var> GMT+0</small><br><strong>Monitoring</strong> -
  The degradation affecting Actions has been mitigated. We are monitoring to ensure stability..</p>
<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>11:30:42</var> GMT+0</small><br><strong>Investigating</strong> -
  The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability..</p>
<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>11:17:52</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We&#039;ll provide another update as more information becomes available..</p>
<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>11:11:30</var> GMT+0</small><br><strong>Investigating</strong> -
  API Requests is experiencing degraded performance. We are continuing to investigate..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 4 Nov 2026 09:49:55 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmw20r7v2037a0rntruu9sg0r</link>
  <guid>https://brev.instatus.com/incident/cmw20r7v2037a0rntruu9sg0r</guid>
</item>

<item>
  <title>Incident with API, Git, and Copilot requests</title>
  <description>
    Type: Incident
    Duration: 1 day, 6 hours and 59 minutes

    Affected Components: GitHub
    Nov 3, 13:56:18 GMT+0 - Resolved - On November 3, 2026, between 12:34 and 13:51 UTC, some users experienced authentication failures and errors with the REST and GraphQL APIs, pull requests, Issues, and GitHub Copilot. On average, the error rate was 0.46% and peaked at 0.98% of API requests. Copilot API errors averaged 2.0% and peaked at 3.1%.&lt;br /&gt;&lt;br /&gt;This was caused by a bug in our process for replacing control-plane servers in one of our compute clusters. When a replacement server did not receive a timely response from the existing cluster, it incorrectly created a separate cluster. This stopped traffic from reaching much of the cluster&#039;s capacity and overloaded the authentication servers that were still handling requests.&lt;br /&gt;&lt;br /&gt;We mitigated the incident by removing the incorrectly configured server.&lt;br /&gt;We are also fixing the replacement logic and adding safeguards to prevent servers in this state from serving traffic. Nov 3, 13:54:20 GMT+0 - Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 3, 13:52:21 GMT+0 - Investigating - API Requests is operating normally. Nov 3, 13:51:46 GMT+0 - Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 6 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>13:56:18</var> GMT+0</small><br><strong>Resolved</strong> -
  On November 3, 2026, between 12:34 and 13:51 UTC, some users experienced authentication failures and errors with the REST and GraphQL APIs, pull requests, Issues, and GitHub Copilot. On average, the error rate was 0.46% and peaked at 0.98% of API requests. Copilot API errors averaged 2.0% and peaked at 3.1%.&lt;br /&gt;&lt;br /&gt;This was caused by a bug in our process for replacing control-plane servers in one of our compute clusters. When a replacement server did not receive a timely response from the existing cluster, it incorrectly created a separate cluster. This stopped traffic from reaching much of the cluster&#039;s capacity and overloaded the authentication servers that were still handling requests.&lt;br /&gt;&lt;br /&gt;We mitigated the incident by removing the incorrectly configured server.&lt;br /&gt;We are also fixing the replacement logic and adding safeguards to prevent servers in this state from serving traffic..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>13:54:20</var> GMT+0</small><br><strong>Monitoring</strong> -
  The degradation has been mitigated. We are monitoring to ensure stability..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>13:52:21</var> GMT+0</small><br><strong>Investigating</strong> -
  API Requests is operating normally..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>13:51:46</var> GMT+0</small><br><strong>Monitoring</strong> -
  The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 3 Nov 2026 13:25:19 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmw0r14r400ly0krt5cq0ulyv</link>
  <guid>https://brev.instatus.com/incident/cmw0r14r400ly0krt5cq0ulyv</guid>
</item>

<item>
  <title>SSO Profile API Timeouts</title>
  <description>
    Type: Incident
    Duration: 5 days, 18 hours and 10 minutes

    Affected Components: Authentication &amp; SSO
    Oct 29, 19:52:48 GMT+0 - Resolved - This incident has been resolved. Oct 29, 18:13:14 GMT+0 - Monitoring - We’ve resolved the issue causing timeouts on the SSO profile API and are monitoring. Oct 29, 17:54:33 GMT+0 - Identified - We&#039;ve identified the issue causing the SSO profile API timeouts and are working on a fix. Oct 29, 17:34:38 GMT+0 - Investigating - We are investigating timeouts on the /sso/profile endpoint. We apologize for the inconvenience and will share an update once we have more information. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 18 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>19:52:48</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>18:13:14</var> GMT+0</small><br><strong>Monitoring</strong> -
  We’ve resolved the issue causing timeouts on the SSO profile API and are monitoring..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>17:54:33</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;ve identified the issue causing the SSO profile API timeouts and are working on a fix..</p>
<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>17:34:38</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating timeouts on the /sso/profile endpoint. We apologize for the inconvenience and will share an update once we have more information..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 29 Oct 2026 17:34:38 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvttv79x214w0jrx2zm4ep2o</link>
  <guid>https://brev.instatus.com/incident/cmvttv79x214w0jrx2zm4ep2o</guid>
</item>

<item>
  <title>Elevated errors for Claude Sonnet 5.5</title>
  <description>
    Type: Incident
    Duration: 1 day, 17 hours and 8 minutes

    Affected Components: Anthropic Claude API
    Oct 27, 15:50:17 GMT+0 - Resolved - The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 07:42 PT / 14:42 UTC to 08:17 PT / 15:17 UTC. Oct 27, 15:09:09 GMT+0 - Identified - We are investigating elevated errors on requests to Claude Sonnet 5.5. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 17 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>15:50:17</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 07:42 PT / 14:42 UTC to 08:17 PT / 15:17 UTC..</p>
<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>15:09:09</var> GMT+0</small><br><strong>Identified</strong> -
  We are investigating elevated errors on requests to Claude Sonnet 5.5. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 27 Oct 2026 15:09:08 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvqtszw700030ko5nttip6rj</link>
  <guid>https://brev.instatus.com/incident/cmvqtszw700030ko5nttip6rj</guid>
</item>

<item>
  <title>Elevated errors for Claude Sonnet 5.5</title>
  <description>
    Type: Incident
    Duration: 1 day, 18 hours and 11 minutes

    Affected Components: Anthropic Claude API
    Oct 27, 09:56:46 GMT+0 - Resolved - The issue affecting Claude services has been resolved. Oct 27, 09:38:11 GMT+0 - Monitoring - A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery. Oct 27, 09:14:35 GMT+0 - Investigating - We are investigating elevated errors on requests to Claude Sonnet 5.5. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 18 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>09:56:46</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting Claude services has been resolved..</p>
<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>09:38:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery..</p>
<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>09:14:35</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to Claude Sonnet 5.5. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 27 Oct 2026 09:14:35 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvqh4gfu1hdv0rnrxxwt8hov</link>
  <guid>https://brev.instatus.com/incident/cmvqh4gfu1hdv0rnrxxwt8hov</guid>
</item>

<item>
  <title>Incident with Actions, Issues, API Requests and Pull Requests</title>
  <description>
    Type: Incident
    Duration: 8 hours and 56 minutes

    Affected Components: GitHub
    Oct 26, 18:57:22 GMT+0 - Resolved - On October 26, 2026, between 17:52 and 18:49 UTC, some customers experienced slower response times across the Checks API, Issues, Pull Requests, GraphQL, Notifications, and related services. Impact was limited to requests served from one of our datacenter sites. Some GraphQL requests failed, and some notifications were delayed. Among GraphQL requests served from the affected site, the average error rate was 5.68%, with a peak five-minute error rate of 14.32%. &lt;br /&gt;&lt;br /&gt;Unusually large requests for contribution history overwhelmed part of our database infrastructure, causing a backlog. Requests continued reaching the slow component rather than being redirected to healthy systems. Restarting the component restored its performance. The incident was marked mitigated at 18:46 UTC and resolved at 18:57 UTC. &lt;br /&gt;&lt;br /&gt;We are adding limits to these requests, improving alerts to detect overload sooner, and strengthening automatic redirection to healthy systems. Oct 26, 18:54:04 GMT+0 - Monitoring - We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.&lt;br /&gt;&lt;br /&gt;We mitigated the issue and all services have recovered. Oct 26, 18:50:58 GMT+0 - Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 26, 18:48:26 GMT+0 - Investigating - We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>18:57:22</var> GMT+0</small><br><strong>Resolved</strong> -
  On October 26, 2026, between 17:52 and 18:49 UTC, some customers experienced slower response times across the Checks API, Issues, Pull Requests, GraphQL, Notifications, and related services. Impact was limited to requests served from one of our datacenter sites. Some GraphQL requests failed, and some notifications were delayed. Among GraphQL requests served from the affected site, the average error rate was 5.68%, with a peak five-minute error rate of 14.32%. &lt;br /&gt;&lt;br /&gt;Unusually large requests for contribution history overwhelmed part of our database infrastructure, causing a backlog. Requests continued reaching the slow component rather than being redirected to healthy systems. Restarting the component restored its performance. The incident was marked mitigated at 18:46 UTC and resolved at 18:57 UTC. &lt;br /&gt;&lt;br /&gt;We are adding limits to these requests, improving alerts to detect overload sooner, and strengthening automatic redirection to healthy systems..</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>18:54:04</var> GMT+0</small><br><strong>Monitoring</strong> -
  We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.&lt;br /&gt;&lt;br /&gt;We mitigated the issue and all services have recovered..</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>18:50:58</var> GMT+0</small><br><strong>Monitoring</strong> -
  The degradation has been mitigated. We are monitoring to ensure stability..</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>18:48:26</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests.</p>
]]>
  </content:encoded>
  <pubDate>Mon, 26 Oct 2026 18:48:26 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvpm24wb044j0rnrjyyz4skq</link>
  <guid>https://brev.instatus.com/incident/cmvpm24wb044j0rnrjyyz4skq</guid>
</item>

<item>
  <title>Elevated errors for Claude Fable 5.1</title>
  <description>
    Type: Incident
    Duration: 1 day, 8 hours and 21 minutes

    Affected Components: Anthropic Claude API
    Oct 25, 08:49:29 GMT+0 - Resolved - The issue affecting Claude services has been resolved. Impact occurred from 01:08 PT / 08:08 UTC to 01:29 PT / 08:29 UTC. Oct 25, 08:30:47 GMT+0 - Monitoring - A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery. Oct 25, 08:17:18 GMT+0 - Identified - We have identified the cause of elevated errors on requests to Claude Fable 5.1 and are working on a fix. We will provide an update as soon as possible. Oct 25, 08:17:08 GMT+0 - Investigating - We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 8 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>08:49:29</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting Claude services has been resolved. Impact occurred from 01:08 PT / 08:08 UTC to 01:29 PT / 08:29 UTC..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>08:30:47</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>08:17:18</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of elevated errors on requests to Claude Fable 5.1 and are working on a fix. We will provide an update as soon as possible..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>08:17:08</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 25 Oct 2026 08:17:08 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvnk3ltg1s5n0jqhf3yj437g</link>
  <guid>https://brev.instatus.com/incident/cmvnk3ltg1s5n0jqhf3yj437g</guid>
</item>

<item>
  <title>Elevated errors for Claude Sonnet 5.5 and other models</title>
  <description>
    Type: Incident
    Duration: 4 days, 3 hours and 20 minutes

    Affected Components: Anthropic Claude API
    Oct 25, 07:53:39 GMT+0 - Resolved - The issue affecting Claude services has been resolved. Impact occurred from 23:05 PT on October 24 / 06:05 UTC on October 25 to 23:35 PT on October 24 / 06:35 UTC on October 25. Oct 25, 06:35:59 GMT+0 - Monitoring - A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery. Oct 25, 06:27:52 GMT+0 - Identified - We have identified the cause of elevated errors on requests to Claude Sonnet 5.5 and are working on a fix. We will provide an update as soon as possible. Oct 25, 06:14:18 GMT+0 - Investigating - We are investigating elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 3 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>07:53:39</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting Claude services has been resolved. Impact occurred from 23:05 PT on October 24 / 06:05 UTC on October 25 to 23:35 PT on October 24 / 06:35 UTC on October 25..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>06:35:59</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>06:27:52</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of elevated errors on requests to Claude Sonnet 5.5 and are working on a fix. We will provide an update as soon as possible..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>06:14:18</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 25 Oct 2026 06:14:18 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvnft9ho1k3k0jqh7kapsbl3</link>
  <guid>https://brev.instatus.com/incident/cmvnft9ho1k3k0jqh7kapsbl3</guid>
</item>

<item>
  <title>Elevated errors for Claude Fable 5 and Claude Fable 5.1</title>
  <description>
    Type: Incident
    Duration: 1 day, 12 hours and 40 minutes

    Affected Components: Anthropic Claude API
    Oct 24, 05:53:30 GMT+0 - Resolved - The issue affecting Claude services has been resolved. Impact occurred from 22:00 PT on October 23 / 05:00 UTC on October 24 to 22:35 PT on October 23 / 05:35 UTC on October 24. Oct 24, 05:41:17 GMT+0 - Monitoring - A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery. Oct 24, 05:40:06 GMT+0 - Identified - We have identified the cause of elevated errors on requests to other Claude models and are working on a fix. We will provide an update as soon as possible. Oct 24, 05:24:53 GMT+0 - Identified - We have identified the cause of elevated errors on requests to other Claude models and are working on a fix. We will provide an update as soon as possible. Oct 24, 05:16:50 GMT+0 - Investigating - We are investigating elevated errors on requests to other Claude models. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 12 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>05:53:30</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting Claude services has been resolved. Impact occurred from 22:00 PT on October 23 / 05:00 UTC on October 24 to 22:35 PT on October 23 / 05:35 UTC on October 24..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>05:41:17</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>05:40:06</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of elevated errors on requests to other Claude models and are working on a fix. We will provide an update as soon as possible..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>05:24:53</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of elevated errors on requests to other Claude models and are working on a fix. We will provide an update as soon as possible..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>05:16:50</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to other Claude models. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 24 Oct 2026 05:16:50 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvly8pnw32nw0ko2dkjd0wag</link>
  <guid>https://brev.instatus.com/incident/cmvly8pnw32nw0ko2dkjd0wag</guid>
</item>

<item>
  <title>Elevated errors for Claude Opus 5.5</title>
  <description>
    Type: Incident
    Duration: 5 hours and 40 minutes

    Affected Components: Anthropic Claude API
    Oct 24, 00:37:17 GMT+0 - Resolved - The issue affecting Claude Opus 5.5 has been resolved. Impact occurred from 17:23 PT on October 23 / 00:23 UTC on October 24 to 17:34 PT on October 23 / 00:34 UTC on October 24. Oct 24, 00:31:37 GMT+0 - Investigating - We are investigating elevated errors on requests to Claude Opus 5.5. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>00:37:17</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting Claude Opus 5.5 has been resolved. Impact occurred from 17:23 PT on October 23 / 00:23 UTC on October 24 to 17:34 PT on October 23 / 00:34 UTC on October 24..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>00:31:37</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to Claude Opus 5.5. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 24 Oct 2026 00:31:37 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvlo23pw2k790ko26snkwo94</link>
  <guid>https://brev.instatus.com/incident/cmvlo23pw2k790ko26snkwo94</guid>
</item>

<item>
  <title>Elevated errors for Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5</title>
  <description>
    Type: Incident
    Duration: 1 day, 9 hours and 38 minutes

    Affected Components: Anthropic Claude API
    Oct 24, 00:11:20 GMT+0 - Resolved - The issue affecting Claude models has been resolved. Impact occurred from 16:28 PT / 23:28 UTC on October 23 to 16:59 PT / 23:59 UTC on October 23. Oct 23, 23:54:14 GMT+0 - Monitoring - We are seeing success rates return to normal for all affected models, and are continuing to monitor to ensure no further issues. Oct 23, 23:39:22 GMT+0 - Identified - We have identified the cause of elevated errors on requests to Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5, as well as fast mode requests to Opus 5.5 and are working on a fix. We will provide an update as soon as possible. Oct 23, 23:37:42 GMT+0 - Investigating - We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 9 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>00:11:20</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting Claude models has been resolved. Impact occurred from 16:28 PT / 23:28 UTC on October 23 to 16:59 PT / 23:59 UTC on October 23..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>23:54:14</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are seeing success rates return to normal for all affected models, and are continuing to monitor to ensure no further issues..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>23:39:22</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of elevated errors on requests to Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5, as well as fast mode requests to Opus 5.5 and are working on a fix. We will provide an update as soon as possible..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>23:37:42</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 23 Oct 2026 23:37:42 +0000</pubDate>
  <link>https://brev.instatus.com/incident/cmvlm4ion2hir0ko2h6r7bujx</link>
  <guid>https://brev.instatus.com/incident/cmvlm4ion2hir0ko2h6r7bujx</guid>
</item>

<item>
  <title>Scheduled System Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Authentication &amp; SSO, AuthKit, Directory Sync, FGA
    Oct 10, 15:29:14 GMT+0 - Completed - The scheduled maintenance has been completed. Oct 10, 15:23:11 GMT+0 - Identified - Verification is currently underway for the maintenance items. Oct 10, 15:00:10 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 10, 14:00:18 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Oct 7, 13:10:44 GMT+0 - Planned - WorkOS will be undergoing a required platform upgrade on Saturday, October 10th starting at 15:00 UTC and ending at 16:00 UTC. 

Within this window, we expect a single period of increased latency and error rate lasting up to 2 minutes across all WorkOS products, including event and webhook delivery. Events and webhooks generated during this period may be delayed. If you have any questions, please reach out to support@workos.com 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>15:29:14</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>15:23:11</var> GMT+0</small><br><strong>Identified</strong> -
  Verification is currently underway for the maintenance items..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>15:00:10</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>14:00:18</var> GMT+0</small><br><strong>Planned</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>13:10:44</var> GMT+0</small><br><strong>Planned</strong> -
  WorkOS will be undergoing a required platform upgrade on Saturday, October 10th starting at 15:00 UTC and ending at 16:00 UTC. 

Within this window, we expect a single period of increased latency and error rate lasting up to 2 minutes across all WorkOS products, including event and webhook delivery. Events and webhooks generated during this period may be delayed. If you have any questions, please reach out to support@workos.com.</p>
]]>
  </content:encoded>
  <pubDate>Sat, 10 Oct 2026 15:00:00 +0000</pubDate>
  <link>https://brev.instatus.com/maintenance/cmuy4po8j0xf00klubuuo3pc9</link>
  <guid>https://brev.instatus.com/maintenance/cmuy4po8j0xf00klubuuo3pc9</guid>
</item>

<item>
  <title>Planned Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Asana
    Aug 2, 05:45:56 GMT+0 - Completed - The scheduled maintenance has been completed. Aug 2, 05:00:11 GMT+0 - Completed - The scheduled maintenance has been completed. Aug 2, 02:46:42 GMT+0 - Identified - Scheduled maintenance is still in progress. We will provide updates as necessary. Aug 2, 02:46:29 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug 2, 02:00:13 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Jul 27, 22:04:15 GMT+0 - Planned - On Sunday, Aug 2nd, 2026, between 3:00 am to 5:00 am UTC, users may experience interruptions or limited availability while we upgrade our databases. During this maintenance window, Asana web and mobile applications and API may be affected. Thank you for your understanding and patience. Please contact support for any questions. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>05:45:56</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>05:00:11</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>02:46:42</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is still in progress. We will provide updates as necessary..</p>
<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>02:46:29</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>02:00:13</var> GMT+0</small><br><strong>Planned</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>22:04:15</var> GMT+0</small><br><strong>Planned</strong> -
  On Sunday, Aug 2nd, 2026, between 3:00 am to 5:00 am UTC, users may experience interruptions or limited availability while we upgrade our databases. During this maintenance window, Asana web and mobile applications and API may be affected. Thank you for your understanding and patience. Please contact support for any questions..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 2 Aug 2026 03:00:00 +0000</pubDate>
  <link>https://brev.instatus.com/maintenance/cmt0rltvm18tp0rmgzuvmsnol</link>
  <guid>https://brev.instatus.com/maintenance/cmt0rltvm18tp0rmgzuvmsnol</guid>
</item>

  </channel>
  </rss>