System status

Degraded — see component detail below

DegradedChecked 2026-08-13 12:16:18 UTC

Imports run as counties publish · (44 days ago)

Index coverage

Records held
10,522,109
Certificates plus the parcels behind them. Queryable rows, not rows read.
Source rows read
30,474,078
Across every completed import. Higher than rows held because sources overlap and are deduplicated on write.
Counties with certificate-level data
42 of 67
52 counties hold at least one certificate; the rest carry the sale directory only.
Current stage
Certificate-level data for 42 of 67 counties. 10 more counties have partial data; the rest are sale-directory only.
Last update
Aug 13, 2026, 7:32 AM UTC
  • Index status

    Live.

    Operational
  • API health

    Liveness probe responded in 46ms.

    Operational
  • Docs

    OpenAPI spec + /api-reference rendering.

    Operational
  • Sample API

    No-auth /sample endpoints responding.

    Operational
  • Searchable certificates

    1,267,795 tax certificates searchable via the live index.

    Operational
  • Last full import

    Completed 1 month ago.

    Operational
  • Last daily import

    8,568 records imported 1 month ago (taxcertsale/delinquent_ad_list). No daily import has completed since — this data is stale.

    Degraded
  • Quarterly reconciliation

    Not implemented — no quarterly reconciliation job exists in the current pipeline and none has ever run. Full imports are the only reconciliation mechanism today.

    Pending

Subscribe to updates

Want a note when ingest completes or a quarterly reconcile lands? Email status alerts coming soon. For now, ping us and we'll add you to the list.

Email status updates

Status is rendered from live database queries on every request. No third-party status page. The freshness badge above and the “Last full import” row below both read the completion time of the most recent completed certificate import — the same row, through the same query that produces last_full_import_at in /api/public/dataset-status, cached 30s. If this page and that payload ever disagree, the page is the bug.