<?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>Serval Status - Incident history</title>
    <link>https://legacystatus.serval.com</link>
    <description>Serval</description>
    <pubDate>Sat, 10 Oct 2026 20:26:15 +0000</pubDate>
    
<item>
  <title>Status page migration complete</title>
  <description>
    Type: Incident
    

    
    Oct 10, 20:26:15 GMT+0 - Resolved - We’ve migrated to a new status page provider. Please visit &lt;https://status.serval.com&gt; and select “Subscribe to updates” to receive future status updates. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>20:26:15</var> GMT+0</small><br><strong>Resolved</strong> -
  We’ve migrated to a new status page provider. Please visit &lt;https://status.serval.com&gt; and select “Subscribe to updates” to receive future status updates..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 10 Oct 2026 20:26:15 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmv2ugzqo008j1ms78iig28m1</link>
  <guid>https://legacystatus.serval.com/incident/cmv2ugzqo008j1ms78iig28m1</guid>
</item>

<item>
  <title>Errors processing large PDFs in the Responses API</title>
  <description>
    Type: Incident
    Duration: 11 days, 1 hour and 55 minutes

    Affected Components: Third Party: OpenAI → APIs → Responses
    Oct 6, 20:11:27 GMT+0 - Resolved - All impacted services have now fully recovered. Oct 6, 16:39:48 GMT+0 - Identified - We are implementing the mitigation. Oct 6, 15:45:31 GMT+0 - Investigating - We are investigating the issue for the listed services. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 days, 1 hour and 55 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>20:11:27</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>16:39:48</var> GMT+0</small><br><strong>Identified</strong> -
  We are implementing the mitigation..</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>15:45:31</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 6 Oct 2026 15:45:31 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmuwuzjj83un90rrtmykykd4w</link>
  <guid>https://legacystatus.serval.com/incident/cmuwuzjj83un90rrtmykykd4w</guid>
</item>

<item>
  <title>Elevated latency for some API requests</title>
  <description>
    Type: Incident
    Duration: 8 days and 18 hours

    Affected Components: Third Party: OpenAI → APIs → Chat Completions, Third Party: OpenAI → APIs → Responses
    Sep 30, 20:35:46 GMT+0 - Resolved - All impacted services have now fully recovered. Sep 30, 18:21:53 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Sep 30, 17:51:40 GMT+0 - Identified - We have implemented an initial mitigation and are seeing improvements in API latency. We are continuing to investigate the scope of the issue and apply additional mitigations as needed. Some requests to the Responses and Chat Completions APIs may still experience elevated latency or timeouts. Sep 30, 17:13:13 GMT+0 - Identified - We have identified that users are experiencing elevated latency for the impacted services.

We are working on implementing a mitigation. Sep 30, 17:05:46 GMT+0 - Identified - We have identified that users are experiencing elevated latency for the impacted services.

We are working on implementing a mitigation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 days and 18 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>20:35:46</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>18:21:53</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>17:51:40</var> GMT+0</small><br><strong>Identified</strong> -
  We have implemented an initial mitigation and are seeing improvements in API latency. We are continuing to investigate the scope of the issue and apply additional mitigations as needed. Some requests to the Responses and Chat Completions APIs may still experience elevated latency or timeouts..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>17:13:13</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified that users are experiencing elevated latency for the impacted services.

We are working on implementing a mitigation..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>17:05:46</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified that users are experiencing elevated latency for the impacted services.

We are working on implementing a mitigation..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 17:05:46 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmuod7bhg034t0rpkus6idp0r</link>
  <guid>https://legacystatus.serval.com/incident/cmuod7bhg034t0rpkus6idp0r</guid>
</item>

<item>
  <title>Elevated errors across ChatGPT, Codex, and the API including the Agents API</title>
  <description>
    Type: Incident
    Duration: 13 days, 9 hours and 9 minutes

    Affected Components: Third Party: OpenAI → APIs → Chat Completions, Third Party: OpenAI → APIs → Responses
    Oct 6, 08:26:10 GMT+0 - Resolved - All impacted services have now fully recovered. Sep 29, 23:14:02 GMT+0 - Resolved - The issue causing elevated errors across ChatGPT, Codex, and the API has been resolved, and all affected services have recovered.

Thank you for your patience while we worked to restore service.

