Status
Live state of this deployment, read at the moment you loaded
the page. Nothing here is cached. This page is for people; /health is the
liveness probe for machines, and returns the same build identity as JSON.
Availability
| Measured availability | 99.983% |
| Window | 30 days, measured since 2026-08-14T10:45:00.000Z |
| Minutes observed | 41,045 of 41,052 |
| Outages recorded | 1 |
| Outage start (UTC) | End (UTC) | Duration |
|---|---|---|
2026-08-17T06:25:00.000Z | 2026-08-17T06:27:00.000Z | 3m |
How this is measured, including what it cannot see. Parse writes one row a minute while it is running, and the gaps are the outage record — a process that has crashed cannot report its own crash, so missing minutes are the evidence. The denominator is capped at the age of the oldest measurement, so a short history reports a short window rather than a misleading percentage. Two limits worth knowing: this cannot tell a software outage from the host being switched off, and it cannot see an outage where Parse is healthy but the network in front of it is not — only an external prober would catch that, and Parse does not run one. Restarts of a minute or less are not counted as outages, because deploys are frequent and are not incidents. Parse runs on a single node; there is no failover, and the recovery procedure is manual. Backups run every six hours and each run is verified by restoring it.
Build
| Overall | Operational |
| Version | 1.0.0 |
| Commit | 54199d0 |
| Build time | 2026-09-03T13:11:31.530Z |
| Running from | source |
| Node | v26.0.0 |
| This build running for | 8d 9h 45m |
| Checked at | 2026-09-11T22:56:48.632Z |
This deploy runs from source rather than a compiled artifact, so the build time is the time the process started. The commit is read from the checkout at boot.
Dependencies
| Dependency | Status | What it does |
|---|---|---|
| Database | Operational | Stores API keys, screening events, and policy configuration. |
| Cache and rate limiting | Operational | Backs rate limits and short-lived counters. |
| Semantic analysis layer | Operational | All 3 semantic screening call(s) in the last hour completed. Per-request status is reported in layers.llm. |
A dependency marked down does not necessarily take the API down. Screening itself runs in-process: pattern matching keeps working when the database or cache is unreachable, and every screening response reports which analysis layers actually ran.
Machine-readable
GET /statuswithAccept: application/json— this page as JSONGET /health— liveness probe, always JSONGET /version— version and build identity
Something broken that this page says is fine? Tell us at [email protected] for security issues, or support for everything else.