Open Exchange Rates Outage History

Started Apr 08, 2026, 03:20 AM UTC· resolved Apr 08, 2026, 04:26 AM UTC

1. identified Apr 08, 2026, 03:20 AM UTC

   We are aware of issues affecting Open Exchange Rates API and are working to resolve this. Please stand by for updates.

2. monitoring Apr 08, 2026, 03:41 AM UTC

   A fix has been implemented to restore full service, and we are now monitoring the results. Please stand by for further updates.

3. resolved Apr 08, 2026, 04:26 AM UTC

   This incident has been resolved and we are continuing to monitor. During this partial outage incident, up to 100 currency symbols became temporarily unavailable in our service, beginning at around 03:07 UTC. We were able to identify the issue and began working on a fix immediately, and service was restored by 03:32 UTC. The root cause appears to be related to routine system maintenance. We are continuing to investigate.

4. postmortem Apr 10, 2026, 10:39 AM UTC

   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.

Read the full incident report →

Started Jan 17, 2026, 06:35 AM UTC· resolved Jan 27, 2026, 03:08 PM UTC

1. investigating Jan 17, 2026, 06:36 AM UTC

   Dear clients, We are experiencing a technical issue with our exchange rates API. A number of symbols (~50) are missing from the live rates API responses, latest.json and other live/historical endpoints, since around 04:35 UTC on 17th January 2026. We are looking into this urgently and will provide further updates as soon as they are available.

2. identified Jan 17, 2026, 07:16 AM UTC

   We have identified the cause of this incident and are working to resolve it as soon as possible. Please stand by for updates.

3. identified Jan 17, 2026, 09:03 AM UTC

   We are continuing to investigate this incident and working on resolution. This was caused by a failure in our cache and data supply pipeline, however the root cause is not clear at present. Since our last update, we have restored the majority of currency symbols to the live latest.json/historical endpoints. There are approximately 38 symbols still unavailable. We have also restored service to our ohlc.json and spot.json endpoints, however there will be gaps in the available data on these endpoints for affected symbols, between approximately 04:30 and 07:15 UTC. Please stand by for further updates.

4. identified Jan 17, 2026, 01:14 PM UTC

   Dear clients, We have identified that this incident began during a routine database maintenance procedure. This caused a brief unexpected database downtime, which propagated to the cache and resulted in a large number of currencies disappearing from live API responses. Unfortunately, this then led to a failure in our data contributor pipeline, which is where we are currently working to restore full service. A fix has been identified and is currently being QA tested, before making the changes to production. We appreciate your patience while we continue to work on resolution.

5. identified Jan 17, 2026, 04:09 PM UTC

   We are continuing to work on this issue and are still testing a potential fix, however we found that this presented a risk of further complications arising under certain conditions. We are now reviewing additional safeguards and will provide further updates as soon as they are available. Thank you for your continued patience.

6. identified Jan 17, 2026, 08:06 PM UTC

   Dear clients, Thank you for your ongoing patience while we have been working to restore API service. This has been complicated by various factors spanning our application, infrastructure, and data contributor connections. At present there are 137 currency symbols available in our latest endpoint, which are receiving updates as normal. The following 35 symbols remain unavailable at this time: AFN, AOA, AWG, AZN, BRL, CLP, CNY, CZK, DKK, GMD, IDR, ILS, JOD, KGS, KMF, MVR, MYR, MZN, NOK, NZD, PHP, RON, SBD, SDG, SEK, SLE, SRD, TMT, TRY, TWD, VES, XAG, XAU, XCD, YER Unfortunately, our earlier planned fix was not able to be deployed, due to a small but present risk of this causing further issues under certain conditions. We are continuing to work on restoring the missing currencies, however in light of further work and testing required we anticipate this may take up to another 24 hours. We will continue to update this page with new information. We sincerely apologise for the inconvenience caused by this outage.

7. identified Jan 18, 2026, 01:14 PM UTC

   We are continuing to work on a fix for this issue and we now anticipate resolution by this evening (UTC) or sooner today. Once again, we sincerely apologise for the delay in restoring full service. We are aware of the issues this can cause to our clients. As soon as service is restored, development will begin on mitigations for the root cause to ensure it cannot happen again. Note: There is no need to upgrade your account in case of increased usage in response to this incident. If your account has made additional requests as a result of this error and risks exceeding its allowance, please let us know and we will make sure this doesn't affect your access for the remainder of your service month. Please stand by for further updates.

8. monitoring Jan 18, 2026, 03:06 PM UTC

   Dear clients, A fix was deployed at ~14:50 (UTC), restoring full service to live API endpoints. We are monitoring the results and working to prevent any possible future recurrence. Note on API Usage: If your account has made additional requests as a result of this incident and risks exceeding its allowance (or already has), please let us know and we'll make sure your access is not affected for the remainder of your service month. There is no need to upgrade your subscription in this case. If you have already upgraded as a result of unexpected overage, please contact us and we will be happy to help. If you experience any further issues, please contact us at [email protected]. Thank you for your patience whilst we worked to resolve this issue. We will provide a further update once full remediation is in place.

9. resolved Jan 27, 2026, 03:08 PM UTC

   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]

Read the full incident report →