SYSTEM STATUS · PUBLIC VIEW
All control-plane systems operational.
No active interruption is reported for authentication, the Control API, audit access, or documentation. This page refreshes every 60 seconds.
Component status
| Component | Current state | Monthly objective | Scope |
|---|---|---|---|
| HTTPS origin | Operational | 99.95% | Static site and API proxy |
| Authentication gateway | Operational | 99.95% | Password, MFA, recovery, sessions |
| Control API | Operational | 99.95% | Status, resources, settings, actions |
| Audit event store | Operational | 99.95% | Authenticated event reads and writes |
| Public documentation | Operational | Best effort | Handbook, security, trust, policy, privacy |
| Regional coordination | Operational | 99.90% | Control-plane representation of regional state |
A regional replication alert or transfer impairment may appear inside the authenticated console without making the interactive control plane unavailable. Component status changes when the published component itself is materially impaired.
Machine-readable health
Automated checks should use the stable JSON endpoints rather than parse this HTML page.
| Endpoint | Purpose | Expected healthy response |
|---|---|---|
/api/v1/health | Application process liveness | 200 with service and uptime |
/api/v1/ready | Origin-to-application readiness | 200 when API is ready |
/api/v1/status | Operating state and release version | 200 with operational state |
/health | HTTPS origin health | 200 from Nginx origin |
Health responses include cache prevention and request correlation headers where applicable. A successful liveness response does not prove that every downstream regional dependency is healthy.
Objectives and measurement
The monthly control-plane availability objective is 99.95%. This is an operating target, not a statement that a full historical measurement period has already been completed. Historical attainment will be published only when the measurement source, exclusions, and complete reporting period are available.
Maintenance policy
Planned control-plane maintenance is reviewed through change management. When user-visible impact is expected, the status page identifies the affected component, start time, expected duration, and operating impact before the window begins.
Maintenance without expected public impact may be recorded only in the authenticated change view. Emergency changes are communicated after initial containment when advance notice is not practical.
| Window state | Public communication |
|---|---|
| Scheduled, no expected impact | Authenticated change record; public notice optional |
| Scheduled, expected degradation | Public maintenance notice before start |
| Emergency mitigation | Incident notice as soon as impact is confirmed |
| Completed | Outcome and residual impact recorded |
No public control-plane maintenance is currently scheduled.
Public incident history
No public control-plane incident has been recorded since the service status page was published on 05 Aug 2026. This statement is limited to confirmed impact within the status scope and does not assert a longer operating history.
When an incident occurs, the public record will include detected time, affected components, confirmed impact, state changes, resolution time, and a summary of corrective action where disclosure does not create additional security risk.
05 Aug 2026 to present · no published control-plane interruption.
Reporting a problem
Before opening a duplicate report, compare the observed condition with the component table and machine-readable endpoints. For an authenticated error, record the request ID, UTC timestamp, operation, and affected component.
Security vulnerabilities follow the vulnerability disclosure process. Do not submit passwords, MFA values, cookies, or private keys with a service report.