System Status
Service status describes recent observations of a service. It is separate from your workspace permissions, production access and the outcome of an individual transaction.
Open XKOVA System Status for the production installation or staging system status when testing that installation.
Read the Observation
| State | Meaning |
|---|---|
| Operational | Recent checks met the configured success threshold. |
| Verifying | Checks are collecting enough observations to confirm a state. |
| Degraded | At least one service check met its failure threshold, or an incident is open. |
| Unknown | A current observation is missing, stale or unavailable. |
| Blocked | A check cannot run because an explicit prerequisite is missing. |
Unknown does not establish an outage, and it must not be treated as operational. Check the observation timestamp and incident updates. A page behind a sign-in gate does not prove the protected application is healthy.
Separate Installations and Workspace Modes
Staging observations describe the staging installation. Production observations describe the production installation. Each installation can serve sandbox workspaces on testnets and production workspaces on mainnets. Confirm the installation, workspace mode and chain when investigating a problem.
Availability Is Not Settlement
A responding API does not prove payment execution, indexing, webhook delivery or on-chain settlement. Follow the operation's status and verify its final result. A transaction included in a block can still revert. Service status never grants production access, billing entitlement or authorization to execute a flow.
Incident Updates and Email
Subscribe on the status page and confirm the email subscription before receiving incident updates. Each notification includes an unsubscribe link. Incident updates describe what the team has verified; they do not promise a recovery deadline or that an individual account is unaffected.
Report a Problem
Use Support and include the error code, correlation ID, timestamp, installation and workspace mode. Avoid repeating a value-moving request until you have checked its outcome and the documented idempotency behavior.