Serval Outage History

Serval is up right now

Serval had 40 outages in the last 2 years totaling 60h 36m of downtime — averaging 1.6 incidents per month.

There were 40 Serval outages since October 22, 2025 totaling 60h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.serval.com

Minor October 6, 2026

Errors processing large PDFs in the Responses API

Detected by Pingoru
Oct 06, 2026, 03:45 PM UTC
Resolved
Oct 06, 2026, 08:11 PM UTC
Duration
4h 25m
Affected: Third Party: OpenAI (Third Party: OpenAI → APIs → Responses)
Timeline · 3 updates
  1. investigating Oct 06, 2026, 03:45 PM UTC

    We are investigating the issue for the listed services.

  2. identified Oct 06, 2026, 04:39 PM UTC

    We are implementing the mitigation.

  3. resolved Oct 06, 2026, 08:11 PM UTC

    All impacted services have now fully recovered.

Read the full incident report →

Minor September 30, 2026

Elevated latency for some API requests

Detected by Pingoru
Sep 30, 2026, 05:05 PM UTC
Resolved
Sep 30, 2026, 08:35 PM UTC
Duration
3h 30m
Affected: Third Party: OpenAI (Third Party: OpenAI → APIs → Chat Completions)Third Party: OpenAI (Third Party: OpenAI → APIs → Responses)
Timeline · 5 updates
  1. identified Sep 30, 2026, 05:05 PM UTC

    We have identified that users are experiencing elevated latency for the impacted services. We are working on implementing a mitigation.

  2. identified Sep 30, 2026, 05:13 PM UTC

    We have identified that users are experiencing elevated latency for the impacted services. We are working on implementing a mitigation.

  3. identified Sep 30, 2026, 05:51 PM UTC

    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.

  4. monitoring Sep 30, 2026, 06:21 PM UTC

    We have applied the mitigation and are monitoring the recovery.

  5. resolved Sep 30, 2026, 08:35 PM UTC

    All impacted services have now fully recovered.

Read the full incident report →

Minor September 29, 2026

Elevated errors across ChatGPT, Codex, and the API including the Agents API

Detected by Pingoru
Sep 29, 2026, 05:52 PM UTC
Resolved
Sep 29, 2026, 11:14 PM UTC
Duration
5h 21m
Affected: Third Party: OpenAI (Third Party: OpenAI → APIs → Chat Completions)Third Party: OpenAI (Third Party: OpenAI → APIs → Responses)
Timeline · 8 updates
  1. investigating Sep 29, 2026, 05:52 PM UTC

    We’re investigating elevated errors affecting ChatGPT, Codex, and the 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.

  2. investigating Sep 29, 2026, 06:24 PM UTC

    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.

  3. investigating Sep 29, 2026, 07:08 PM UTC

    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.

  4. monitoring Sep 29, 2026, 07:39 PM UTC

    We have applied the mitigation and are monitoring the recovery.

  5. monitoring Sep 29, 2026, 09:09 PM UTC

    We have applied the mitigation and are monitoring the recovery.

  6. monitoring Sep 29, 2026, 10:03 PM UTC

    We have applied the mitigation and are monitoring the recovery.

  7. monitoring Sep 29, 2026, 10:47 PM UTC

    We have applied the mitigation and are monitoring the recovery.

  8. resolved Sep 29, 2026, 11:14 PM UTC

    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.

Read the full incident report →

Minor September 29, 2026

Workflow runs failing to start, Degraded Catalyst performance

Detected by Pingoru
Sep 29, 2026, 04:00 PM UTC
Resolved
Sep 29, 2026, 06:10 PM UTC
Duration
2h 10m
Affected: WorkflowsThird Party: Anthropic → Claude API (api.anthropic.com)
Timeline · 2 updates
  1. identified Sep 29, 2026, 04:00 PM UTC

    We are continuing to work on a fix for this incident.

  2. resolved Sep 29, 2026, 06:10 PM UTC

    We implemented a fix and are currently monitoring the result.

Read the full incident report →

Minor September 19, 2026

Email delivery issues

Detected by Pingoru
Sep 19, 2026, 05:59 PM UTC
Resolved
Sep 19, 2026, 06:56 PM UTC
Duration
57m
Affected: Application
Timeline · 2 updates
  1. investigating Sep 19, 2026, 05:59 PM UTC

    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.

  2. resolved Sep 19, 2026, 06:56 PM UTC

    This was resolved by a rate limit increase.

