Blaxel Reliability | ComputeSDK

All passedBlipsDownNot counted

Participant	Uptime	Downtime	p50		Details
Blaxel	99.930%	1 min	482ms

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

Every check

Fri, Nov 13

99.930% uptime1178 passed1 failed0 not counted482ms p50753ms p95

00:00

Incidents

No incidents in this window. Incidents are stretches of 3+ consecutive counted checks that did not pass. Not-counted checks break an incident.

What went wrong (1 error)

1×step_timeout

Methodology

Every minute, we create a Blaxel 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 Blaxel.

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

Terminal

compute new blaxel

Explore Sandbox Router

Uptime

Every check

Incidents

Methodology

Run a sandbox on Blaxel.