Status

Use this page to check the current operational status of NutritionSignals and what to do if something looks degraded.

For real-time updates and incident history, we recommend linking to a public status page once it’s live.

Current status

API: Operational
Image proxy: Operational
Food resolution: Operational
Barcode lookup: Operational

Tip: If you’re seeing issues only with a specific endpoint (for example, POST /v1/foods/analyze-image), check endpoint-specific latency, rate limits, and retry behavior.

What to check when something fails

Latency spikes (slow responses or timeouts)
Auth errors (401 / 403) — check your Authorization: Bearer <API_KEY> header and plan access
Rate limiting (429) — retry with exponential backoff and respect Retry-After when present
Server errors (500 / 502 / 503 / 504) — usually transient; retries are recommended

If the issue persists, include the following when contacting support:

Timestamp (with timezone)
Endpoint + method (for example, POST /v1/foods/resolve)
HTTP status code
request_id (if returned)

Status page

Status page: Coming soon (real-time uptime, incidents, and maintenance updates)