Service status

Hosted watchtower availability for driftguard.org — API, console, and background watch checks.

Live health check

The public health endpoint returns JSON when the Worker is serving traffic:

curl -sS https://driftguard.org/health

Expected response when operational:

{ "ok": true }

Checking health…

This probe covers the edge Worker — not individual third-party APIs your watches poll. A green health check does not mean every vendor endpoint is reachable.

What we monitor

  • Hosted API — watches, status, preflight, billing, MCP proxy routes
  • Console & docs — static assets and authenticated console shell
  • Watch pipeline — scheduled checks, queue consumers, alert delivery

Your watches surface vendor-specific failures as drift_status: error on the affected watch — see Glossary: drift_status.

Incidents & communication

There is no separate status.driftguard.org page yet (MED-9). During incidents we post updates via:

  • GitHub issues on the OSS repo for cross-posted incident threads
  • Email hello@driftguard.org for Pro/Team customers with active subscriptions

For webhook delivery gaps on your account, check console alert stats and support channels.

Stay informed

  • Watch the OSS repository for release and incident labels
  • Review changelog for planned maintenance notes
  • Enterprise teams: request a dedicated status feed when SSO/RBAC ships (CP-5)

Related

  • Security overview — data handling and hosted boundary
  • FAQ — pricing, support tiers, MCP offline tools
  • Plans & pricing — SLA expectations by tier