- 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
-
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.
-
resolved Sep 19, 2026, 06:56 PM UTC
This was resolved by a rate limit increase.
Read the full incident report →
- 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
-
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
-
resolved Sep 18, 2026, 11:35 PM UTC
This issue is resolved. WorkOS has recovered from their API errors.
Read the full incident report →
- 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
-
investigating Sep 18, 2026, 08:35 PM UTC
We are currently investigating this incident.
-
identified Sep 18, 2026, 08:36 PM UTC
We are continuing to work on a fix for this incident.
-
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. 
-
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).
-
resolved Sep 18, 2026, 10:16 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
monitoring Sep 17, 2026, 09:20 PM UTC
We have applied the mitigation and are monitoring the recovery.
-
resolved Sep 17, 2026, 09:50 PM UTC
All impacted services have now fully recovered.
Read the full incident report →
- 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
-
investigating Sep 16, 2026, 10:37 PM UTC
We are currently investigating this incident.
-
monitoring Sep 16, 2026, 11:06 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Sep 16, 2026, 11:37 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Sep 14, 2026, 06:51 AM UTC
We are currently investigating this incident.
-
identified Sep 14, 2026, 07:08 AM UTC
We are continuing to work on a fix for this incident.
-
monitoring Sep 14, 2026, 07:28 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Sep 14, 2026, 07:29 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
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
-
resolved Sep 11, 2026, 11:21 AM UTC
All impacted services have now fully recovered.
Read the full incident report →
- 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
-
investigating Sep 08, 2026, 09:14 PM UTC
We are currently investigating this incident.
-
identified Sep 08, 2026, 09:19 PM UTC
We are continuing to work on a fix for this incident.
-
monitoring Sep 08, 2026, 09:39 PM UTC
Latency is recovering after working through a backlog of events. We're monitoring.
-
resolved Sep 08, 2026, 09:51 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Sep 06, 2026, 06:30 AM UTC
We are currently investigating this incident.
-
resolved Sep 06, 2026, 07:21 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Sep 04, 2026, 07:57 PM UTC
We are currently investigating this incident.
-
identified Sep 04, 2026, 08:11 PM UTC
We have identified a root cause and are implementing a fix.
-
monitoring Sep 04, 2026, 08:13 PM UTC
We implemented a fix and are currently monitoring recovery.
-
monitoring Sep 04, 2026, 08:18 PM UTC
We are observing a return to normal behavior and are continuing to monitor recovery.
-
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 →
- Detected by Pingoru
- Sep 03, 2026, 10:30 AM UTC
- Resolved
- Sep 03, 2026, 11:00 AM UTC
- Duration
- 30m
Affected: Application
Timeline · 2 updates
-
investigating Sep 03, 2026, 10:30 AM UTC
We are currently investigating this incident.
-
resolved Sep 03, 2026, 11:00 AM UTC
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.
Read the full incident report →
- 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
-
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.
-
monitoring Aug 31, 2026, 11:13 PM UTC
We have applied a mitigation and are monitoring recovery.
-
monitoring Sep 01, 2026, 01:46 AM UTC
We have applied the mitigation and are monitoring the recovery.
-
identified Sep 01, 2026, 03:15 PM UTC
We have identified elevated latencies impacting Responses API on the US endpoint.
-
identified Sep 01, 2026, 05:36 PM UTC
We are implementing the mitigation.
-
monitoring Sep 01, 2026, 06:09 PM UTC
We have applied the mitigation and are monitoring the recovery.
-
resolved Sep 01, 2026, 07:05 PM UTC
All impacted services have now fully recovered.
Read the full incident report →
- 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 →
- 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
-
investigating Aug 25, 2026, 12:50 AM UTC
We are currently investigating this incident.
-
identified Aug 25, 2026, 12:54 AM UTC
We have identified a root cause and are now implementing a fix.
-
monitoring Aug 25, 2026, 01:09 AM UTC
We have implemented a fix and are observing availability is recovering. We are currently monitoring recovery.
-
resolved Aug 25, 2026, 01:31 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
monitoring Aug 20, 2026, 11:02 AM UTC
We have deployed a fix and are monitoring for service recovery and stability.
-
resolved Aug 20, 2026, 11:24 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Aug 07, 2026, 05:30 AM UTC
We are currently investigating this incident.
-
identified Aug 07, 2026, 05:45 AM UTC
We have identified the root cause of the availability issue and are implementing a fix.
-
identified Aug 07, 2026, 06:15 AM UTC
We are deploying the fix and monitoring the result.
-
monitoring Aug 07, 2026, 07:04 AM UTC
We have deployed the fix and are monitoring service recovery.
-
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.
-
monitoring Aug 07, 2026, 08:01 AM UTC
We have implemented mitigations for issues impacting availability and are monitoring recovery.
-
resolved Aug 07, 2026, 08:41 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jul 30, 2026, 06:39 PM UTC
We are currently investigating this incident.
-
investigating Jul 30, 2026, 06:45 PM UTC
We are currently investigating this incident.
-
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.
-
monitoring Jul 30, 2026, 07:07 PM UTC
We are continuing to monitor recovery. Performance has recovered to baseline.
-
resolved Jul 30, 2026, 07:28 PM UTC
This incident has been resolved. We are implementing long term remediations.
Read the full incident report →
- Detected by Pingoru
- Jul 05, 2026, 10:59 PM UTC
- Resolved
- Jul 05, 2026, 11:23 PM UTC
- Duration
- 24m
Affected: Application
Timeline · 3 updates
-
investigating Jul 05, 2026, 10:59 PM UTC
We are currently investigating this incident.
-
monitoring Jul 05, 2026, 11:14 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 05, 2026, 11:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 05:45 PM UTC
- Resolved
- Jun 30, 2026, 05:45 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 30, 2026, 05:45 PM UTC
Type: Incident Duration: 52 minutes Affected Components: Application, Workflows Jun 30, 17:45:00 GMT+0 - Investigating - We are currently investigating this incident. Jun 30, 18:12:50 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 30, 18:37:17 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 03:07 PM UTC
- Resolved
- May 14, 2026, 03:41 PM UTC
- Duration
- 33m
Affected: ApplicationWorkflows
Timeline · 2 updates
-
monitoring May 14, 2026, 03:07 PM UTC
Slack is having an outage, so messages are not being routed to Serval. Latest status is available here:
-
resolved May 14, 2026, 03:41 PM UTC
This incident has been resolved by Slack.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 09:42 PM UTC
- Resolved
- May 12, 2026, 10:12 PM UTC
- Duration
- 30m
Timeline · 2 updates
-
investigating May 12, 2026, 09:42 PM UTC
Serval is not creating tickets when emails are sent to existing intake addresses. We are currently investigating this incident.
-
resolved May 12, 2026, 10:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 10, 2026, 04:02 AM UTC
- Resolved
- May 10, 2026, 04:04 AM UTC
- Duration
- 1m
Affected: Application
Timeline · 2 updates
-
identified May 10, 2026, 04:02 AM UTC
We have identified an issue with an upstream provider impacting help agent responses. We are currently working on a fix.
-
resolved May 10, 2026, 04:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 09:58 PM UTC
- Resolved
- Apr 24, 2026, 10:40 PM UTC
- Duration
- 41m
Affected: ServalApplicationWorkflows
Timeline · 3 updates
-
investigating Apr 24, 2026, 09:58 PM UTC
We are currently investigating this incident.
-
monitoring Apr 24, 2026, 10:18 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Apr 24, 2026, 10:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 05:15 PM UTC
- Resolved
- Apr 23, 2026, 02:31 AM UTC
- Duration
- 9h 15m
Affected: ServalWorkflows
Timeline · 8 updates
-
identified Apr 22, 2026, 05:15 PM UTC
We are continuing to work on a fix for this incident.
-
monitoring Apr 22, 2026, 05:59 PM UTC
We implemented a fix and are currently monitoring the result.
-
monitoring Apr 22, 2026, 10:00 PM UTC
We have mitigated issues contributing to performance and workflow service availability and are continuing to investigate further reports of degraded performance. We will provide an update at 4 PM PT or earlier as our mitigation efforts progress.
-
monitoring Apr 22, 2026, 11:14 PM UTC
We are continuing to work on performance improvements. We will provide an update at 5 PM PT or earlier as our mitigation efforts progress.
-
monitoring Apr 23, 2026, 12:06 AM UTC
We are continuing to work on performance improvements. We will provide an update at 6 PM PT or earlier as our mitigation efforts progress.
-
monitoring Apr 23, 2026, 12:59 AM UTC
We are working on additional fixes to improve workflow performance and availability. We will provide an update at 7PM or earlier as work progresses.
-
monitoring Apr 23, 2026, 02:02 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Apr 23, 2026, 02:31 AM UTC
We have confirmed fixes have resolved performance issues. We are implementing performance fixes across all services to improve performance and reliability moving forward.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 12:39 AM UTC
- Resolved
- Apr 08, 2026, 12:39 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 08, 2026, 12:39 AM UTC
Type: Incident Duration: 24 minutes Affected Components: Workflows Apr 8, 01:03:37 GMT+0 - Resolved - This incident has been resolved. Apr 8, 00:39:57 GMT+0 - Identified - We are working on a fix for this incident. Apr 8, 00:42:19 GMT+0 - Monitoring - We implemented a fix and are currently monitoring recovery of workflow systems.
Read the full incident report →
