Skyvern Outage History
Skyvern is up right nowPingoru has recorded 23 incidents for Skyvern: 20 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 1 of 720 (0%) |
| May 2026 | 2 | 3 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 0 of 744 (0%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 1 of 509 (0%) |
Incidents, newest first
Minor October 10, 2026 Workflow runs failing to start for runs using saved credentials 1h 4m Skyvern Async Workers
Started Oct 10, 2026, 12:38 AM UTC· resolved Oct 10, 2026, 01:43 AM UTC
- monitoring Oct 10, 2026, 12:38 AM UTC
Starting at approximately 4:45 PM PT (23:45 UTC) on October 9, workflow runs that use credentials saved in Skyvern's credential vault failed to start, with the error "Failed to initialize workflow run context." The cause was an expired authentication secret that Skyvern uses to access its credential storage. This was an issue on our side, and customers do not need to take any action. We replaced the secret and restarted the affected services at approximately 5:35 PM PT (00:35 UTC). New runs are now starting normally. Runs that failed to start during this window did not execute. Please re-run any affected runs during this period. We are monitoring and will post a final update once we confirm everything is stable.
- resolved Oct 10, 2026, 01:43 AM UTC
Everything looks healthy. Incident has been resolved.
Major August 6, 2026 Elevated task and workflow failure rates 46m Skyvern Async Workers
Started Aug 06, 2026, 09:44 PM UTC· resolved Aug 06, 2026, 10:30 PM UTC
- identified Aug 06, 2026, 09:44 PM UTC
Starting at approximately 21:20 UTC on August 6, we are seeing elevated failure rates on task and workflow runs. We have identified the root cause: one of our upstream AI model providers began rejecting requests. We are deploying a mitigation.
- identified Aug 06, 2026, 09:44 PM UTC
We are continuing to work on a fix for this issue.
- resolved Aug 07, 2026, 03:54 AM UTC
This incident has been resolved.
Major July 3, 2026 API unavailable — elevated 503 errors on api.skyvern.com 8m Skyvern API, Skyvern Cloud (Web Application)
Started Jul 03, 2026, 01:22 PM UTC· resolved Jul 03, 2026, 01:30 PM UTC
- identified Jul 03, 2026, 01:22 PM UTC
Starting at approximately 13:08 UTC, api.skyvern.com began returning 503 errors and API requests are failing. We have identified the root cause and a fix is currently rolling out. We will provide an update shortly.
- identified Jul 03, 2026, 01:24 PM UTC
We are continuing to work on a fix for this issue.
- resolved Jul 03, 2026, 01:30 PM UTC
Between approximately 12:54 and 13:23 UTC, api.skyvern.com returned 503 errors due to an infrastructure issue affecting our API instances. The issue has been identified and resolved, and all systems are operating normally.
Minor May 17, 2026 Elevated workflow + task run failure 1h 39m Skyvern API, Skyvern Async Workers
Started May 17, 2026, 10:14 AM UTC· resolved May 17, 2026, 11:54 AM UTC
- investigating May 17, 2026, 10:14 AM UTC
We are investigating elevated failure rates on workflow and task runs. Some runs in this window may return a failure status. The platform remains otherwise reachable. We will post the next update within 30 minutes.
- identified May 17, 2026, 10:28 AM UTC
We have identified the cause of the elevated workflow and task run failures and are rolling out a fix. We will post the next update once the impact has subsided.
- monitoring May 17, 2026, 11:22 AM UTC
The fix has been deployed, and we are monitoring for recovery. Workflow and task runs are processing normally.
- resolved May 17, 2026, 11:54 AM UTC
The issue has been fully resolved. Workflow and task runs are processing normally.
Minor May 9, 2026 Skyvern runs are stuck in queued status 53m Skyvern Async Workers
Started May 09, 2026, 11:21 PM UTC· resolved May 10, 2026, 12:14 AM UTC
- identified May 09, 2026, 11:21 PM UTC
Some runs have been stuck in queued status due to bug. We're working on the fix.
- resolved May 10, 2026, 12:14 AM UTC
We have fixed the issue and runs are being processed again.
Major April 27, 2026 DB timeout 37m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Apr 27, 2026, 07:53 PM UTC· resolved Apr 27, 2026, 08:30 PM UTC
- investigating Apr 27, 2026, 07:53 PM UTC
We are currently investigating this issue.
- identified Apr 27, 2026, 08:18 PM UTC
we're rolling back
- monitoring Apr 27, 2026, 08:24 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 27, 2026, 08:30 PM UTC
This incident has been resolved.
Major March 31, 2026 run page not loading 1h 56m Skyvern API, Skyvern Cloud (Web Application)
Started Mar 31, 2026, 07:31 PM UTC· resolved Mar 31, 2026, 09:28 PM UTC
- identified Mar 31, 2026, 07:31 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 31, 2026, 07:46 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 31, 2026, 09:28 PM UTC
This incident has been resolved.
Minor March 28, 2026 Workflow runs intermittently stuck in "queued" status 8h 24m Skyvern Async Workers
Started Mar 28, 2026, 09:46 AM UTC· resolved Mar 28, 2026, 06:10 PM UTC
- identified Mar 28, 2026, 09:46 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 28, 2026, 06:10 PM UTC
Resolved — A subset of workflow runs were stuck in "queued" status due to a worker infrastructure issue. We've addressed the issue. impacted stuck runs are marked as failed.
Critical March 21, 2026 Scheduled Downtime from 11pm Mar 20th - 12:30am Mar 21st 2026 (Pacific Time) 1h 25m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Mar 21, 2026, 06:07 AM UTC· resolved Mar 21, 2026, 07:32 AM UTC
- monitoring Mar 21, 2026, 06:07 AM UTC
We're performing database maintenance to improve reliability. - 11:00 PM PT, Mar 20 — Async workers begin scaling down. New agent run requests will be queued but won't be processed for approximately one hour. - 12:00–12:10 AM PT, Mar 21 — Database restart (~5–10 minutes). The API and cloud app will be unavailable during this window. - ~12:10 AM PT, Mar 21 — All services restored.
- resolved Mar 21, 2026, 07:32 AM UTC
Database maintenance is completed. All services are restored.
Minor February 19, 2026 Authentication Provider (Clerk) Outage - Degraded Login 2h 17m Skyvern Cloud (Web Application)
Started Feb 19, 2026, 04:31 PM UTC· resolved Feb 19, 2026, 06:49 PM UTC
- investigating Feb 19, 2026, 04:31 PM UTC
We are experiencing degraded performance due to an outage with our authentication provider (Clerk). Users may experience slow or failed login attempts, and API requests may time out. We are actively monitoring the situation and will provide updates every 30 minutes.
- identified Feb 19, 2026, 05:07 PM UTC
The issue has been identified. The impact is only on Skyvern Cloud UI. We have to wait for our auth provider (clerk.com status page: https://status.clerk.com/) to recover.
- monitoring Feb 19, 2026, 05:10 PM UTC
We're seeing recovery. We will keep monitoring.
- resolved Feb 19, 2026, 06:49 PM UTC
The authentication provider (Clerk) outage has been resolved. All login and API services are fully operational. No action is required from users. We apologize for the inconvenience.
Major February 16, 2026 Elevated API & Agent Run Errors 1h 34m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Feb 16, 2026, 11:15 PM UTC· resolved Feb 17, 2026, 12:50 AM UTC
- identified Feb 16, 2026, 11:15 PM UTC
We're experiencing an elevated level of API & Agent errors. We see a lot of database errors. We're working on a fix.
- monitoring Feb 17, 2026, 12:37 AM UTC
Our service and agents have recovered. We will keep monitoring
- resolved Feb 17, 2026, 12:50 AM UTC
This incident has been resolved.
Minor February 15, 2026 Skyvern Agent Runs Are Getting Stuck 2h 25m Skyvern Async Workers
Started Feb 15, 2026, 11:14 PM UTC· resolved Feb 16, 2026, 01:40 AM UTC
- investigating Feb 15, 2026, 11:14 PM UTC
We are currently investigating this issue.
- monitoring Feb 15, 2026, 11:47 PM UTC
One of our db role ran into trouble connecting to DB (supabase). We've fixed it and now runs are back to work. We'll keep monitoring
- monitoring Feb 15, 2026, 11:47 PM UTC
We are continuing to monitor for any further issues.
- resolved Feb 16, 2026, 01:40 AM UTC
This incident has been resolved.
Critical February 3, 2026 Database outage 3h 45m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Feb 03, 2026, 08:24 AM UTC· resolved Feb 03, 2026, 12:09 PM UTC
- identified Feb 03, 2026, 08:24 AM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 03, 2026, 08:41 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 03, 2026, 09:16 AM UTC
We've fixed a deploy. We're actively monitoring the issue
- investigating Feb 03, 2026, 11:20 AM UTC
We are currently investigating this issue.
- identified Feb 03, 2026, 11:27 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 03, 2026, 12:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 03, 2026, 12:09 PM UTC
This incident has been resolved.
Major January 31, 2026 DB Restart Currently in progress 3h 17m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Jan 31, 2026, 04:36 AM UTC· resolved Jan 31, 2026, 07:53 AM UTC
- investigating Jan 31, 2026, 04:36 AM UTC
We are currently investigating this issue.
- monitoring Jan 31, 2026, 06:24 AM UTC
We had a DB outage for 10 minutes. We have identified the issue and fixed it.
- resolved Jan 31, 2026, 07:53 AM UTC
This incident has been resolved.
Minor January 20, 2026 Skyvern captcha solver is currently degraded 11h 45m Skyvern Async Workers
Started Jan 20, 2026, 05:37 PM UTC· resolved Jan 21, 2026, 05:22 AM UTC
- investigating Jan 20, 2026, 05:37 PM UTC
We are currently investigating this issue.
- resolved Jan 21, 2026, 05:22 AM UTC
This incident has been resolved.
Major December 16, 2025 Skyvern API service outage. API Latency is up and some requests are being dropped. 5h 2m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Dec 16, 2025, 05:57 PM UTC· resolved Dec 16, 2025, 10:59 PM UTC
- identified Dec 16, 2025, 05:57 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Dec 16, 2025, 08:22 PM UTC
Our redis cluster was down. We found the root cause and fixed it. Our API service is back. Our there's a backup in our async worker queue. We're ramping up our workers to drain the jobs in the queue. ETA: 6 hours to fully recover.
- resolved Dec 16, 2025, 10:59 PM UTC
We have fully recovered and drained runs in our queue.
Major December 15, 2025 Skyvern experiencing large number of errors 1h 20m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Dec 15, 2025, 04:22 PM UTC· resolved Dec 15, 2025, 05:42 PM UTC
- investigating Dec 15, 2025, 04:22 PM UTC
We are currently investigating this issue.
- investigating Dec 15, 2025, 04:22 PM UTC
We are continuing to investigate this issue.
- monitoring Dec 15, 2025, 04:49 PM UTC
There was a traffic spike and we had database errors for 10 minutes. We have identified the issue and mitigated it. There's a 10-20 minute latency in our agent queue right now.
- resolved Dec 15, 2025, 05:42 PM UTC
Skyvern has cleared the backed up jobs in our queue. We're have recovered and resolved the incident
Major December 11, 2025 Skyvern Agent Queue Slow 6h 59m Skyvern Async Workers
Started Dec 11, 2025, 04:05 PM UTC· resolved Dec 11, 2025, 11:05 PM UTC
- identified Dec 11, 2025, 04:05 PM UTC
Our agent runs are experiencing slow DB performance right now.
- monitoring Dec 11, 2025, 05:06 PM UTC
Our processing speed is catching up. There is still an half hour to 2 hour delay to process new runs.
- resolved Dec 11, 2025, 11:05 PM UTC
This incident has been resolved.
Major December 1, 2025 Skyvern Service Degraded 3h 26m Skyvern API, Skyvern Async Workers
Started Dec 01, 2025, 04:29 PM UTC· resolved Dec 01, 2025, 07:56 PM UTC
- identified Dec 01, 2025, 04:29 PM UTC
The issue has been identified and a fix is being implemented.
- identified Dec 01, 2025, 04:30 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 01, 2025, 05:03 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Dec 01, 2025, 05:05 PM UTC
API service has recovered. Our database had a major timeout issue which caused downtime in our API services. After database was recovered, we scaled up our api services and everything should be back.
- resolved Dec 01, 2025, 07:56 PM UTC
Our platform seems stable for the past 3 hours and the original issue has not returned. Marking resolved.
Minor November 25, 2025 Elevated queue times 1h 33m Skyvern API
Started Nov 25, 2025, 12:03 AM UTC· resolved Nov 25, 2025, 01:36 AM UTC
- investigating Nov 25, 2025, 12:03 AM UTC
We are currently investigating this issue.
- investigating Nov 25, 2025, 01:20 AM UTC
We are continuing to investigate this issue.
- resolved Nov 25, 2025, 01:36 AM UTC
This incident has been resolved
Major October 20, 2025 Stuck Task And Workflow Runs - Impacted By AWS Outage 14h 57m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Oct 20, 2025, 07:49 AM UTC· resolved Oct 20, 2025, 10:46 PM UTC
- investigating Oct 20, 2025, 07:49 AM UTC
We are currently investigating this issue.
- 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
- 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)
- identified Oct 20, 2025, 08:02 AM UTC
Our browsers are impacted and failing to start.
- 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]
- monitoring Oct 20, 2025, 09:33 PM UTC
We're seeing recoveries. Started ramping up our infrastructure to process agent runs.
- 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.
- resolved Oct 20, 2025, 10:46 PM UTC
We've fully recovered
Minor March 10, 2025 Skyvern Database Is Partially Degraded 7h 35m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Mar 10, 2025, 12:09 PM UTC· resolved Mar 10, 2025, 07:45 PM UTC
- investigating Mar 10, 2025, 12:09 PM UTC
We're experiencing issues with our database providers again and we're looking into it. Impact: - Task and workflow runs might be delayed. - Higher error rate in agent execution - Higher error rate in the Skyvern Cloud app and API.
- resolved Mar 10, 2025, 07:45 PM UTC
The issue has been resolved
Major March 8, 2025 Skyvern Database Is Partially Down 7h 12m Skyvern API, Skyvern Cloud (Web Application), Skyvern Async Workers
Started Mar 08, 2025, 12:14 AM UTC· resolved Mar 08, 2025, 07:26 AM UTC
- identified Mar 08, 2025, 12:14 AM UTC
Our database provider, supabase, has an ongoing incident (https://status.supabase.com/incidents/6ndq3cr0kt5q) and it's impacting Skyvern's ability to serve some API requests as well as running the asynchronous tasks in our workers.
- identified Mar 08, 2025, 12:15 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 08, 2025, 12:35 AM UTC
Our worker processing queue is backed up a little bit. Task and workflow processing is delayed as a result.
- monitoring Mar 08, 2025, 06:49 AM UTC
Error has been resolved. We're closely monitoring errors.
- monitoring Mar 08, 2025, 07:25 AM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 08, 2025, 07:26 AM UTC
The incident has been resolved
- resolved Mar 08, 2025, 07:26 AM UTC
This incident has been resolved.