XRates API Status
Live health of the XRates API and the upstream data providers it aggregates. Generated server-side from the last seven days of fetch logs and refreshed every 60 seconds.
All systems operational
Last successful fetch:
Data Sources
XRates aggregates rates from multiple upstream providers and falls back through them in priority order. A degraded source does not block the API as long as at least one source is operational.
| Source | Status | Last fetch | 24h uptime | 7d uptime |
|---|---|---|---|---|
| cbr | Operational | 100% | 100% | |
| ecb | Operational | 100% | 100% | |
| fawazahmed0 | Operational | 100% | 100% | |
| floatrates | Operational | 100% | 100% | |
| imf | Operational | 100% | 100% |
Refreshed every 60 seconds. Programmatic access: GET /api/v1/status returns the same data as JSON.
How XRates calculates status
- ·The scheduler runs
rates:fetchevery 4 hours and writes asource_logsrow per provider per attempt. - ·Each row records whether the upstream returned valid rates, how many currencies were parsed, and any error message.
- ·"24h uptime" is the percentage of
successrows over the last 24 hours; "7d uptime" over the last 7 days. - ·The overall banner is "operational" only if every source's most recent fetch succeeded. A single degraded source flips the banner to "degraded" — but the API itself stays up because at least one source still serves rates.