Skyvern incident

Stuck Task And Workflow Runs - Impacted By AWS Outage

Major Resolved View vendor source →

Skyvern experienced a major incident on October 20, 2025 affecting Skyvern API and Skyvern Cloud (Web Application) and 1 more component, lasting 14h 56m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 07:50 AM UTC
Resolved
Oct 20, 2025, 10:46 PM UTC
Duration
14h 56m
Detected by Pingoru
Oct 20, 2025, 07:50 AM UTC

Affected components

Skyvern APISkyvern Cloud (Web Application)Skyvern Async Workers

Update timeline

  1. investigating Oct 20, 2025, 07:49 AM UTC

    We are currently investigating this issue.

  2. investigating Oct 20, 2025, 07:50 AM UTC

    Our task/workflow processing infrastructure is running behind due to AWS's major outage in us-east-1: https://health.aws.amazon.com/health/status

  3. identified Oct 20, 2025, 07:50 AM UTC

    The issue has been identified - aws has an outage in us-east-1 (https://health.aws.amazon.com/health/status)

  4. identified Oct 20, 2025, 08:02 AM UTC

    Our browsers are impacted and failing to start.

  5. identified Oct 20, 2025, 05:52 PM UTC

    We're still impacted by the AWS outage. All the runs are stuck at the "created" status. These runs won't be executed going forward and we're planning to cancel the stuck runs once the incident is resolved. Sorry for the inconvenience and please reach out to us if you need any help [email protected]

  6. monitoring Oct 20, 2025, 09:33 PM UTC

    We're seeing recoveries. Started ramping up our infrastructure to process agent runs.

  7. monitoring Oct 20, 2025, 10:04 PM UTC

    Skyvern Browser Sessions have recovered. There's a long queue to process the backed up runs. It'll take 4-5 hours for us to catch up processing the agent runs in real time.

  8. resolved Oct 20, 2025, 10:46 PM UTC

    We've fully recovered