Istoricul incidentelor Open Exchange Rates

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

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

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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]

Dear clients, we are currently experiencing a technical issue that is causing a delay in updating exchange rates in our API. We apologise for the inconvenience caused. Please stand by for updates.

The issue has been identified and relates to an upstream issue with one of our data contributors. We are continuing to work on resolution on our side, and working with our data contributor to establish a timeline for resolution.

The data contributor issue has been resolved and rate updates have resumed as normal. We are monitoring the ongoing performance of the API and will provide a further update shortly. We apologise for any inconvenience caused.

This incident has been resolved.

We are currently undergoing unscheduled maintenance on our caching infrastructure. API connectivity will be impacted for up to 1 hour. During this time, clients may experience timeouts when connecting to the service. We apologise for any inconvenience this may cause.

We are currently experiencing unplanned API downtime, caused by an application error that occurred during automatic maintenance to our AWS caching infrastructure. We are actively working to get the service back up and running as soon as possible. However, we are not able to provide an ETA at present. We sincerely apologise for the inconvenience caused.

We have implemented a fix and connectivity to the API is now restored. We are continuing with remediation steps and monitoring all systems closely to ensure continued operation. Please note that historical data availability may be affected between approximately 07:30 and 12:00 UTC.

This incident has been resolved.

We are currently investigating a technical issue affecting our API and causing service interruption for clients. Please stand by for updates.

The issue affecting our caching infrastructure has been identified and we are currently working to restore full operation.

A fix has been implemented and we are monitoring the results.

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.

We are currently investigating a platform issue that is resulting in API timeouts. Please stand by for updates.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved. The service degradation began at approximately 07:10 UTC, and was resolved by 08:10 UTC. During this time, some clients received 500 error messages in response to their API requests. This was the result of a misconfiguration during regular scheduled platform updates that was caused by a cache recovery event that occurred at the same time. We do not anticipate a recurrence.

We are currently investigating connection failures on our API. Please stand by for updates.

Please be advised Open Exchange Rates API is currently running with partial outage. Latest and historical rates for today's date, and other API queries, may be unavailable. We are continuing to investigate this issue.

We are continuing to investigate this issue.

We have identified the issue, and are continuing to work on a solution.

We will shortly undergo a maintenance window during which our API and some areas of our website will be temporarily unavailable. Please refer to the separate Scheduled Maintenance update (to be posted shortly) for more details including the maintenance window time. We aim to keep this maintenance period to a minimum, however please be advised that the service may be unavailable for up to 30 minutes after the beginning of the scheduled maintenance.

We are continuing to work to restore the missing values to the API after this morning's service interruption. The following symbols are currently still affected by this incident and remain temporarily unavailable in our latest API results: > AOA, AWG, GEL, GMD, IRR, KMF, LRD, MVR, MZN, NAD, SBD, SDG, SRD, TMT, TND, VES, XCD, YER In addition, we will be undergoing scheduled maintenance at 12:55 UTC. We aim to keep this maintenance window as short as possible, however the API may be unavailable for up to 30 minutes while this is underway.

We are continuing to work to restore the missing values to the API after this morning's service interruption. The following symbols remain temporarily unavailable in our latest API results: > SRD, TMT, XCD Our earlier scheduled maintenance was successfully completed after approximately 12 minutes, with no reported API downtime during this period.

Missing currency symbols have now been restored to the live API results and we are continuing to monitor the service performance and investigating the root cause. Note: Although latest.json and historical/.json endpoints are restored, affected symbols may be unavailable for certain historical ohlc.json and spot.json requests coinciding with the incident period. Please contact us at [email protected] if you need any further support.

Please be advised that we experienced further issues relating to yesterday's incident this morning, beginning at 07:35 and causing degraded performance on our API. We are working on a solution and will continue to update this post with any additional information.

The repeat occurrence this morning began at 07:35 UTC, after which a small number of currencies appeared as unavailable in our service, and it was resolved again by 07:55 UTC. The API has been operational since this time. However, clients are advised that our incident response is still in progress, and we are continuing to work on full remediation. Although we are working hard to avoid any further disruption in service, it is possible that the API may experience further performance issues over the next 48 hours, while we implement our solution. Please stand by for further updates.

This incident has been resolved. We are continuing to make ongoing improvements to our platform to prevent any recurrence.

We are currently investigating missing currencies in historical API queries for 4th February 2023.

