Status

Live health of the ALETHEIA Safety API, refreshed every 60 seconds from your browser.

Checking…

Last check: — · API version: — · API timestamp: —

Auto-refresh every 60s · next: 60s

Data freshness

Counts and recency of the reference data the API serves. Pulled from /api/freshness.

Compounds

—

Materials

—

Products

—

Snapshot generated

—

Deploy age

—

Stale?

—

What this page checks

This page is a browser-side health probe. When you load it (and every 60 seconds after), your browser fetches https://api.aletheia.holisticquality.io/api/health and /api/freshness directly. There is no intermediate server, no synthetic monitor, and no multi-region external probe behind these numbers.

The signals we surface here are load-time correct from your network location: if the API is unreachable from your client, the badge above turns red. If a transient regional issue affects a specific Vercel edge (we deploy to iad1, sfo1, lhr1) without affecting your route, the badge stays green and we miss that signal. A proper external multi-region monitor with incident history is on the roadmap; until then this page is the honest version of what we can prove from a browser.

Historical incidents and release notes live on the changelog. If you spot a problem that this page doesn't catch, please report it via the contact form — we read every submission.

Subscribe to status updates

No RSS feed or email-on-incident pipeline yet. For now the most reliable signals are:

Watch the changelog for dated incidents and release notes.
Subscribe to the API release-notes endpoint (machine-readable).
For critical-path applications, run your own per-region external monitor against /api/health. We support GET from any origin (CORS *) with no rate limit on the health endpoint specifically.