Serval incident

Degraded performance loading workflows

Major Resolved

Serval experienced a major incident on April 22, 2026 affecting Serval and Workflows, lasting 9h 15m. The incident has been resolved; the full update timeline is below.

Started
Apr 22, 2026, 05:15 PM UTC
Resolved
Apr 23, 2026, 02:31 AM UTC
Duration
9h 15m
Detected by Pingoru
Apr 22, 2026, 05:15 PM UTC

Affected components

ServalWorkflows

Update timeline

  1. identified Apr 22, 2026, 05:15 PM UTC

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

  2. monitoring Apr 22, 2026, 05:59 PM UTC

    We implemented a fix and are currently monitoring the result.

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

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

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

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

  7. monitoring Apr 23, 2026, 02:02 AM UTC

    We implemented a fix and are currently monitoring the result.

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