The detailed Root Cause Analysis (RCA) will be published in the next 5 business days. Sep 29, 22:47:10 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Sep 29, 22:03:22 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Sep 29, 21:09:11 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Sep 29, 19:39:36 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Sep 29, 19:08:39 GMT+0 - Investigating - We’re still investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.

Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more. Sep 29, 18:24:17 GMT+0 - Investigating - We’re investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.

Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more. Sep 29, 18:09:42 GMT+0 - Resolved -  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 days, 9 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>08:26:10</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>23:14:02</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue causing elevated errors across ChatGPT, Codex, and the API has been resolved, and all affected services have recovered.

Thank you for your patience while we worked to restore service.

The detailed Root Cause Analysis (RCA) will be published in the next 5 business days..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>22:47:10</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>22:03:22</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>21:09:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>19:39:36</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>19:08:39</var> GMT+0</small><br><strong>Investigating</strong> -
  We’re still investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.

Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>18:24:17</var> GMT+0</small><br><strong>Investigating</strong> -
  We’re investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.

Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>18:09:42</var> GMT+0</small><br><strong>Resolved</strong> -
  .</p>
]]>
  </content:encoded>
  <pubDate>Tue, 29 Sep 2026 17:52:52 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmumzdc7dfhcz0krvitid6nzw</link>
  <guid>https://legacystatus.serval.com/incident/cmumzdc7dfhcz0krvitid6nzw</guid>
</item>

<item>
  <title>Workflow runs failing to start, Degraded Catalyst performance</title>
  <description>
    Type: Incident
    Duration: 2 hours and 10 minutes

    Affected Components: Workflows, Third Party: Anthropic → Claude API (api.anthropic.com)
    Sep 29, 18:10:40 GMT+0 - Resolved - We implemented a fix and are currently monitoring the result. Sep 29, 16:00:23 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> 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>18:10:40</var> GMT+0</small><br><strong>Resolved</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>16:00:23</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 29 Sep 2026 16:00:23 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmumxsu2q08kz1bobb5q9k5g0</link>
  <guid>https://legacystatus.serval.com/incident/cmumxsu2q08kz1bobb5q9k5g0</guid>
</item>

<item>
  <title>Email delivery issues</title>
  <description>
    Type: Incident
    Duration: 57 minutes

    Affected Components: Application
    Sep 19, 18:56:29 GMT+0 - Resolved - This was resolved by a rate limit increase. Sep 19, 17:59:23 GMT+0 - Investigating - We are experiencing email deliverability issues due to a AWS SES rate-limit issue. We are working with AWS support to get it resolved ASAP. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 57 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>18:56:29</var> GMT+0</small><br><strong>Resolved</strong> -
  This was resolved by a rate limit increase..</p>
<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>17:59:23</var> GMT+0</small><br><strong>Investigating</strong> -
  We are experiencing email deliverability issues due to a AWS SES rate-limit issue. We are working with AWS support to get it resolved ASAP..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 19 Sep 2026 17:59:23 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmu8oz8xc0eta1dmrqpqxou97</link>
  <guid>https://legacystatus.serval.com/incident/cmu8oz8xc0eta1dmrqpqxou97</guid>
</item>

<item>
  <title>SSO Login Issues</title>
  <description>
    Type: Incident
    Duration: 27 minutes

    Affected Components: Login
    Sep 18, 23:35:05 GMT+0 - Resolved - This issue is resolved. WorkOS has recovered from their API errors. Sep 18, 23:07:39 GMT+0 - Investigating - We are currently investigating issues with SSO-based login.   
  
It appears to be an issue with a downstream auth-provider, WorkOS.  
  
See &lt;https://status.workos.com/&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>23:35:05</var> GMT+0</small><br><strong>Resolved</strong> -
  This issue is resolved. WorkOS has recovered from their API errors..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>23:07:39</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating issues with SSO-based login.   
  
It appears to be an issue with a downstream auth-provider, WorkOS.  
  
See &lt;https://status.workos.com/&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Fri, 18 Sep 2026 23:07:39 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmu7kjsx30knx0wpc8sgysh68</link>
  <guid>https://legacystatus.serval.com/incident/cmu7kjsx30knx0wpc8sgysh68</guid>
</item>

