Reliability Benchmarks

Our reliability benchmark creates a sandbox, runs a workload, and destroys it every minute to test the uptime reliability of sandbox providers. All times are UTC.

All passedBlipsDownMissed (scheduler)Pending
ParticipantUptimeDowntimep50
Schedulerours4.19%16349 missed—
Promigence100%—153ms
Novita100%—821ms
Gravixlayer99.85%1 min257ms
Buddy99.85%1 min459ms
sfcompute99.85%1 min1.09s
Freestyle99.85%1 min1.27s
Upstash99.71%2 min905ms
Railway99.70%2 min5.05s
CreateOS99.57%3 min299ms
Beam99.57%3 min511ms
E2B99.57%3 min1.66s
Isorun99.43%4 min239ms
Sandbox099.29%5 min3.04s
Sail99.29%5 min3.29s
Daytona99.15%6 min418ms
Superserve99.00%7 min447ms
Vercel98.86%8 min1.76s
Tenki98.72%9 min1.02s
Sprites98.58%10 min902ms
Blaxel98.44%11 min498ms
Cloudflare98.44%11 min692ms
Arker98.30%12 min424ms
CodeSandbox98.30%12 min8.27s
Tensorlake97.87%15 min2.25s
Modal97.73%16 min781ms
Mosaic97.45%18 min890ms
Run Cloud97.45%18 min4.40s
Archil97.31%19 min282ms
Namespace96.74%23 min2.23s
Cloud Run96.32%26 min739ms
Miosa95.92%29 min192ms
Declaw76.00%6 min43.66s
Microsandbox40.74%16 min27.58s
Hopx0.00%5 min—
Lightning AI0.00%5 min—
Northflank0.00%5 min—
OpenComputer0.00%5 min—

