Legal
Verdscore is seeing issues.
Last updated · 13 July 2026
The position
A single honest signal, refreshed every four hours against a real liveness check. Per-component signals (database, background workers, Resend, Stripe webhooks) move to a dedicated status.verdscore.ai when we wire the observability for it — the roadmap is real, the timeline is when it's ready.
Right now
DegradedLast checked · just now
The last liveness ping did not succeed. If you're seeing errors in the app, please write to [email protected] so we can investigate.
How this page works
- The pill above reflects the last successful liveness check against /api/healthz, which does a synchronous read against the primary database.
- The check runs on-demand up to once every four hours (Next ISR). If nobody visits the page for a day, the pill you see is the state from the last visit; visit again to refresh.
- This is intentionally coarse. A single “app reachable” signal is honest; a fake per-component table would not be.
Incident history
Individual incidents are recorded internally and included in the post-mortem sent to affected customers under the 72-hour GDPR Article 33 commitment. A public incident log will land on status.verdscore.ai alongside per-component signals.
Questions about this document? Send me a message — I read every one.