Skip to main content
Live status and incident history for every Coinversa surface are on the status page at status.coinversa.ai. Check it first when something looks wrong — and subscribe there to get incident updates by email or RSS.

What is monitored

During an incident

The REST API returns a 5xx status while a component is degraded. Treat any 5xx as retryable — retry with exponential backoff (with jitter) rather than in a tight loop, and check the status page before you escalate. A 4xx is not an incident: it is about the request or the key — see Authentication. WebSocket clients should reconnect with backoff too; refused upgrades and close codes are covered in WebSocket protocol.

Availability

There is no formal SLA yet. Our target is 99.5% monthly availability, and incidents and their resolution are published on the status page. If you need contractual commitments, contact us.