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. Maintenance follows a predictable schedule:
| Type | Frequency | Typical Duration | Notification |
|---|---|---|---|
| Security patches | As needed | 5--15 minutes | 24 hours in advance |
| Minor updates | Bi-weekly | 10--30 minutes | 48 hours in advance |
| Major upgrades | Quarterly | 1--2 hours | 1 week in advance |
| Infrastructure maintenance | As needed | 15--60 minutes | 72 hours in advance |
Maintenance Windows
Planned maintenance is scheduled during low-usage periods:
- Primary window: Sundays, 02:00--06:00 UTC
- Secondary window: Wednesdays, 02:00--04:00 UTC (for urgent patches only)
Note: Enterprise tier customers can negotiate custom maintenance windows that align with their operations schedule.
What to Expect During Maintenance
- Shared tier: Brief downtime is possible. Active sessions may be interrupted.
- Dedicated tier: Rolling updates with minimal downtime. Most maintenance is zero-downtime.
- Enterprise tier: Maintenance coordinated with your team. Zero-downtime deployment for most updates.
Incident Communication
When an unplanned incident occurs, we follow a structured communication process:
How We Notify You
- Status page update --- Posted within 15 minutes of incident detection.
- Email notification --- Sent to account administrators for affected tiers.
- Portal banner --- A notification banner appears in the customer portal during active incidents.
Incident Severity Levels
| Severity | Description | Response Target | Update Frequency |
|---|---|---|---|
| Critical | Service is completely unavailable | 15 minutes | Every 30 minutes |
| Major | Service is significantly degraded | 30 minutes | Every hour |
| Minor | Partial impact, workaround available | 2 hours | Every 4 hours |
| Informational | Cosmetic or non-impacting issue | Next business day | As resolved |
Post-Incident Reports
For Critical and Major incidents, we publish a post-incident report within 5 business 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 SLA | Allowed Downtime/Month | Credit for Breach |
|---|---|---|---|
| Shared | 99.5% | ~3.6 hours | None |
| Dedicated | 99.9% | ~43 minutes | 10% of monthly fee |
| Enterprise | 99.95% | ~22 minutes | Per contract terms |
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
- Third-party IdP outages affecting SSO (your IdP, not Keycloak)
Historical Uptime
We maintain a rolling 12-month uptime history on the status page. Our track record:
- Platform average: 99.95% uptime over the trailing 12 months
- Longest incident: Details available on the status page
- Incidents per quarter: Typically 0--2 minor incidents
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 by visiting:
https://yourorg.openboxes.cloud/openboxes/api/status
A healthy instance returns a 200 OK response with version and status information.