Service status

Status without
inventing green lights.

This public page does not infer production health from a marketing server. A trustworthy status page must be connected to independent monitors for each deployed service.

TH / STATUS MODEL
Monitor feed not connectedNo operational claim is being made.
honest by default
RECOMMENDED COMPONENTS

What a live status feed should actually measure.

When monitoring is connected, these components can be published independently instead of reducing the whole platform to one misleading badge.

StorefrontHTTP availability + critical renderNot connected
Commerce APIhealth + latency + error ratioNot connected
Checkout / paymentssynthetic path + callback queueNot connected
Webhooksingest + processing backlogNot connected
Workersheartbeat + queue ageNot connected
Backstage operationslogin + critical operational actionNot connected
WEBSITE / MACHINE-READABLE CHECK

Website-overlay health has
an intentionally narrow endpoint.

/_thonem-site/health.php verifies only that the public website overlay and its release assets are readable. It explicitly does not claim database, checkout, payment, queue, carrier or commerce API health.

HTTP 200

Overlay readable

The release-owned homepage, version file, CSS and JavaScript are present.

HTTP 503

Overlay incomplete

At least one required website release file is unavailable.

NOT INCLUDED

Commerce health

Use independent application monitoring and provider checks for transaction health.

V7 / MACHINE READABLE

Release metadata is public; commerce health is not inferred.

version.json, release-manifest.v9.json and the overlay health endpoint describe this website release only. They do not imply database, checkout, payment, queue or provider availability.

Release manifest →