<item>
  <title>Issues with Email Intake</title>
  <description>
    Type: Incident
    Duration: 1 hour and 41 minutes

    Affected Components: Application
    Sep 18, 22:16:23 GMT+0 - Resolved - This incident has been resolved. Sep 18, 21:33:52 GMT+0 - Monitoring - We are still monitoring. Many customers report being able to create tickets via email and getting fast response times.   
  
Some customers will still experience slow response times caused by the outage to AWS Simple Notification Service (SNS). Sep 18, 21:10:26 GMT+0 - Monitoring - This is caused by AWS outage with SNS in us-west-1\. We are still actively monitoring.  
  
Some customers are reporting they are now able to create email tickets.

![](https://res.cloudinary.com/sup/image/upload/v1789765787/wyaame8pdepbrorggz7q.png) Sep 18, 20:36:20 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 18, 20:35:25 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>22:16:23</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>21:33:52</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are still monitoring. Many customers report being able to create tickets via email and getting fast response times.   
  
Some customers will still experience slow response times caused by the outage to AWS Simple Notification Service (SNS)..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>21:10:26</var> GMT+0</small><br><strong>Monitoring</strong> -
  This is caused by AWS outage with SNS in us-west-1\. We are still actively monitoring.  
  
Some customers are reporting they are now able to create email tickets.

![](https://res.cloudinary.com/sup/image/upload/v1789765787/wyaame8pdepbrorggz7q.png).</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>20:36:20</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>20:35:25</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 18 Sep 2026 20:35:25 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmu7f419v0j811fpcftr6cubq</link>
  <guid>https://legacystatus.serval.com/incident/cmu7f419v0j811fpcftr6cubq</guid>
</item>

<item>
  <title>We are seeing elevated error rates across API models</title>
  <description>
    Type: Incident
    Duration: 21 hours

    Affected Components: Third Party: OpenAI → APIs → Chat Completions, Third Party: OpenAI → APIs → Responses
    Sep 17, 21:50:36 GMT+0 - Resolved - All impacted services have now fully recovered. Sep 17, 21:20:00 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Sep 17, 20:20:00 GMT+0 - Identified - We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>21:50:36</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>21:20:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>20:20:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 17 Sep 2026 21:29:35 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmu61rkq584ko0rmh7ckuc5eu</link>
  <guid>https://legacystatus.serval.com/incident/cmu61rkq584ko0rmh7ckuc5eu</guid>
</item>

<item>
  <title>Tickets Failing to Create</title>
  <description>
    Type: Incident
    Duration: 1 hour and 1 minute

    Affected Components: Application
    Sep 16, 23:37:44 GMT+0 - Resolved - This incident has been resolved. Sep 16, 23:06:31 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 16, 22:37:12 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>23:37:44</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>23:06:31</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>22:37:12</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 16 Sep 2026 22:37:12 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmu4oky9y02xb0wo93j06j390</link>
  <guid>https://legacystatus.serval.com/incident/cmu4oky9y02xb0wo93j06j390</guid>
</item>

<item>
  <title>Degraded performance of the help agent</title>
  <description>
    Type: Incident
    Duration: 38 minutes

    Affected Components: Application
    Sep 14, 07:29:46 GMT+0 - Resolved - This incident has been resolved. Sep 14, 07:28:18 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 14, 07:08:39 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 14, 06:51:17 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 38 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>07:29:46</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>07:28:18</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>07:08:39</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>06:51:17</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 14 Sep 2026 06:51:17 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmu0vwrsu096q0wl02xpl2z4s</link>
  <guid>https://legacystatus.serval.com/incident/cmu0vwrsu096q0wl02xpl2z4s</guid>
</item>

<item>
  <title>Elevated errors for GPT-5.6 Sol on the API</title>
  <description>
    Type: Incident
    Duration: 5 days, 13 hours and 28 minutes

    Affected Components: Third Party: OpenAI → APIs → Chat Completions, Third Party: OpenAI → APIs → Responses
    Sep 11, 11:21:43 GMT+0 - Resolved - All impacted services have now fully recovered. Sep 11, 10:09:47 GMT+0 - Monitoring - We have brought additional capacity online and are seeing improvements for some GPT-5.6 Sol API traffic.
We continue to mitigate elevated errors affecting Chat Completions and Responses and are monitoring recovery Sep 11, 09:08:15 GMT+0 - Identified - We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 13 hours and 28 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>11:21:43</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>10:09:47</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have brought additional capacity online and are seeing improvements for some GPT-5.6 Sol API traffic.
We continue to mitigate elevated errors affecting Chat Completions and Responses and are monitoring recovery.</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>09:08:15</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 11 Sep 2026 09:08:15 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmtwqotgj0pnn0rl9x318tu4g</link>
  <guid>https://legacystatus.serval.com/incident/cmtwqotgj0pnn0rl9x318tu4g</guid>
</item>

<item>
  <title>Increased Latency across Slack, Teams and Workflow Runs</title>
  <description>
    Type: Incident
    Duration: 37 minutes

    Affected Components: Application, Workflows
    Sep 8, 21:51:47 GMT+0 - Resolved - This incident has been resolved. Sep 8, 21:39:42 GMT+0 - Monitoring - Latency is recovering after working through a backlog of events. We&#039;re monitoring. Sep 8, 21:19:55 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 8, 21:14:29 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 37 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>21:51:47</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>21:39:42</var> GMT+0</small><br><strong>Monitoring</strong> -
  Latency is recovering after working through a backlog of events. We&#039;re monitoring..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>21:19:55</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>21:14:29</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 8 Sep 2026 21:14:29 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmtt63rgy0cnc13mr1di1c89k</link>
  <guid>https://legacystatus.serval.com/incident/cmtt63rgy0cnc13mr1di1c89k</guid>
</item>

<item>
  <title>Slow responses from help agent</title>
  <description>
    Type: Incident
    Duration: 45 minutes

    Affected Components: Workflows
    Sep 6, 07:21:00 GMT+0 - Resolved - This incident has been resolved. Sep 6, 06:30:08 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>07:21:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>06:30:08</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 6 Sep 2026 06:30:08 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmtpidxca0hun1bn3w80zi9fu</link>
  <guid>https://legacystatus.serval.com/incident/cmtpidxca0hun1bn3w80zi9fu</guid>
</item>

<item>
  <title>Issues with help agent responses and running workflows</title>
  <description>
    Type: Incident
    Duration: 30 minutes

    Affected Components: Application, Workflows
    Sep 4, 20:27:49 GMT+0 - Resolved - This incident has been mitigated. We are working to implement long-term preventative fixes. Sep 4, 20:18:03 GMT+0 - Monitoring - We are observing a return to normal behavior and are continuing to monitor recovery. Sep 4, 20:13:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring recovery. Sep 4, 20:11:35 GMT+0 - Identified - We have identified a root cause and are implementing a fix. Sep 4, 19:57:29 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>20:27:49</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been mitigated. We are working to implement long-term preventative fixes..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>20:18:03</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are observing a return to normal behavior and are continuing to monitor recovery..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>20:13:51</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring recovery..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>20:11:35</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified a root cause and are implementing a fix..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>19:57:29</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 4 Sep 2026 19:57:29 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmtndlbww00he0wo0gwi4tdb9</link>
  <guid>https://legacystatus.serval.com/incident/cmtndlbww00he0wo0gwi4tdb9</guid>
</item>

<item>
  <title>Degraded performance with help agent</title>
  <description>
    Type: Incident
    Duration: 30 minutes

    Affected Components: Application
    Sep 3, 11:00:00 GMT+0 - Resolved - We identified and addressed a period of increased load that impacted workflow runs from approximately 01:40 to 03:40 AM PT. We are implementing longer term fixes for this class of issue. This incident has been resolved. Sep 3, 10:30:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We identified and addressed a period of increased load that impacted workflow runs from approximately 01:40 to 03:40 AM PT. We are implementing longer term fixes for this class of issue. This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 3 Sep 2026 10:30:00 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmtlejznp06yk1mph1ywqwohz</link>
  <guid>https://legacystatus.serval.com/incident/cmtlejznp06yk1mph1ywqwohz</guid>
</item>

<item>
  <title>Degraded performance with help agent</title>
  <description>
    Type: Incident
    Duration: 33 minutes

    Affected Components: Application
    Sep 3, 11:03:16 GMT+0 - Resolved - We have observed performance returning to normal baseline. We are implementing longer term fixes to address this class of performance degradation. This incident has been resolved. Sep 3, 10:30:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>11:03:16</var> GMT+0</small><br><strong>Resolved</strong> -
  We have observed performance returning to normal baseline. We are implementing longer term fixes to address this class of performance degradation. This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 3 Sep 2026 10:30:00 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmtlehkrf0bp31nqtkfqz98ek</link>
  <guid>https://legacystatus.serval.com/incident/cmtlehkrf0bp31nqtkfqz98ek</guid>
</item>

<item>
  <title>Elevated latency in the Responses API</title>
  <description>
    Type: Incident
    Duration: 20 days, 13 hours and 49 minutes

    Affected Components: Third Party: OpenAI → APIs → Responses
    Sep 1, 19:05:46 GMT+0 - Resolved - All impacted services have now fully recovered. Sep 1, 18:09:31 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Sep 1, 17:36:17 GMT+0 - Identified - We are implementing the mitigation. Sep 1, 15:15:09 GMT+0 - Identified - We have identified elevated latencies impacting Responses API on the US endpoint. Sep 1, 01:46:22 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Aug 31, 23:13:46 GMT+0 - Monitoring - We have applied a mitigation and are monitoring recovery. Aug 31, 22:27:56 GMT+0 - Identified - We have identified an issue causing elevated latency for some Responses API requests. We are working on implementing a mitigation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 days, 13 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>19:05:46</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>18:09:31</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>17:36:17</var> GMT+0</small><br><strong>Identified</strong> -
  We are implementing the mitigation..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>15:15:09</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified elevated latencies impacting Responses API on the US endpoint..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>01:46:22</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>23:13:46</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied a mitigation and are monitoring recovery..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>22:27:56</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified an issue causing elevated latency for some Responses API requests. We are working on implementing a mitigation..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 31 Aug 2026 22:27:56 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmthtf9n38eu20kpw9nkx45e5</link>
  <guid>https://legacystatus.serval.com/incident/cmthtf9n38eu20kpw9nkx45e5</guid>
</item>

<item>
  <title>Third Party: OpenAI provider outage</title>
  <description>
    Type: Incident
    Duration: 9 hours and 36 minutes

    Affected Components: Third Party: OpenAI → APIs → Chat Completions, Third Party: OpenAI → APIs → Responses
    Sep 1, 02:43:51 GMT+0 - Resolved - We are continuing to use Anthropic for all agent responses as we monitor OpenAI&#039;s recovery. We will return to normal operation once API responsiveness returns to expected baseline. Aug 31, 22:51:45 GMT+0 - Monitoring - We are continuing to use Anthropic for all agent responses as we monitor OpenAI API incident response and recovery. Follow OpenAI&#039;s status updates here: &lt;https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98&gt; Aug 31, 21:34:40 GMT+0 - Monitoring - We are continuing to use Anthropic for all agent responses as we monitor OpenAI API recovery. Aug 31, 20:16:08 GMT+0 - Monitoring - We are continuing to observe issues with OpenAI API responsiveness, so will maintain failover to Anthropic models and continue monitoring. Aug 31, 19:43:53 GMT+0 - Monitoring - We are recording improved API responsiveness from OpenAI and are evaluating a progressive rollback to normal operations. Aug 31, 19:17:54 GMT+0 - Monitoring - We have completed failing remaining inference activity to Anthropic and are continuing to monitor OpenAI endpoints for recovery.  Aug 31, 18:58:57 GMT+0 - Monitoring - We are continuing to failover to Anthropic and are implementing other mitigations. Aug 31, 18:26:11 GMT+0 - Monitoring - We are continuing to failover to Anthropic models for remaining affected agent behaviors and monitoring rollout. Aug 31, 17:45:26 GMT+0 - Monitoring - We are continuing to observe inconsistent response latencies with OpenAI endpoints. We are deploying a mitigation to failover all remaining affected model usages to Anthropic. Aug 31, 17:32:44 GMT+0 - Monitoring - We are seeing consistent availability from the OpenAI endpoint, but performance remains degraded. We are continuing to monitor the situation. Aug 31, 17:21:42 GMT+0 - Investigating - We are continuing to see fluctuating availability and response times from OpenAI across multiple model classes. We are continuing to investigate and implement mitigations. Aug 31, 17:14:47 GMT+0 - Investigating - We are currently investigating this issue with OpenAI. We are seeing some inconsistent response times from OpenAI. Aug 31, 17:07:57 GMT+0 - Investigating - We are currently experiencing elevated error rates and API hangs communicating with OpenAI. We are investigating the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>02:43:51</var> GMT+0</small><br><strong>Resolved</strong> -
  We are continuing to use Anthropic for all agent responses as we monitor OpenAI&#039;s recovery. We will return to normal operation once API responsiveness returns to expected baseline..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>22:51:45</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to use Anthropic for all agent responses as we monitor OpenAI API incident response and recovery. Follow OpenAI&#039;s status updates here: &lt;https://status.openai.com/incidents/01M1CYZDD84XD0H56XNEV2PT98&gt;.</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>21:34:40</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to use Anthropic for all agent responses as we monitor OpenAI API recovery..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>20:16:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to observe issues with OpenAI API responsiveness, so will maintain failover to Anthropic models and continue monitoring..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>19:43:53</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are recording improved API responsiveness from OpenAI and are evaluating a progressive rollback to normal operations..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>19:17:54</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have completed failing remaining inference activity to Anthropic and are continuing to monitor OpenAI endpoints for recovery. .</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>18:58:57</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to failover to Anthropic and are implementing other mitigations..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>18:26:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to failover to Anthropic models for remaining affected agent behaviors and monitoring rollout..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:45:26</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to observe inconsistent response latencies with OpenAI endpoints. We are deploying a mitigation to failover all remaining affected model usages to Anthropic..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:32:44</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are seeing consistent availability from the OpenAI endpoint, but performance remains degraded. We are continuing to monitor the situation..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:21:42</var> GMT+0</small><br><strong>Investigating</strong> -
  We are continuing to see fluctuating availability and response times from OpenAI across multiple model classes. We are continuing to investigate and implement mitigations..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:14:47</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this issue with OpenAI. We are seeing some inconsistent response times from OpenAI..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:07:57</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently experiencing elevated error rates and API hangs communicating with OpenAI. We are investigating the issue..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 31 Aug 2026 17:07:57 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmthhrvz305im1bmvmk3g77z2</link>
  <guid>https://legacystatus.serval.com/incident/cmthhrvz305im1bmvmk3g77z2</guid>
</item>

<item>
  <title>Issues creating tickets and AI responses in Serval</title>
  <description>
    Type: Incident
    Duration: 41 minutes

    Affected Components: Application
    Aug 25, 01:31:34 GMT+0 - Resolved - This incident has been resolved. Aug 25, 01:09:41 GMT+0 - Monitoring - We have implemented a fix and are observing availability is recovering. We are currently monitoring recovery. Aug 25, 00:54:01 GMT+0 - Identified - We have identified a root cause and are now implementing a fix. Aug 25, 00:50:09 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>01:31:34</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>01:09:41</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have implemented a fix and are observing availability is recovering. We are currently monitoring recovery..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>00:54:01</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified a root cause and are now implementing a fix..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>00:50:09</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 25 Aug 2026 00:50:09 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmt7y7bo70d3s0knht4w3i5yr</link>
  <guid>https://legacystatus.serval.com/incident/cmt7y7bo70d3s0knht4w3i5yr</guid>
</item>

<item>
  <title>Intermittent connectivity issues with EU1 shard</title>
  <description>
    Type: Incident
    Duration: 58 minutes

    Affected Components: Application
    Aug 20, 11:24:56 GMT+0 - Resolved - This incident has been resolved. Aug 20, 11:02:46 GMT+0 - Monitoring - We have deployed a fix and are monitoring for service recovery and stability. Aug 20, 10:27:14 GMT+0 - Identified - We have identified an issue causing intermittent connectivity issues with our EU deployment. We are working to implement a fix. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 58 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>11:24:56</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>11:02:46</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have deployed a fix and are monitoring for service recovery and stability..</p>
<p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>10:27:14</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified an issue causing intermittent connectivity issues with our EU deployment. We are working to implement a fix..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 20 Aug 2026 10:27:14 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmt1dm7e90b7i0kmelh25qxjb</link>
  <guid>https://legacystatus.serval.com/incident/cmt1dm7e90b7i0kmelh25qxjb</guid>
</item>

<item>
  <title>Issues accessing Serval</title>
  <description>
    Type: Incident
    Duration: 3 hours and 10 minutes

    Affected Components: Application, Workflows
    Aug 7, 08:41:04 GMT+0 - Resolved - This incident has been resolved. Aug 7, 08:01:17 GMT+0 - Monitoring - We have implemented mitigations for issues impacting availability and are monitoring recovery. Aug 7, 07:48:33 GMT+0 - Identified - We have identified additional contributing factors that are impacting Serval availability. We are working to restore service and will provide updates as they become available. Aug 7, 07:04:14 GMT+0 - Monitoring - We have deployed the fix and are monitoring service recovery. Aug 7, 06:15:00 GMT+0 - Identified - We are deploying the fix and monitoring the result. Aug 7, 05:45:00 GMT+0 - Identified - We have identified the root cause of the availability issue and are implementing a fix. Aug 7, 05:30:52 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>08:41:04</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>08:01:17</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have implemented mitigations for issues impacting availability and are monitoring recovery..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>07:48:33</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified additional contributing factors that are impacting Serval availability. We are working to restore service and will provide updates as they become available..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>07:04:14</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have deployed the fix and are monitoring service recovery..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>06:15:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are deploying the fix and monitoring the result..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>05:45:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the root cause of the availability issue and are implementing a fix..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>05:30:52</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 7 Aug 2026 05:30:52 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmsilk68x09560kpq7g1ghx3q</link>
  <guid>https://legacystatus.serval.com/incident/cmsilk68x09560kpq7g1ghx3q</guid>
</item>

<item>
  <title>Issues loading tickets</title>
  <description>
    Type: Incident
    Duration: 48 minutes

    Affected Components: Application
    Jul 30, 19:28:02 GMT+0 - Resolved - This incident has been resolved. We are implementing long term remediations. Jul 30, 19:07:11 GMT+0 - Monitoring - We are continuing to monitor recovery. Performance has recovered to baseline. Jul 30, 18:55:01 GMT+0 - Monitoring - We have applied a fix and are monitoring for service recovery. Service performance is degraded but recovering. Jul 30, 18:45:00 GMT+0 - Investigating - We are currently investigating this incident. Jul 30, 18:39:37 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 48 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>19:28:02</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. We are implementing long term remediations..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>19:07:11</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to monitor recovery. Performance has recovered to baseline..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>18:55:01</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied a fix and are monitoring for service recovery. Service performance is degraded but recovering..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>18:45:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>18:39:37</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 30 Jul 2026 18:39:37 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cms7uyibc070a0knzpxfopics</link>
  <guid>https://legacystatus.serval.com/incident/cms7uyibc070a0knzpxfopics</guid>
</item>

<item>
  <title>Elevated error rates with the invalid_prompt error code</title>
  <description>
    Type: Incident
    Duration: 3 days, 12 hours and 51 minutes

    Affected Components: Third Party: OpenAI → APIs → Chat Completions
    Jul 29, 02:20:19 GMT+0 - Resolved - All impacted services have now fully recovered. Jul 29, 01:39:33 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Jul 29, 00:55:27 GMT+0 - Investigating - We are investigating the issue for the listed services. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 12 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>02:20:19</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>01:39:33</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied the mitigation and are monitoring the recovery..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>00:55:27</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 29 Jul 2026 00:55:27 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmthhbdo109y91ao11d4flm7d</link>
  <guid>https://legacystatus.serval.com/incident/cmthhbdo109y91ao11d4flm7d</guid>
</item>

<item>
  <title>We’re seeing elevated latency, timeouts, and interrupted streaming across gpt 5.1 mini model and gpt 4.1 mini</title>
  <description>
    Type: Incident
    Duration: -1 days, -12 hours and -39 minutes

    Affected Components: Third Party: OpenAI → APIs → Chat Completions
    Jul 27, 17:30:00 GMT+0 - Resolved - All impacted services have now fully recovered. Jul 27, 15:30:00 GMT+0 - Investigating - We are investigating the issue for the listed services. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> -1 days, -12 hours and -39 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Resolved</strong> -
  All impacted services have now fully recovered..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating the issue for the listed services..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 27 Jul 2026 18:06:39 +0000</pubDate>
  <link>https://legacystatus.serval.com/incident/cmthhbdn109y81ao1nfostsom</link>
  <guid>https://legacystatus.serval.com/incident/cmthhbdn109y81ao1nfostsom</guid>
</item>

  </channel>
  </rss>