System Status
Public engine and platform status for CryptoIQ Sentinel
Inspect the real-time status of the CryptoIQ Sentinel public engine endpoint, market observation feeds, and verification surfaces.
What the public status surface monitors
This status page queries the public engine health endpoint directly to report whether the core Sentinel API, market data ingestion pipeline, and public receipt verification services are reachable and responding within normal latency bounds.
If the public engine endpoint is degraded or unreachable, the interface reports that state plainly rather than masking outages with cached or synthetic placeholders.
Fail-closed behavior during data or venue disruptions
CryptoIQ Sentinel is engineered to fail closed. When market data feeds become stale, an exchange adapter reports connectivity errors, or the backend readiness check cannot verify account state, LiveOrderGuard blocks new order submissions automatically.
Public pages and receipt permalinks also degrade gracefully: if the metadata service times out, the application shell still loads cleanly while withholding unverified state.
Operator actions when status is degraded
During any platform or exchange disruption, operators can use the cockpit kill switch to halt new signals and can always manage or close open positions directly inside their exchange account interface, since funds and custody remain at the venue.
For additional operational guidance and troubleshooting steps, review the trust documentation and operator resources.
Operating modes and verification path
Every surface on CryptoIQ Sentinel separates read-only Watch observation, 10,000 USD simulated Paper practice with no cash value, historical Replay analysis, Shadow observation, and backend-certified Live venue execution. Operators can review public decision receipts, verify trading-scoped API key custody boundaries, and inspect gate refusal reasons before considering any live order path. Educational material only, not financial, investment, legal, or tax advice.