We have identified the cause of this incident and are working on a solution. Please be advised that both historical and OHLC queries are currently impacted, with approx. 61 currency rates showing as unavailable.

A fix has been implemented and we are monitoring the results. All rates that were unavailable for queries to the "/historical/2023-02-04.json" endpoint (4th February 2023) are now available again in the API response for that date. The following currency symbols were affected: AED, ANG, AOA, AWG, AZN, BIF, BOB, BYN, BZD, CDF, CLP, CNH, ETB, FJD, GEL, GMD, GTQ, GYD, HTG, ILS, IRR, ISK, JMD, JOD, KES, KGS, KMF, KYD, LRD, MMK, MOP, MRU, MVR, MYR, MZN, NAD, NGN, NIO, PGK, PHP, PKR, RWF, SBD, SDG, SRD, SVC, TJS, TMT, TND, TOP, TZS, UAH, UYU, UZS, VES, VND, XAG, XAU, XCD, YER, ZMW We are continuing to investigate the root cause of this incident. Please note that as a result of this issue, /ohlc.json and /spot.json queries will remain temporarily unavailable for the above currency symbols for the period between approximately 04:00 UTC on 4th February and 09:00 UTC on 5th February. We sincerely apologise for any inconvenience this may cause. We will update this post with further details in due course.

This incident has been resolved.

Please be aware that Bitcoin (BTC) and Ethereum (ETH) are currently operating with a delay in our API, with rate updates being published at a reduced frequency. We are working to rectify this as soon as possible.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We experienced an unexpected spike in SGD (Singapore Dollar) rates in the Open Exchange Rates API on Sunday 8th May, between approx. 07:15 UTC and 19:05 UTC. A fix has been implemented and we are continuing to investigate the root cause with our data contributors. Please contact [email protected] if you experience any further issues.

This incident was resolved at 19:05 UTC on 2022-05-08.

We experienced a minor API outage this morning during a routine system maintenance. The API was intermittently unavailable for a period of up to 20 minutes, starting from 07:40 GMT, before being corrected. We are currently investigating the root cause of this outage. Following this outage, a number of exchange rates are unavailable in our OHLC endpoint (ohlc.json). We are continuing to investigate this issue, and will provide further updates as soon as we have more information available.

The issue has been identified and a fix is being implemented.

We have completed restoring all missing currency values in our OHLC endpoint (ohlc.json) as of 15:30 GMT, and will continue to monitor the service closely for any further issues. As a result of this incident, historical spot and OHLCA information may be unavailable for certain currency and time period combinations between 07:30 and 15:30 on 20th February 2022. If you are affected by this, please contact us for advice. Please reach out to us at [email protected] if you need any additional support.

This incident has been resolved.

Following technical issues this morning, there are currently delays in rate updates in our latest.json and other live API endpoints. We are working on a resolution to this issue. Please stand by for updates.

This incident has been resolved.

We are currently investigating an issue that is causing intermittent downtime and 500 errors on our website and API, occurring since 06:50 UTC.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate further 5XX errors. Please stand by for updates.

We are continuing to investigate this issue.

This incident has been resolved as of 10:00 UTC. We are continuing to monitor API performance throughout the day. Please contact us if you encounter any further issues connecting to our services.

We are investigating a confirmed incident that is affecting our API and causing 400 errors. Please stand by for updates.

We are continuing to investigate this outage, which we believe may be connected to a wider service interruption at AWS (Amazon Web Services). Thank you for your patience.

We are working hard to resolve this connectivity issue, which we believe was caused by a power failure reported by Amazon Web Services in their us-east region. We will continue to update our status page as often as possible to keep you informed on our progress.

A fix was implemented at 13:55 GMT to temporarily redirect traffic away from the affected AWS resources. We are monitoring the results and carrying out further tests. Please note that clients may continue to experience degraded performance until the issue is fully resolved. We will provide further updates in due course, or in the event of any further incident.

As a result of the earlier outage at Amazon Web Services, a large number of currency symbols are temporarily showing as unavailable in our API. We believe this is related to a cache failover event that occurred as a result of the AWS incident. We are working to restore full service and will post further updates to our status page as soon as we have any updates.

We are continuing to work to restore missing data to the API, however the majority of currency rates have now returned to the API. We will continue to update our status page with additional details as they become available.