Read the full incident report →

Major September 18, 2026

SSO Login Issues

Detected by Pingoru
Sep 18, 2026, 11:07 PM UTC
Resolved
Sep 18, 2026, 11:35 PM UTC
Duration
27m
Affected: Login
Timeline · 2 updates
  1. investigating Sep 18, 2026, 11:07 PM UTC

    We are currently investigating issues with SSO-based login. It appears to be an issue with a downstream auth-provider, WorkOS. See

  2. resolved Sep 18, 2026, 11:35 PM UTC

    This issue is resolved. WorkOS has recovered from their API errors.

Read the full incident report →

Major September 18, 2026

Issues with Email Intake

Detected by Pingoru
Sep 18, 2026, 08:35 PM UTC
Resolved
Sep 18, 2026, 10:16 PM UTC
Duration
1h 40m
Affected: Application
Timeline · 5 updates
  1. investigating Sep 18, 2026, 08:35 PM UTC

    We are currently investigating this incident.

  2. identified Sep 18, 2026, 08:36 PM UTC

    We are continuing to work on a fix for this incident.

  3. monitoring Sep 18, 2026, 09:10 PM UTC

    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)

  4. monitoring Sep 18, 2026, 09:33 PM UTC

    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).

  5. resolved Sep 18, 2026, 10:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 17, 2026

We are seeing elevated error rates across API models

Detected by Pingoru
Sep 17, 2026, 09:29 PM UTC
Resolved
Sep 17, 2026, 09:50 PM UTC
Duration
21m
Affected: Third Party: OpenAI (Third Party: OpenAI → APIs → Chat Completions)Third Party: OpenAI (Third Party: OpenAI → APIs → Responses)
Timeline · 3 updates
  1. identified Sep 17, 2026, 08:20 PM UTC

    We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

  2. monitoring Sep 17, 2026, 09:20 PM UTC

    We have applied the mitigation and are monitoring the recovery.

  3. resolved Sep 17, 2026, 09:50 PM UTC

    All impacted services have now fully recovered.

Read the full incident report →

Minor September 16, 2026

Tickets Failing to Create

Detected by Pingoru
Sep 16, 2026, 10:37 PM UTC
Resolved
Sep 16, 2026, 11:37 PM UTC
Duration
1h
Affected: Application
Timeline · 3 updates
  1. investigating Sep 16, 2026, 10:37 PM UTC

    We are currently investigating this incident.

  2. monitoring Sep 16, 2026, 11:06 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Sep 16, 2026, 11:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 14, 2026

Degraded performance of the help agent

Detected by Pingoru
Sep 14, 2026, 06:51 AM UTC
Resolved
Sep 14, 2026, 07:29 AM UTC
Duration
38m
Affected: Application
Timeline · 4 updates
  1. investigating Sep 14, 2026, 06:51 AM UTC

    We are currently investigating this incident.

  2. identified Sep 14, 2026, 07:08 AM UTC

    We are continuing to work on a fix for this incident.

  3. monitoring Sep 14, 2026, 07:28 AM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Sep 14, 2026, 07:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 11, 2026

Elevated errors for GPT-5.6 Sol on the API

Detected by Pingoru
Sep 11, 2026, 09:08 AM UTC
Resolved
Sep 11, 2026, 11:21 AM UTC
Duration
2h 13m
Affected: Third Party: OpenAI (Third Party: OpenAI → APIs → Chat Completions)Third Party: OpenAI (Third Party: OpenAI → APIs → Responses)
Timeline · 3 updates
  1. identified Sep 11, 2026, 09:08 AM UTC

    We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

  2. monitoring Sep 11, 2026, 10:09 AM UTC

    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

  3. resolved Sep 11, 2026, 11:21 AM UTC

    All impacted services have now fully recovered.

Read the full incident report →

Minor September 8, 2026

Increased Latency across Slack, Teams and Workflow Runs

Detected by Pingoru
Sep 08, 2026, 09:14 PM UTC
Resolved
Sep 08, 2026, 09:51 PM UTC
Duration
37m
Affected: ApplicationWorkflows
Timeline · 4 updates
  1. investigating Sep 08, 2026, 09:14 PM UTC

    We are currently investigating this incident.

  2. identified Sep 08, 2026, 09:19 PM UTC

    We are continuing to work on a fix for this incident.

  3. monitoring Sep 08, 2026, 09:39 PM UTC

    Latency is recovering after working through a backlog of events. We're monitoring.

  4. resolved Sep 08, 2026, 09:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 6, 2026

