Skip to main content
status.instabox.sh shows whether each part of InstaBox is working now, and its uptime over the last 90 days. Check it when requests start to fail, to see whether the problem is on our side. Most incidents on the page are posted automatically by our control plane and an outside check, with no person in the loop:
  • A problem must persist before it is posted: the control plane waits 2 to 3 minutes, and the outside check fails twice before it posts.
  • The rows judged from our users’ requests move only when failures come from several customers, so one customer’s failing requests do not open an incident. Our team still handles those.
  • Automation posts at most a partial outage. Only a person on our team posts a full outage, after confirming it.
  • Our team also posts incidents by hand for problems the checks do not cover.

What the page shows

Each row is one part of InstaBox, with its status now and its uptime over the last 90 days. Sandboxes and CI runners are groups. A group shows the combined uptime of its rows.

Follow incidents

To read past incidents, open View history on the status page. To be told about incidents, use Subscribe to updates on the status page, or add a feed to your reader. Email and Slack subscriptions only get the incidents a person on our team posts. The feeds carry every incident, including the automatic ones:
  • RSS: https://status.instabox.sh/feed.rss
  • Atom: https://status.instabox.sh/feed.atom

What to expect during an incident

  • Posted after a few minutes. A problem shows on the page after it lasts 3 minutes at degraded performance, or 2 minutes at an outage. Slow CI jobs take longer to show, because jobs must first wait several minutes. The outside check runs about every 10 minutes, so the rows it covers can take longer too.
  • Monitored before it is resolved. When such a component recovers, the incident says “Recovered. Monitoring to confirm.” for 30 minutes. If the problem comes back in that time, it continues in the same incident. The final update says how long the incident lasted and what you need to do, or “No action needed.”
  • Resolved by the next good check. Incidents on Dashboard and API, SSH and Public URLs are resolved by the next run of the outside check that passes.
  • A person takes over. When our team posts an incident on a component, the automation leaves that component alone until the incident is resolved.

How uptime is calculated

The status page is hosted on incident.io, which calculates uptime as described in How we calculate uptime:
  • A partial outage and a full outage count in full as downtime. Degraded performance and scheduled maintenance count as up.
  • Downtime counts only while the component shows the outage. The minutes before an incident is posted and the 30 minutes of monitoring after it recovers do not count.
  • A group counts as up only when every row in it is up. Time when two rows are down at once counts once.
Our checks measure what you see, so a failure of a provider we run on shows like any other failure.

Report a problem

Check the status page first, so you know whether we already have an open incident. Then email support@instabox.sh or tell us on Discord. Enterprise SLA terms are set in the customer’s agreement, not on the status page.

Errors

Every error code, with whether to retry and what to do.

Limits

What each plan allows, and the limits inside a machine.