Claimscan status
Live overview of all Claimscan components. Refreshes every 30 seconds. For incidents, see severity classification and response process below.
// MONITORED COMPONENTS
Public REST API (api.claimscan.io)
Forensic analysis endpoints and authentication.
Database (PostgreSQL)
Cases, findings, accounts and audit log.
Job queue (Redis)
Asynchronous image-analysis pipeline.
Image storage (MinIO)
Encrypted, retention-bound image store in the EU.
Service-level target
We target 99.5% monthly availability on the production API (api.claimscan.io). Scheduled maintenance is announced at least 48 hours in advance — either via email to account holders or here on the status page.
Severity classification
- S1
Critical
API fully down or data loss. Immediate response, update every 30 minutes until resolved.
- S2
Major
Important feature unusable (e.g. image upload fails). Response within 1 hour, update every 2 hours.
- S3
Limited
Non-critical feature or elevated latency. Response within 1 business day.
- S4
Minor
Cosmetic or rarely hit. Fixed in the normal release cycle.
During an incident
- Detection via uptime monitoring (Uptime Kuma) or customer report.
- Severity confirmation, status page update.
- Investigation & mitigation. S1/S2 updates every 30/120 minutes.
- Restoration of normal state, final status update.
- Post-mortem within 5 business days — available on request at support@claimscan.io.
Notifications
A dedicated status subdomain with RSS feed and email subscriptions is in the works. Until then: account holders are notified by email for critical incidents. For real-time monitoring you can poll GET https://api.claimscan.io/health/deep yourself.