Status
Status
Section titled “Status”There is no automated status page yet. This page is the placeholder for one; the probes, history, and alerting ship with F6 (launch hardening).
What will be probed
Section titled “What will be probed”- Listings freshness: did the daily 13:00 UTC run land, and how many active listings resulted.
/mcp: tool catalog reachable, plus a canary tool call within its time budget.- Per-feed last-refresh: each source in data sources checked against its freshness SLO — tract vintage block, SAFMR year, ZHVI/ZORI month, comp-source reachability.
- Error rates: 429 and 5xx counts on the public endpoints.
Checking today (manual)
Section titled “Checking today (manual)”curl https://chicago-value-map.mohammad210.workers.dev/api/healthWhat to read in the response:
| Field | Meaning |
|---|---|
ok, d1, kv |
service and storage bindings up |
last_run |
most recent listings run: kind, finished timestamp, found, new_count. Older than ~24 h = the daily run failed |
active_listings |
current active inventory |
stale_model_rows |
active rows still scored by an older model_version — nonzero right after a release, draining via rescore |
/api/metrics/scorecard also returns last_data_run alongside the published accuracy numbers. If something looks stuck for more than a day, open a GitHub issue (repository link to be published).