Production service
Web app
Public app shell, login, and customer-facing product interface.
Latest update
This status page is currently serving the public web experience.
Production service health refreshes every minute. Active incidents, formal notices, and customer reporting channels stay published here.
Live service checks run every 60 seconds. Incident communications and formal notices are managed from structured page data so customer-facing wording stays intentional and reviewable.
Current System Status
These components reflect the live production web experience plus the latest readiness checks for the API, MCP server, and background processing layer.
Production service
Public app shell, login, and customer-facing product interface.
Latest update
This status page is currently serving the public web experience.
Production service
Authenticated application traffic and external API requests.
Latest update
Waiting for the first live readiness probe.
Production service
Workspace-bound MCP access for compatible clients and agent workflows.
Latest update
Waiting for the first live readiness probe.
Critical infrastructure
Asynchronous processing for workspace automation and queued jobs.
Latest update
Waiting for the first live readiness probe.
Incident Status Updates
When there is an ongoing disruption, this section becomes the source of truth for status, scope, impact, and customer-facing update cadence.
No active incidents
There are no published disruptions right now. If that changes, status updates will appear here with timestamps until the incident is resolved.
Incident History
Recent incidents stay published here after resolution so customers can review scope, duration, and the final status summary.
No incident history published yet
Once an incident or maintenance event is closed, the summary and timeline will stay here for customer reference.
Reporting Channels
Customers and partners should have an obvious way to report suspected security events, availability problems, or abnormal behavior.
Report outages, degraded performance, or product access issues.
support@zentrik.aiReport suspected security events, abuse, or privacy concerns.
security@zentrik.aiReview our security posture, controls, and incident-response commitments.
zentrik.ai/securityFormal Notices
If leadership determines that a formal breach or security notice must be published, it will appear here with scope, timing, affected systems, and customer action guidance.
No formal notices published
Formal external breach notices are only published when approved by Zentrik leadership and counsel. This section is reserved for that communication path.
Operational note
This page uses the existing production readiness probe for real-time infrastructure status. To publish incident updates or formal notices, edit the status page content source in the frontend and redeploy.