Loading…
Loading…
When we last learned something new for each dataset, measured now. If something is behind, it says so here and the API says so per response with meta.stale.
The cadence column is the window each dataset is expected to receive new rows within. It is derived from its ingest schedule, not a service-level promise.
| Dataset | Last ingest | Expected cadence | Rows | State |
|---|---|---|---|---|
| Daily barsEnd-of-day OHLCV for every covered instrument. | 21 September 2026, 00:31 | within 2 days | 4,220,862 | Fresh |
| FX ratesDaily currency pair rates. | 21 September 2026, 00:00 | within 2 days | 13,020 | Fresh |
| Corporate actionsSplits, dividends, spin-offs and the rest. Drives price adjustment. | 20 September 2026, 02:30 | within 7 days | 51,958 | Fresh |
| Earnings calendarAnnounced and confirmed earnings dates. | 20 September 2026, 03:00 | within 7 days | 8,235 | Fresh |
| News eventsIngested headlines backing the sentiment series. | 17 September 2026, 05:00 | within 1 days | 3,594 | Behind |
| Instrument registryThe universe itself, including delisted names. | 19 September 2026, 01:00 | within 14 days | 27,359 | Fresh |
There is no uptime percentage, no incident history and no SLA figure here, because this system does not yet measure any of them. Publishing a number we do not measure would undermine the only thing this page is for.
What it does give you is the measurement that actually affects your results: whether the data you are about to query has been refreshed recently. The same fact is available per-request as meta.stale and meta.asOf on every response, so your code can check it without scraping this page.
Pulse Markets