Open Exchange Rates Status Page

Apr 8, 2026 · resolved Apr 8

This incident was triggered by a routine system maintenance task and escalated due to an edge case in our application caching infrastructure. At 02:50 UTC, while system maintenance was taking place, a database deadlock was caused by multiple background processes attempting to write data simultaneously. Under normal circumstances, this behaviour would self-correct. However, in this instance one of the processes retried repeatedly, and the database became unresponsive at 03:07 UTC. As a result of this, incomplete data were added to the cache, causing up to 100 currency symbols to be temporarily unavailable in live API responses. We identified the issue and immediately began working to resolve it, which required several manual interventions in our infrastructure. Service was restored at 03:32 UTC, 25 minutes after the first production issues were reported. The incident was then marked resolved on our Status Page. \(The HNL currency symbol however remained unavailable in live API responses, until approximately 11:20 UTC when its data contributors were restored\). A fix for this behaviour is being developed, with deployment planned in the next 2 weeks. In the meantime, there remains a small risk that a similar issue could occur again. We are actively working on reducing this risk ahead of the fix being deployed, and in the unlikely event of a repeat occurrence, our 24/7/365 monitoring team are standing by to resolve it without delay.

Jan 17, 2026 · resolved Jan 27

Dear clients, This incident was resolved with a deployment at ~14:50 UTC on Sunday 18th January, restoring full service to our live API endpoints. We actively monitored the results and saw no further related issues. Work is ongoing to mitigate the root causes of the incident. This incident began during a routine database maintenance procedure on the morning of Saturday 17th January, which caused a brief unplanned database downtime. This propagated to our caching infrastructure and resulted in a number of currency symbols disappearing from live API responses. Unfortunately, this further led to a failure in our data contributor pipeline. We quickly identified a potential fix for the issue, however upon further investigation we found that deploying this would have presented a small, but unacceptable risk of causing further issues. We therefore decided to carry out additional QA and testing which lasted until the following day. Following this we deployed the fix and resolved the issue on Sunday afternoon. Since resolving the incident, we have carried out further investigations and are now implementing additional redundancies in our data platform and caching infrastructure, to prevent any similar issues from occurring again. - Note on historical data: Although live and end-of-day rates were restored by our fix, there are gaps in our intra-day (spot) / open-high-low-close-average (ohlc) endpoints, between approx. 05:00 and 07:00 UTC on 18th January. - Note on API Usage: If your account made additional API requests as a result of this incident and exceeded its usage allowance, please let us know and we'll make sure your access is not affected for the remainder of your usage month. There is no need to upgrade your subscription in this case; if you have already upgraded as a result of unexpected overages, please contact us and we will be happy to help. We sincerely apologise for any inconvenience you may have experienced during this incident. Please contact us if you need any additional support. Open Exchange Rates Team [email protected]

Feb 1, 2024 · resolved Feb 1

This incident has been resolved.

Jan 21, 2024 · resolved Jan 22

This incident has been resolved.

Jan 14, 2024 · resolved Jan 15

Between 07:00 and 09:00 UTC on Sunday, clients experienced intermittent connection failures and internal server errors when connecting to our API. This was related to a network issue with our caching infrastructure. We apologise for any inconvenience caused by this partial outage. The incident was fully resolved by 10:00 UTC and there have been no further reported issues.