Daytona Reliability | ComputeSDK

All passedBlipsDownNot counted

Participant	Uptime	Downtime	p50		Details
Daytona	96.875%	45 min	625ms

Hover a cell for its numbers. Click a cell to see those checks.

Every check

Fri, Nov 13

96.875% uptime1133 passed45 failed0 not counted625ms p5016.00s p95

00:00

Incidents

Down
Fri, Nov 13 16:13 UTC → Fri, Nov 13 16:20 UTC · 8 min · 7 failed
Error
Down
Fri, Nov 13 15:43 UTC → Fri, Nov 13 15:47 UTC · 5 min · 4 failed
cleanup_failed
Down
Fri, Nov 13 15:33 UTC → Fri, Nov 13 15:38 UTC · 6 min · 5 failed
cleanup_failed
Down
Fri, Nov 13 15:18 UTC → Fri, Nov 13 15:21 UTC · 4 min · 3 failed
cleanup_failed

What went wrong (3 errors)

22×cleanup_failed
15×step_timeout
8×Error

Methodology

Every minute, we create a Daytona sandbox, run a small workload in it and destroy it. A check fails if any step errors. Each counted failed check counts as 1 minute of downtime out of the 525,600 minutes in a year. Checks our scheduler skipped never count against a provider. Manually excluded failures appear as “Not counted” with a reason and do not affect uptime or incidents. All times are UTC.

Run a sandbox on Daytona.

Start with $5 in free credit. The CLI handles sign-in and setup. Bring your own keys whenever you want.

Terminal

compute new daytona

Explore Sandbox Router

Uptime

Every check

Incidents

Methodology

Run a sandbox on Daytona.