Status
The measured state of the Asqav cloud. The readings below come from the sign-verify canary and the /health check, recorded in status.json; the incident log and the support response targets are published from the same feed.
Current readings
Loading the measured status feed.
Feed updated: not recorded
not recorded means the feed holds no measurement, not a passing one; a last canary run older than two canary intervals is stale in the same way. Read either as unknown rather than as a green state.
- Sign-verify canary, last passed: not recorded
- Sign-verify canary, last run: not recorded
- Health check, last passed: not recorded
Incident log
Incidents that affect the hosted API are recorded here with the date they were opened. The log is empty until an incident is recorded; the feed update date above is the date of the last reading.
No incidents recorded.
Support response targets
These are the targets the support API publishes for Enterprise tickets. They are commitments we staff against, not a measured history of past response times; the incident log above records outages, not ticket performance.
| Priority | First response | Resolution target |
|---|
The figures are read from status.json, which follows the support API's tables. Support targets are separate from the 72-hour personal-data breach notification in the Data Processing Agreement and from the vulnerability disclosure window on the security page.