Hover a cell for its numbers. Click a participant cell to open their checks for that day.

  • MissedAll participants
    Tue, Nov 3 22:33 UTC → Tue, Nov 3 22:36 UTC · 4 min · 0 failed, 3 missed
  • MissedAll participants
    Tue, Oct 27 20:03 UTC → Tue, Nov 3 00:00 UTC · 6 d 3 h · 0 failed, 8877 missed
  • MissedAll participants
    Tue, Oct 27 18:38 UTC → Tue, Oct 27 20:02 UTC · 1 h 25 min · 0 failed, 84 missed
  • MissedAll participants
    Tue, Oct 27 18:17 UTC → Tue, Oct 27 18:37 UTC · 21 min · 0 failed, 20 missed
  • MissedAll participants
    Tue, Oct 27 18:13 UTC → Tue, Oct 27 18:16 UTC · 4 min · 0 failed, 3 missed
  • MissedAll participants
    Tue, Oct 27 17:55 UTC → Tue, Oct 27 18:12 UTC · 18 min · 0 failed, 17 missed
  • MissedAll participants
    Tue, Oct 27 17:43 UTC → Tue, Oct 27 17:52 UTC · 10 min · 0 failed, 9 missed
  • MissedAll participants
    Tue, Oct 27 17:35 UTC → Tue, Oct 27 17:42 UTC · 8 min · 0 failed, 7 missed
  • MissedAll participants
    Tue, Oct 27 17:31 UTC → Tue, Oct 27 17:34 UTC · 4 min · 0 failed, 3 missed
  • MissedAll participants
    Tue, Oct 27 17:22 UTC → Tue, Oct 27 17:30 UTC · 9 min · 0 failed, 8 missed
  • MissedAll participants
    Tue, Oct 27 17:14 UTC → Tue, Oct 27 17:21 UTC · 8 min · 0 failed, 7 missed
  • MissedAll participants
    Tue, Oct 27 17:07 UTC → Tue, Oct 27 17:10 UTC · 4 min · 0 failed, 3 missed
  • MissedAll participants
    Tue, Oct 27 16:56 UTC → Tue, Oct 27 17:04 UTC · 9 min · 0 failed, 8 missed
  • MissedAll participants
    Tue, Oct 27 16:46 UTC → Tue, Oct 27 16:55 UTC · 10 min · 0 failed, 9 missed
  • MissedAll participants
    Tue, Oct 27 16:39 UTC → Tue, Oct 27 16:45 UTC · 7 min · 0 failed, 6 missed
  • MissedAll participants
    Tue, Oct 27 16:34 UTC → Tue, Oct 27 16:38 UTC · 5 min · 0 failed, 4 missed
  • MissedAll participants
    Tue, Oct 27 16:03 UTC → Tue, Oct 27 16:33 UTC · 31 min · 0 failed, 30 missed
  • MissedAll participants
    Tue, Oct 27 13:29 UTC → Tue, Oct 27 16:02 UTC · 2 h 34 min · 0 failed, 153 missed
  • MissedAll participants
    Tue, Oct 27 12:36 UTC → Tue, Oct 27 13:28 UTC · 53 min · 0 failed, 52 missed
  • MissedAll participants
    Tue, Oct 27 01:08 UTC → Tue, Oct 27 12:35 UTC · 11 h 28 min · 0 failed, 687 missed
  • MissedAll participants
    Tue, Oct 27 00:40 UTC → Tue, Oct 27 01:07 UTC · 28 min · 0 failed, 27 missed
  • MissedAll participants
    Tue, Oct 27 00:17 UTC → Tue, Oct 27 00:39 UTC · 23 min · 0 failed, 22 missed
  • MissedAll participants
    Mon, Oct 26 22:42 UTC → Tue, Oct 27 00:16 UTC · 1 h 35 min · 0 failed, 94 missed
  • MissedAll participants
    Mon, Oct 26 21:56 UTC → Mon, Oct 26 22:41 UTC · 46 min · 0 failed, 45 missed
  • MissedAll participants
    Mon, Oct 26 21:30 UTC → Mon, Oct 26 21:55 UTC · 26 min · 0 failed, 25 missed
  • MissedAll participants
    Mon, Oct 26 21:08 UTC → Mon, Oct 26 21:29 UTC · 22 min · 0 failed, 21 missed
  • MissedAll participants
    Mon, Oct 26 20:47 UTC → Mon, Oct 26 21:07 UTC · 21 min · 0 failed, 20 missed
  • MissedAll participants
    Mon, Oct 26 20:28 UTC → Mon, Oct 26 20:46 UTC · 19 min · 0 failed, 18 missed
  • MissedAll participants
    Thu, Oct 22 20:54 UTC → Mon, Oct 26 20:27 UTC · 3 d 23 h · 0 failed, 5733 missed
  • MissedAll participants
    Thu, Oct 22 19:49 UTC → Thu, Oct 22 20:53 UTC · 1 h 5 min · 0 failed, 64 missed
  • MissedAll participants
    Thu, Oct 22 15:06 UTC → Thu, Oct 22 19:48 UTC · 4 h 43 min · 0 failed, 282 missed
What went wrong (8 errors)
  • 129×reliability_install_failed
  • 106×reliability_run_failed
  • 57×reliability_create_failed
  • 12×step_timeout
  • 10×participant failed
  • 6×reliability_verify_failed
  • 2×probe_failed
  • 1×participant failed before reporting results

How it works: a ComputeSDK Actions run fires on schedule and, for each provider, creates a fresh sandbox through that provider’s ComputeSDK adapter — the same create path our TTI and DAX benchmarks use. Inside the sandbox it writes a 1 MiB file of random data, SHA-256 hashes it twice, requires the digests to match, deletes the file, and destroys the sandbox. The check passes only if the full create → probe → destroy loop succeeds in time; runs that fail to dispatch count as scheduler misses, not provider downtime.

Need a provider’s uptime on demand? Sign up for a free ComputeSDK account and query any provider’s status through the API, CLI, or MCP.

On this leaderboard? Your next public run is benchmark Friday — know your number every day.Get stealth benchmarks →