---
slug: 50577-health-check-advisors
published: 2026-09-18
change_type: improvement
affected_products:
  - Auth
  - Data APIs
  - Database
  - Edge Functions
  - Realtime
  - Storage
page: https://supabase.com/changelog/50577-health-check-advisors
---

# Health Check Advisors

Supabase Advisors already surface security misconfigurations and performance issues. They now also monitor service health, starting with error rates — the broadest early-warning signal across your stack.

## What's in v1

**Service error rate checks** — read from log data, one per service:

- `log_data_api_error_rate_high` — PostgREST 5xx rate is elevated
- `log_auth_error_rate_high` — Auth service error rate is elevated
- `log_storage_error_rate_high` — Storage service error rate is elevated
- `log_edge_function_error_rate_high` — Edge Functions error rate is elevated

Error rate checks are designed to be a broad net. A single elevated result tells you where to look; from there you can drill into logs, query connection stats, or trigger your own deeper checks. This makes them particularly useful as a signal source for agents — an elevated rate check is a reliable catalyst for automated investigation flows.

An empty result means all checks ran and found nothing. `advisor_check_unavailable` means a check could not run — so you can distinguish between healthy and unchecked.

## Where to access them

**Studio** — a Health tab appears in the Advisors section of your project, above Security in the navigation. Each check result links directly to the relevant logs, connection stats, or infrastructure view.

**Management API** — `POST /v2/projects/{ref}/advisors/run` returns health check results alongside security and performance advisors. Results are cached to avoid repeated probing.

## Get started

Open your project in Supabase Studio and go to [**Advisors → Health**](https://supabase.com/dashboard/project/_/advisors/health).

To query programmatically:

```bash
curl -X POST https://api.supabase.com/v2/projects/{ref}/advisors/run \
  -H "Authorization: Bearer {token}"
```

## What's next

v1 ships service error rate checks. Database connectivity probes and instance health checks are next on the roadmap.

If there are health signals you wish Supabase surfaced — specific error conditions, resource thresholds, connection patterns — reply in the GitHub Discussion linked below.