Skip to main content

Data status

Seven data domains. Content clocks come first — latest_data_date, data_age_hours, content_ok / content_stale — then collector heartbeat. Heartbeat green is not freshness. Pipeline / system health is ops, not a public data domain and not counted in the live total.

The live JSON board is not an availability promise and not a freshness score of “all green.” A green collector heartbeat does not mean the data is on cadence. A green board does not mean the site or API will stay up.

Live JSON board Recipes

Live content clocks

Loading content clocks…

Primary fields are latest_data_date, data_age_hours, and content_ok. Heartbeat age is secondary.

Domain latest_data_date data_age_hours content_ok Heartbeat age (hours)
Waiting for /api/v1/status/p0…

Freshness budgets

Two different clocks. Collector heartbeat is how often ingest should run for that domain. Content age budget is how old the newest usable observation may be before we call it off cadence. Hours are UTC wall-clock targets for an international audience — not a live SLA and not uptime. Pipeline / system health is ops, not a customer data domain on this table.

Domain Collector heartbeat (hours) Content age budget (hours)
filings 24 48
ownership 48 336
equities 6 72
positioning 48 264
rates 24 72
economics 48 168
calendar 12 Forward schedule — no age budget

How to read the board

curl -sS "https://data.finuties.com/api/v1/status/p0" | jq '{overall, content_stale: .summary.content_stale, stale_domains: .summary.stale_domains, content: .summary.content}'