Status
What the API is serving right now.
Every response comes straight from our own store, so the useful question is how old the reading behind it is. That figure, the catalogue it covers and the last scheduled sync are published here.
State
Operational
The stored reading is inside the sync cadence.
Reading age
1 hour old
Counted from the fetch timestamp carried on every response.
Source published
2026-11-10 00:00:01
The provider's own publication time, which is a different fact from when we read it.
Last check
Passed
166 codes · largest move 0.00% · median 0.00% · source unchanged since the last reading
Currencies
166
Codes in the stored reading the API serves.
Last sync
success
2026-11-10 14:00:34 UTC · 3.5s
Readings · 7 days
105/112
Syncs that stored a reading, against the number the cadence called for.
Failed runs
0
Last success 2026-11-10 14:00:34 UTC
What this measures
- The sync job re-reads the provider on a fixed internal cadence and stores what it finds. Nothing is fetched upstream when you call the API — your request is answered from the last stored reading, with both its timestamps attached.
- The provider publishes on its own schedule, so a newer fetch can legitimately carry the same rates. That is why the source publication time and our fetch time are reported separately rather than as a single “updated” figure.
- Every reading is checked before it is stored: complete, positive values, no loss of catalogue, and no market-wide move large enough to suggest a broken feed. A reading that fails is refused and the previous one keeps answering.
- A reading older than two cycles is shown as behind schedule. Calls keep being served from it in the meantime, with its timestamp attached.
- Reliability is counted from the sync job's own run log, not from a hand-written figure: every stored reading and every failed run in the last 7 days is listed above, against the ticks the cadence called for.
- The last run finished without reporting an error.
- There is no uptime SLA behind this page. Refund and support policy are set out in the terms.
Check it yourself, in one call.
The open endpoint returns the same reading this page reports, with its timestamp, and needs no key.
Read next