Some ZoikoSuite services
are experiencing
degraded performance.
See current service health, active incidents, scheduled maintenance, and historical status for the ZoikoSuite services covered by this public page.
Status freshness, scope & methodology
"Operational" without freshness and scope is incomplete. When telemetry is stale or
unknown, this page says so — it never silently preserves the last green state.
Live · Delayed · Stale · Unknown. Stale/unknown
suppresses confident "operational" language and
shows the last verified timestamp instead.
Shared multi-tenant services and published regions.
Beta/private preview and dedicated environments
are explicitly excluded.
Component status matrix
Buyer-readable components mapped to internal service ownership — not a dump
of every microservice.
Region & deployment status
Availability is qualified by deployment and jurisdiction — never presented
as a blanket claim.
Fully represented on this page where telemetry
coverage is complete.
Shared dependencies shown here;
environment-specific status may differ.
Only Zoiko-managed shared dependencies appear
publicly.
Evidence export delays in EU region
Public incident ID INC-2026-0914-03 · Impact: Degraded performance · Started 08:58 UTC
Scheduled maintenance
Distinct from incidents — visible before the window and retained historically after
completion.
Document services storage migration
Window: 15 Sep 2026, 07:00–09:00 UTC · Affected: Document / File Services ·
Expected impact: intermittent read-only mode
Governance & Policy service upgrade
Window: 21 Sep 2026, 02:00–03:30 UTC · Affected: Governance & Policy · Expected
impact: none expected
Availability & reliability history
Published only when service boundary, observation points, measurement period,
and data completeness are approved and reproducible. No invented uptime
percentages.
Incident history
A durable trust record — not curated to show only favorable outcomes.
Post-incident review
An accountability artifact, not a forensic dump — explains impact and corrective
learning without exposing exploitable detail.
Status notifications
A retention and support-reduction tool, not a lead-capture mechanism. Only
configured, supported channels are shown.
Enterprise & environment-specific
status
Public status cannot safely represent every dedicated or
customer-controlled environment — so this page says so, clearly.
Shared dependencies shown above; your dedicated environment may have separate status.
Customer-specific environments are never exposed publicly.
Contracted private operating-status channel applies.
Frequently asked questions
This page reflects the live overall state and affected scope. If status data is stale or unknown, that is stated explicitly rather than defaulting to "operational."