Slow responses from help agent

Detected by Pingoru
Sep 06, 2026, 06:30 AM UTC
Resolved
Sep 06, 2026, 07:21 AM UTC
Duration
50m
Affected: Workflows
Timeline · 2 updates
  1. investigating Sep 06, 2026, 06:30 AM UTC

    We are currently investigating this incident.

  2. resolved Sep 06, 2026, 07:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 4, 2026

Issues with help agent responses and running workflows

Detected by Pingoru
Sep 04, 2026, 07:57 PM UTC
Resolved
Sep 04, 2026, 08:27 PM UTC
Duration
30m
Affected: ApplicationWorkflows
Timeline · 5 updates
  1. investigating Sep 04, 2026, 07:57 PM UTC

    We are currently investigating this incident.

  2. identified Sep 04, 2026, 08:11 PM UTC

    We have identified a root cause and are implementing a fix.

  3. monitoring Sep 04, 2026, 08:13 PM UTC

    We implemented a fix and are currently monitoring recovery.

  4. monitoring Sep 04, 2026, 08:18 PM UTC

    We are observing a return to normal behavior and are continuing to monitor recovery.

  5. resolved Sep 04, 2026, 08:27 PM UTC

    This incident has been mitigated. We are working to implement long-term preventative fixes.

Read the full incident report →

Minor September 3, 2026

Degraded performance with help agent

Detected by Pingoru
Sep 03, 2026, 10:30 AM UTC
Resolved
Sep 03, 2026, 10:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 03, 2026, 10:30 AM UTC

    Type: Incident Duration: 33 minutes Affected Components: Application Sep 3, 10:30:00 GMT+0 - Investigating - We are currently investigating this incident. 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.

Read the full incident report →

Minor August 31, 2026

Elevated latency in the Responses API

Detected by Pingoru
Aug 31, 2026, 10:27 PM UTC
Resolved
Sep 01, 2026, 07:05 PM UTC
Duration
20h 37m
Affected: Third Party: OpenAI (Third Party: OpenAI → APIs → Responses)
Timeline · 7 updates
  1. identified Aug 31, 2026, 10:27 PM UTC

    We have identified an issue causing elevated latency for some Responses API requests. We are working on implementing a mitigation.

  2. monitoring Aug 31, 2026, 11:13 PM UTC

    We have applied a mitigation and are monitoring recovery.

  3. monitoring Sep 01, 2026, 01:46 AM UTC

    We have applied the mitigation and are monitoring the recovery.

  4. identified Sep 01, 2026, 03:15 PM UTC

    We have identified elevated latencies impacting Responses API on the US endpoint.

  5. identified Sep 01, 2026, 05:36 PM UTC

    We are implementing the mitigation.

  6. monitoring Sep 01, 2026, 06:09 PM UTC

    We have applied the mitigation and are monitoring the recovery.

  7. resolved Sep 01, 2026, 07:05 PM UTC

    All impacted services have now fully recovered.

Read the full incident report →

Major August 31, 2026

Third Party: OpenAI provider outage

Detected by Pingoru
Aug 31, 2026, 05:07 PM UTC
Resolved
Sep 01, 2026, 02:43 AM UTC
Duration
9h 35m
Affected: Third Party: OpenAI (Third Party: OpenAI → APIs → Chat Completions)Third Party: OpenAI (Third Party: OpenAI → APIs → Responses)
Timeline · 13 updates

Read the full incident report →

Major August 25, 2026

Issues creating tickets and AI responses in Serval

Detected by Pingoru
Aug 25, 2026, 12:50 AM UTC
Resolved
Aug 25, 2026, 01:31 AM UTC
Duration
41m
Affected: Application
Timeline · 4 updates
  1. investigating Aug 25, 2026, 12:50 AM UTC

    We are currently investigating this incident.

  2. identified Aug 25, 2026, 12:54 AM UTC

    We have identified a root cause and are now implementing a fix.

  3. monitoring Aug 25, 2026, 01:09 AM UTC

    We have implemented a fix and are observing availability is recovering. We are currently monitoring recovery.

  4. resolved Aug 25, 2026, 01:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 20, 2026

Intermittent connectivity issues with EU1 shard

