Anvat

Status

Gateway health, live from your browser.

No pre-rendered "all systems operational" badge — the widget below makes a real fetch to api.anvat.app/healthz from your network and reports what happens.

Gateway · api.anvat.app

Checking…

Endpoint
/healthz
Round-trip
Process uptime
Last checked

This check runs in your browser, from your network. Auto-refreshes every 30 seconds. If it's green here, the gateway is reachable from your edge — the most honest signal we can give.

Service-level objectives

The numbers we target for paying customers. Misses get reported transparently in the incident log below.

MetricTargetHow we measure
Gateway availability99.9% monthlySuccessful 200/ok responses to /healthz from 3 monitored regions.
Request error rate< 0.5% (excluding upstream)Anvat-originated 5xx as a share of total requests. Upstream provider errors don't count against this.
p50 response overhead< 25 ms vs direct upstreamMedian latency added by the gateway over a direct upstream call on the same region.
p99 response overhead< 80 ms vs direct upstream99th-percentile gateway-added latency on the same region.
Streaming TTFTWithin 30 ms of upstreamTime-to-first-token over SSE matches the upstream provider's TTFT within 30 ms.

Incident log

No customer-visible incidents reported yet. When something goes wrong we'll write it here with timestamps, duration, and what we changed — same week, no spin.

How we monitor

  • • External synthetic probes hit /healthz from 3 regions every minute.
  • • Per-route p50/p95/p99 latency tracked on the gateway itself; alerts fire on 5-min sustained breach.
  • • Upstream provider availability tracked separately so Anthropic / OpenAI / Google outages don't pollute our SLO.
  • • Cost-of-error alarms: if request error rate or 5xx pattern looks anomalous, pager fires before customers see it.

Get notified

We don't have a status-page subscription endpoint yet (small team, honest about it). For now: