The status page goes live at launch

When Sandscale opens, this page shows the live state of every service, with plain updates when something breaks.

Nothing to report
until we open

Sandscale isn’t open to the public yet, so there’s no uptime to show. When it opens, this page shows the live state of each service in each region, US East (N. Virginia) and EU (Frankfurt), and any new region gets its own rows.

sandscale.dev/statusNo checks have run yet
ServiceRegionState
SandboxesUS EastLive from launch
SandboxesEULive from launch
WorkspacesUS East, EULive from launch
Build hostsUS East, EULive from launch
API and MCPUS East, EULive from launch
DashboardGlobalLive from launch

Plain updates,
with times

When there’s an incident we post what’s affected, what we know and what we’re doing, then update it until it’s resolved. This is how an entry will look.

Slow sandbox starts in US EastExample, not a real incident
TimePhaseUpdate
14:02 UTCInvestigatingSome sandboxes in US East are slow to start. We’re looking into it.
14:11 UTCIdentifiedOne warm pool ran low. We’re adding capacity; running boxes aren’t affected.
14:24 UTCMonitoringStart times are back to normal. We’re watching the pool.
14:50 UTCResolvedResolved. A short write-up of what happened follows.

Something
not working?

Tell us, with the box id and what you saw.

Support

Your account, a box that did something unexpected, billing.

support@sandscale.dev
Security

Send vulnerabilities to security, not support.

security@sandscale.dev

Releases and changes,
written plainly

See what has shipped so far.

A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI