System Status
Checking Current Status#
The OpenBoxes Lift status page provides real-time information about platform health and any ongoing incidents:
Status page: status.openboxes.cloud
The status page shows the current state of:
- OpenBoxes instances — Availability of customer instances
- Customer portal — The management dashboard at
app.openboxes.cloud - Authentication — Login and SSO services via
auth.openboxes.cloud - API gateway — The API layer at
api.openboxes.cloud - Marketing website — The public site at
openboxes.cloud
You can subscribe to status updates via email or RSS from the status page.
Planned Maintenance#
We perform planned maintenance to apply security patches, infrastructure upgrades, and platform improvements. There is no fixed patch cadence — maintenance happens when there is something to ship, and every planned maintenance is announced on the status page before it starts.
Maintenance Window#
Planned maintenance that may cause downtime is scheduled inside a single weekly window:
- Sundays, 02:00--04:00 US Pacific time
The status page banner announces the window ahead of time. Downtime inside the announced window is planned maintenance, not an incident.
Note: Enterprise agreements include version upgrades in a window you choose, rehearsed on a copy of your data first.
What to Expect During Maintenance#
- Shared tier: Brief downtime is possible. Active sessions may be interrupted.
- Dedicated tier: Updates are applied by Lift; brief downtime can occur during an instance update.
- Enterprise tier: Your agreement includes version upgrades in a window you choose, rehearsed on a copy of your data first.
Incident Communication#
When an unplanned incident occurs, we follow a structured communication process:
How We Notify You#
- Status page update — An "Investigating" update is posted within 5 minutes of the incident being acknowledged.
- Progress updates — For any incident with customer impact (a full or partial outage), the status page is updated at least every 30 minutes until the incident is mitigated, then again at resolution.
- Email notification — Sent to affected account administrators when an incident breaches our uptime commitment.
Incident Severity Levels#
| Severity | Description | Response Target |
|---|---|---|
| S1 — Critical | Full outage, data-loss risk, or security issue affecting most customers | Investigated immediately, at any hour |
| S2 — Major | Partial outage or a major workflow blocked for a subset of customers | Business hours (09:00--18:00 US Eastern); escalated next morning if it lands outside them |
| S3 — Minor | Single-customer issue or a visible but non-blocking bug | Next business day |
| S4 — Informational | Cosmetic or non-customer-impacting | As scheduled |
Status-page updates every 30 minutes apply to S1 and S2 incidents.
Post-Incident Reports#
For S1 incidents we publish a post-incident report within 72 hours of resolution, and for S2 incidents within 7 days. Reports include:
- Timeline of the incident
- Root cause analysis
- Impact assessment
- Steps taken to prevent recurrence
Post-incident reports are available on the status page and sent to affected account administrators.
Uptime SLAs#
OpenBoxes Lift provides uptime commitments that vary by tier:
| Tier | Monthly Uptime Target |
|---|---|
| Shared | 99.0% |
| Dedicated | 99.5% |
| Enterprise | 99.9% monthly availability target, measured per instance; remedies are defined in the agreement |
What counts toward downtime:
- Complete inability to access your OpenBoxes instance
- Authentication service unavailability preventing login
What does not count:
- Planned maintenance during announced windows
- Issues caused by your internet connection or browser
- Outages of third-party sign-in providers (Google, Microsoft, GitHub)
Historical Uptime#
Uptime and incident history are published on the status page at status.openboxes.cloud — check there for the live track record rather than a snapshot in this doc.
Tip: Subscribe to the status page RSS feed or email notifications to receive proactive updates rather than checking manually. Visit status.openboxes.cloud to subscribe.
Checking Instance Health#
You can verify your specific instance is responding with a plain, unauthenticated request to OpenBoxes' own status endpoint:
curl https://yourorg.openboxes.cloud/api/status
A healthy instance returns a 200 OK response with version and status information. No API key is needed for this check — it is served by OpenBoxes itself, not by the Lift API gateway.