Regions

Monitor regions control where checks run:

The default is ["global"]. The dashboard calls this All deployed regions. Region availability depends on the deployed workers; a missing worker does not become a failed target check.

Verification

Global monitoring requires the configured quorum of fresh regional failures before confirming a new Down state. A disconnected worker, missing observation, or consensus-store error cannot reduce that threshold or start an incident. If reliable observations are unavailable, the UI shows unknown or stale data and the last confirmed check time.

An explicitly selected single region is a local check and can confirm an outage from that region alone. Select it deliberately; it cannot provide cross-region verification.

API example

Business is required to create or update monitors with an API key; Pro API keys are read-only.

curl -X POST https://obzerv.xyz/api/monitors \
  -H "Authorization: Bearer $OBZERV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Production API",
    "url": "https://api.example.com/health",
    "monitor_type": "http",
    "regions": ["global"]
  }'

Use ["nl-ams", "de-fra"] to explicitly select both listed regions. Do not mix global with specific region IDs.

Observation times

• last_checked_at is the last confirmed result.
• last_observed_at records the latest observation, which may be inconclusive.
• is_stale marks data that cannot support a current health claim.

Regional chart failures describe those probes. Global outage shading and public downtime come from confirmed incidents.

Next

• Incidents.
• Monitor types.