All systems operational

Every on-chain comp records how it was attributed to a card. A healthy mix is dominated by the tightest strategies — number+grade and number+player+grade. Looser strategies are still safe (every match goes through a player-similarity check) but they signal where our card metadata is incomplete enough that the matcher has to lean on weaker signals.

• Healthy: last row seen within 36 hours. Daily syncs (Scryfall, Pokémon TCG, YGOPRODeck) should always be here when running.
• Stale: last row between 36h and 7d ago. Aggregator quotes drop here first; marketplaces stay healthy longer since activity is naturally bursty.
• Inactive: never ingested. Either the source is on the roadmap but not wired up yet, or it's been disabled.
• Cron Never run / Stale: every tracked job is listed, even with no cron_runs row. Stale means the last start is older than 36 hours — Vercel is not invoking it, or auth is failing before the job can log.

Cron rows are judged against their own cadence, and the Expected column is derived from vercel.json rather than restated here, so the two can't drift. A cron reads Stale once its last run is more than one full cadence plus 2h old, and Never run when it has no run on record at all — a tracked job that never fires is the failure mode this table exists to catch, so it is always shown rather than omitted.

The same payload is available as JSON at /api/v1/status. That endpoint and this page share their query logic, so they can never diverge.