LeadRails Status

Status / Live probe

Live health probe

Each component below is probed every 30 seconds directly from your browser, so latency reflects your network location. For 90-day uptime history and active-incident posts, see the status overview.

Checking systems…

Last refreshed never · auto-refresh every 30s while this tab is visible

Per-component health

  • Intake

    intake.leadrails.dev

    Checking…

    HMAC-signed lead-event ingress

    Latency (your network)
    —
    Last probed
    —

  • Admin API

    api.leadrails.dev

    Checking…

    REST + OpenAPI control plane

    Latency (your network)
    —
    Last probed
    —

Three internal workers (delivery, outbox, dlq) consume Cloudflare Queues and D1 with no public HTTP surface. Their health is implicit in the Admin API's ability to respond — if the shared D1 instance is unreachable, Admin API fails the probe above.

Subscribe to status updates

Want a heads-up the moment we declare an incident? Email [email protected] and we'll add you to the notification list. A self-serve subscribe form (and an RSS feed for monitoring tools) is on the roadmap.

For machine-readable status, you can also poll api.leadrails.dev/admin/healthz and intake.leadrails.dev/healthz directly. Both return JSON with wildcard CORS.