Detected by Pingoru
Aug 20, 2026, 10:27 AM UTC
Resolved
Aug 20, 2026, 11:24 AM UTC
Duration
57m
Affected: Application
Timeline · 3 updates
  1. identified Aug 20, 2026, 10:27 AM UTC

    We have identified an issue causing intermittent connectivity issues with our EU deployment. We are working to implement a fix.

  2. monitoring Aug 20, 2026, 11:02 AM UTC

    We have deployed a fix and are monitoring for service recovery and stability.

  3. resolved Aug 20, 2026, 11:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 7, 2026

Issues accessing Serval

Detected by Pingoru
Aug 07, 2026, 05:30 AM UTC
Resolved
Aug 07, 2026, 08:41 AM UTC
Duration
3h 10m
Affected: ApplicationWorkflows
Timeline · 7 updates
  1. investigating Aug 07, 2026, 05:30 AM UTC

    We are currently investigating this incident.

  2. identified Aug 07, 2026, 05:45 AM UTC

    We have identified the root cause of the availability issue and are implementing a fix.

  3. identified Aug 07, 2026, 06:15 AM UTC

    We are deploying the fix and monitoring the result.

  4. monitoring Aug 07, 2026, 07:04 AM UTC

    We have deployed the fix and are monitoring service recovery.

  5. identified Aug 07, 2026, 07:48 AM UTC

    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.

  6. monitoring Aug 07, 2026, 08:01 AM UTC

    We have implemented mitigations for issues impacting availability and are monitoring recovery.

  7. resolved Aug 07, 2026, 08:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 30, 2026

Issues loading tickets

Detected by Pingoru
Jul 30, 2026, 06:39 PM UTC
Resolved
Jul 30, 2026, 07:28 PM UTC
Duration
48m
Affected: Application
Timeline · 5 updates
  1. investigating Jul 30, 2026, 06:39 PM UTC

    We are currently investigating this incident.

  2. investigating Jul 30, 2026, 06:45 PM UTC

    We are currently investigating this incident.

  3. monitoring Jul 30, 2026, 06:55 PM UTC

    We have applied a fix and are monitoring for service recovery. Service performance is degraded but recovering.

  4. monitoring Jul 30, 2026, 07:07 PM UTC

    We are continuing to monitor recovery. Performance has recovered to baseline.

  5. resolved Jul 30, 2026, 07:28 PM UTC

    This incident has been resolved. We are implementing long term remediations.

Read the full incident report →

Minor July 29, 2026

Elevated error rates with the invalid_prompt error code

Detected by Pingoru
Jul 29, 2026, 12:55 AM UTC
Resolved
Jul 29, 2026, 12:55 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 29, 2026, 12:55 AM UTC

    Type: Incident Duration: 3 days, 12 hours and 51 minutes Affected Components: Third Party: OpenAI → APIs → Chat Completions Jul 29, 00:55:27 GMT+0 - Investigating - We are investigating the issue for the listed services. Jul 29, 01:39:33 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Jul 29, 02:20:19 GMT+0 - Resolved - All impacted services have now fully recovered.

Read the full incident report →

Minor July 27, 2026

We’re seeing elevated latency, timeouts, and interrupted streaming across gpt 5.1 mini model and gpt 4.1 mini

Detected by Pingoru
Jul 27, 2026, 06:06 PM UTC
Resolved
Jul 27, 2026, 06:06 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 27, 2026, 06:06 PM UTC

    Type: Incident Duration: 1 day, 12 hours and 39 minutes Affected Components: Third Party: OpenAI → APIs → Chat Completions Jul 27, 15:30:00 GMT+0 - Investigating - We are investigating the issue for the listed services. Jul 27, 17:30:00 GMT+0 - Resolved - All impacted services have now fully recovered.

Read the full incident report →

Minor July 25, 2026

Elevated error rates

Detected by Pingoru
Jul 25, 2026, 11:35 AM UTC
Resolved
Jul 25, 2026, 11:35 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 25, 2026, 11:35 AM UTC

    Type: Incident Duration: 21 hours and 37 minutes Affected Components: Third Party: OpenAI → APIs → Responses, Third Party: OpenAI → APIs → Chat Completions Jul 25, 11:35:24 GMT+0 - Identified - We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Jul 25, 11:46:39 GMT+0 - Monitoring - We have applied the mitigation and are monitoring the recovery. Jul 25, 11:57:02 GMT+0 - Resolved - All impacted services have now fully recovered.

Read the full incident report →