Health
Keep service context visible for operators.
The dashboard gives customers a familiar place to understand workspace activity when they are checking status or impact.
Status workflow anchor
Uptime and service health
Status
Platform status, uptime and incident communications.
A visible status page is an important SaaS trust signal. Use the link below to view uptime, incidents and planned maintenance.
Status hub
Service health
Uptime, maintenance, incident communications and escalation routes for Zektrx customers.ServicePublic status
UpdatesIncidents
TrustMaintenance
What you should see
- Uptime and service health
- Incident history
- Planned maintenance updates
- API and webhook health where applicable
Need enterprise comms?
For enterprise customers we can align incident communications, escalation paths and response expectations to your internal process.
Status escalation guide
Know where to go when something looks wrong.
A simple route for separating public incidents, account-specific support, security reports and enterprise communication needs.
First checkConfirm the public statusStart with this status hub for uptime, incidents and planned maintenance notes.Open routeCustomer issueSend support the symptomsIf your team is affected, include the module, user role, browser and what changed.Open routeSecurityReport sensitive findingsUse responsible disclosure for suspected security issues, exposed data or unsafe behaviour.Open routeEnterpriseAlign incident communicationsAsk for enterprise escalation paths, internal comms wording or procurement-ready summaries.Open route
Status In Product
Connect service health to operational context.
Status information is most useful when customers know how to route issues, understand impact and keep records moving after service updates.
1
Health
Uptime and service health
2
Comms
Send support the symptoms
3
Review
Align incident communications
Comms
Move from incident note to report-ready summary.
Reporting surfaces help teams document impact, exports and follow-up when service changes affect operational work.
Status workflow anchor
Send support the symptoms
Review
Connect status to operational review.
Analytics and management views make reliability conversations easier to connect to daily contractor operations.
Status workflow anchor
Align incident communications
Status Control
Status, support and incident routes in one view.
The status page now gives customers a clearer operating model: public service checks, account-specific support, security disclosure and enterprise incident communication all stay easy to separate.
1
Public signal
Status hub
Keep uptime, maintenance and incident context visible from one durable route.
2
Customer issue
Support path
Move account-specific symptoms into support with module, role and browser context.
3
Sensitive report
Disclosure
Route security-sensitive issues away from normal support and into responsible reporting.
4
Enterprise
Incident comms
Give larger customers a clear place to align summaries and internal update needs.
Operational Continuity
Make incidents easier to understand and route.
The status page now connects service health, customer support, security reporting and enterprise communications so teams know where to go when something changes.
Route the issue
Give teams a clear path to status, support, recovery or security without hunting through the site.
Protect the record
Keep operational guidance connected to the documents, evidence and controls that matter on live work.
Return to work
Help users get back to the app, the right page or the right contact route with less friction.