Jun 2, 08:53 UTC
Resolved - This incident has been resolved. Please contact us at [email protected] if you require any further assistance.
May 31, 10:50 UTC
Monitoring - This issue has now been resolved, however some clients may need to make modifications to their integration in order to continue to connect to our API, as our SSL certificate has been updated (for the majority of clients affected by this incident however no change should be required). We are continuing to monitor the situation and will update this notice if anything changes.
Please contact us at [email protected] if you experience any further issues connecting to our API, or if you need any additional support.
May 30, 21:28 UTC
Identified - We are continuing to investigate the issue concerning the Root CA expiry.
Please contact us at [email protected] if you are affected by this issue, or if you need any advice concerning the temporary workaround.
May 30, 19:03 UTC
Investigating - We are currently investigating an issue affecting a number of clients, which appears to be the result of the expiry of the AddTrust External CA Root (root certificate) on 30 May 2020.
While our SSL certificate is valid until 5 January 2021, and our API instances and website are fully operational at present, clients that are affected by this issue may receive "Certificate expired" errors on attempting to connect to our API.
We are currently working to identify which clients may be affected by this issue, and the steps that are required to remedy it. We will update this notice as soon as we have any further information.
Please contact [email protected] if you experience any issues connecting to our service.
Sep 14, 09:35 UTC
Resolved - This incident has been resolved.
Sep 11, 09:00 UTC
Investigating - We are currently experiencing an issue with USD/UGX (Ugandan Shilling) currency rates, which is also affecting other currency pairs with UGX. The USD/UGX rate is currently reporting at approximately 37.06, instead of the correct value of approximately 3,706. We are working with our data contributors to identify and resolve this issue as soon as possible. Other currency rates that do not involve the UGX symbol are not affected.
Jan 4, 17:36 UTC
Resolved - This incident has been resolved.
Jan 4, 16:49 UTC
Investigating - We are currently investigating slow response times affecting some API clients. Please bear with us for more updates.
Jan 5, 00:52 UTC
Resolved - This incident has been resolved.
Jan 4, 19:21 UTC
Investigating - We are again experiencing slow responses from our API. We will update this notification as soon as we have further information.
Jan 6, 13:40 UTC
Resolved - This incident has been resolved.
Jan 5, 23:41 UTC
Monitoring - 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.
Jan 5, 17:10 UTC
Investigating - 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.
Apr 30, 00:00 UTC
Resolved - This incident has been resolved.
Jan 6, 00:13 UTC
Update - 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.
Jan 5, 09:48 UTC
Identified - 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.
Jan 4, 20:42 UTC
Investigating - 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.
Jun 6, 11:00 UTC
Resolved - This incident has been resolved.
Jun 4, 11:39 UTC
Investigating - 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.
Aug 24, 09:47 UTC
Resolved - 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].
Aug 22, 11:50 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 22, 11:12 UTC
Identified - We have identified the cause of the incident occurring today, and we are working on a solution. Thank you for your patience.
Aug 22, 09:30 UTC
Investigating - We are investigating a technical issue with our infrastructure that is causing API 500 errors. Please stand by for updates.
Oct 31, 11:54 UTC
Resolved - 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.
Oct 31, 07:47 UTC
Monitoring - 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.
Dec 24, 09:39 UTC
Resolved - 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.
Dec 23, 14:15 UTC
Monitoring - 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.
Dec 22, 23:41 UTC
Update - 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.
Dec 22, 16:41 UTC
Identified - 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.
Dec 22, 14:09 UTC
Monitoring - 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.
Dec 22, 13:53 UTC
Identified - 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.
Dec 22, 13:19 UTC
Update - 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.
Dec 22, 12:37 UTC
Investigating - We are investigating a confirmed incident that is affecting our API and causing 400 errors. Please stand by for updates.