Uptime and reliability

truval.dev runs API infrastructure intended for production use. This page points to live status, what we monitor, and what we do not publish so you can set expectations with your team and customers.

System status

Public status page: https://status.truval.dev

Subscribe there for incident notifications. The page reflects synthetic checks and service health as configured (for example API availability); exact components and history are shown on that site.

Geography and platform

• Core APIs are served from Cloudflare’s network (global edge) with EU-aligned product positioning (see Quick start and marketing copy on truval.dev).
• The developer dashboard and data plane backing usage and webhooks run in Europe (Frankfurt) as described across these docs.

SLA and availability targets

truval.dev does not publish a separate contractual SLA or fixed uptime percentage on this site. For availability expectations, use:

1. status.truval.dev — historical incidents and current checks.
2. Your own synthetic monitoring against production endpoints (below).

If we introduce a formal SLA or enterprise terms later, they will be linked from here and from the main site.

Monitoring the API yourself

For your dashboards and alerts (complementary to our status page):

• GET https://api.truval.dev/health — lightweight liveness check (JSON with ok and timestamp).
• OpenAPI: https://api.truval.dev/openapi.json — contract for the verify and public routes you depend on.

These help you detect issues from your network perspective; they do not replace the vendor status page for platform-wide incidents.

Related

• Webhooks — delivery retries and signature verification for async verify callbacks.
• Error reference — HTTP error codes and remediation.