Loading…
LoadingLoading…
LoadingStatus
Live result from Veripsa service-health checks. This page does not claim a contractual uptime SLA — it reports the state observed at the time you loaded the page. For the SLA stance, see the Trust Center.
The Veripsa Core public status check reported normal service operation.
No contractual SLA. This page is for transparency, not a promise. The badge above is a single live probe at the moment you loaded the page; it is not an aggregate uptime number, and we do not claim “100% uptime”.
This page is uncached and re-runs the check on every request. Reload to re-poll.
A fresh sample was still being prepared when this page loaded. This is not a service warning — reload in a moment for the completed sample.
This aggregate analysis-freshness signal is reported separately from Core service availability. A stale or behind analysis does not by itself mean the Core service is down.
Free early access is open. Install the GitHub App to connect a repository; self-serve paid plans are not live.
Each visit checks Core service operation and analysis freshness separately on the server. Reload to re-poll.
These checks describe Veripsa's own service path — not any customer's repository — and contain no source code, no file paths, and no engine internals.
No incidents active right now.
Past incident notes are listed on /incidents. To report a suspected outage or security issue, email support@veripsa.com. The incident process is documented in the Trust Center.
Looking for the formal posture? See the Trust Center for data, retention, isolation, subprocessors, the SLA stance, and the incident process.
