Trust

Status.

There is no hosted status dashboard yet. This page explains how each part of the service is monitored and links the public health endpoints, so you can check them yourself.

Components

Component	Health check	Monitoring
Website and docs `openplacesapi.com`	Homepage loads	External uptime check every 5 minutes.
Dashboard and account API `app.openplacesapi.com`	`/health`	External uptime check of the health endpoint every 5 minutes.
Places API `api.openplacesapi.com`	`/health`	Runtime error reporting and request metrics on the server. Not yet part of the 5-minute external uptime check.

Each /health endpoint is public, needs no API key, and returns JSON with "ok": true when that service is up. The Places API health response also reports the Overture source release being served. A health response only shows the service is running; it does not prove every search will succeed.

How monitoring works

A separate Cloudflare Worker checks the website and the dashboard health endpoint every 5 minutes, with retries. It runs apart from the services it checks, so a bad deploy cannot take its monitor down with it.
Failed checks raise an alert in Sentry. If the monitor itself stops running, Sentry alerts on that too.
The dashboard, account API, and Places API report runtime errors to Sentry, and the Places API server exports request, error, and latency metrics.

Reporting an outage

If requests are failing, email support@openplacesapi.com with the time, the HTTP status, and the request_id from the error body. Self-serve plans do not include an uptime guarantee; see the SLA page.