A fix has been implemented and we are monitoring the results. We will continue to update our status page with additional details as and when they become available.

This incident has been resolved and no further downtime has been experienced. We intend to publish a brief post-mortem in due course. Please contact us at [email protected] if you encounter any further issues.

We identified an issue with our cache infrastructure at 07:05 UTC on Sunday 31st October. Upon inspection this appeared to be the result of a cache failover event, which temporarily caused a spike in database connections, and caused "500 Internal Server Error" messages to be received by many clients. A fix was deployed at 07:31 UTC resolving the issue, and we are continuing to monitor the results. Please contact us at [email protected] if you have any questions or concerns relating to this incident.

This incident was resolved about 25 minutes after it started, and has not re-occured. Please contact us at [email protected] if you have any questions or concerns relating to this incident.

We are investigating a technical issue with our infrastructure that is causing API 500 errors. Please stand by for updates.

We have identified the cause of the incident occurring today, and we are working on a solution. Thank you for your patience.

A fix has been implemented and we are monitoring the results.

This incident was resolved at 11:40 UTC on Sunday 22nd August, approximately 3 hours and 45 minutes after it began. The issue related to a cache failover event, leading to certain parts of our API infrastructure becoming overburdened. While our service remained available during this time, up to approximately 50% of API requests may have received 500 errors. (NB: An earlier update to this incident report may have continued to show the API status as "partially degraded," however the service has been fully operational since the fix was implemented.) Please accept our apologies for any inconvenience caused by this incident. If you have any further comments or questions, please don't hesitate to contact us at [email protected].

We are investigating a brief period of connection timeouts and partial unavailability on the API taking place on Friday at approximately 07:45 UTC. We will update our status page as soon as we have any further information.

This incident has been resolved.

We are currently experiencing delays updating BTC, ETH, LTC, and other cryptocurrency rates (available via our 'alternative' endpoint parameter), which is unrelated to the service issues taking place yesterday and earlier today. We will provide updates via this notification as soon as we have more information. In the meantime, customers requiring updates for these symbols may wish to temporarily switch to an alternative service (such as the Coinbase API) to receive data for these symbols.

Rates for BTC, ETH and LTC are updating as usual as of approximately 22:24 UTC this evening. This incident was caused by a service outage at a third-party provider, and was not related to other technical issues over the past 48 hours. We are continuing to monitor these rates, as well as identifying changes that will prevent this issue from re-occurring, and we will provide a further update to our Status Page should any more information become available about this. Please note that while this particular incident is resolved, a number of cryptocurrency rates that were previously available in our application (under the 'alternative' rates endpoint parameter) are currently unavailable. Please refer to the following Status Page notification, where we will post updates regarding these: https://status.openexchangerates.org/incidents/4ztv8qh3ztmt Please contact us at [email protected] if you experience any further issues relating to BTC, ETH or LTC rates.

This incident has been resolved.

We are investigating an issue in our API that has caused certain rates to be unavailable in our service this evening. We will update this notification as soon as we have any further information.

The issue was identified and a fix was made last night. We are continuing to monitor the results and working to prevent any re-occurence and identify downstream issues that were caused. Please note that as a result of this incident, the Cuban Convertible Peso (CUC) symbol has been temporarily removed from our latest API results. All other rates should now be available as usual. Clients that found their integrations made a much larger volume of requests than normal (due to failed connections) should contact us at [email protected], regarding having their usage allowance reset. Please contact us if you experience any further issues connecting to our service.

While the technical incident that occurred yesterday has been resolved and our systems are stable, we are continuing to look into issues today regarding several currency symbols that are no longer available in our API, following the earlier incident. The following cryptocurrency symbols, which were previously only available when specifying the "show_alternative" rates endpoint parameter, are affected: EAC, EMC, FCT, FTC, NMC, NVC, PPC, VTC, and XPM. In addition, the deprecated Venezuelan Bolívar Fuerte (VEF) symbol is no longer available. The VEF currency symbol was deprecated and replaced by the newer Bolívar Soberano (VES) rate in August 2018, and this rate should be used instead. Please refer to the relevant historical Status Page update for more information about this change: https://status.openexchangerates.org/incidents/wrmzgmh6zwhy Please contact us at [email protected] if you experience any further issues connecting to our services.

This incident has been resolved.

We are again experiencing slow responses from our API. We will update this notification as soon as we have further information.

This incident has been resolved.