SERVICE STATUS
All systems operational
Checked 2026-08-05 04:35 UTC · every request re-probes the database and snapshot.
Control databaseKey, scope, and quota store
OperationalReachable, schema current · 1264 ms
Snapshot releaseDeployment-bundled data, digest verified
Operational2026-08-04-ce0db35f-48eca91725c3422e · 10 h old · 0 ms
Articles API/v1/articles and /v1/articles/{slug}
OperationalFresh, validated · 0 ms
Economic calendar/v1/economic-calendar
OperationalFresh, validated · 0 ms
Smart Money/v1/smart-money investors, consensus, and trades
OperationalFresh, validated · 0 ms
Current snapshot
- Snapshot
2026-08-04-ce0db35f-48eca91725c3422e- Generated
- 2026-08-04 18:19 UTC · 10 h old
- Schema
- v1.0
- Source commit
ce0db35fbcd9- Excluded investors
- 2
Deployment
- Environment
- production
- Region
- iad1
- Commit
b523aea83253
50Articles22Calendar events10Investors317Consensus issuers2,115Filing changesHow this page works
Each load runs the same probes as the machine health endpoint: the control database must answer and match the required schema, and the deployment-bundled snapshot must pass digest and freshness validation for every surface. No live market provider is contacted.
Daily uptime history is not published yet. For monitoring, poll /health, which returns JSON and answers 503 when a component is unavailable. Incident contact: ECONALK developer support.
Endpoint contracts and error codes live in the documentation.