Is Open Exchange Rates Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

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.

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.

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.

This incident has been resolved.

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.

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 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.

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.

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

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

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

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.

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

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

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

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

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.

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.

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 support@openexchangerates.org if you need any further support.

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.

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 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 have identified the issue, and are continuing to work on a solution.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

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 currently investigating connection failures on our API. Please stand by for updates.

This incident has been resolved.

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.

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.

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

This incident has been resolved.

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

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.

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

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 support@openexchangerates.org if you experience any further issues.

This incident has been resolved.

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 support@openexchangerates.org if you need any additional support.

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

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.

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 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 continuing to investigate this issue.

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

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

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

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 support@openexchangerates.org if you encounter any further issues.

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.

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.

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.

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.

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.

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 investigating a confirmed incident that is affecting our API and causing 400 errors. Please stand by for updates.

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

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 support@openexchangerates.org if you have any questions or concerns relating to this incident.

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 support@openexchangerates.org.

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

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

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

This incident has been resolved.

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.

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 support@openexchangerates.org if you experience any further issues connecting to our services.

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 support@openexchangerates.org, regarding having their usage allowance reset. Please contact us if you experience any further issues connecting to our service.

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.

This incident has been resolved.

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 support@openexchangerates.org if you experience any further issues relating to BTC, ETH or LTC rates.

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.

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.

We are currently investigating slow response times affecting some API clients. Please bear with us for more updates.

This incident has been resolved.

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.

This incident has been resolved. Please contact us at support@openexchangerates.org if you require any further assistance.

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 support@openexchangerates.org if you experience any further issues connecting to our API, or if you need any additional support.

We are continuing to investigate the issue concerning the Root CA expiry. Please contact us at support@openexchangerates.org if you are affected by this issue, or if you need any advice concerning the temporary workaround.

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 support@openexchangerates.org if you experience any issues connecting to our service.

No further incident has been observed related to today's database maintenance. In total, we observed a total of around 3 minutes of unplanned service downtime, comprised of several shorter outages occurring between 15:31 UTC to 15:35 UTC on Saturday afternoon. We do not anticipate any further issues in relation to this maintenance and we apologise for any inconvenience this may have caused. Please don't hesitate to contact us at support@openexchangerates.org if you have any questions or concerns.

We are monitoring a minor service outage occurring on the openexchangerates.org API and website on Saturday afternoon. This began at approximately 15:30 UTC and was caused by scheduled database maintenance. Requests may receive "Service Unavailable" errors while this is occurring. We apologise for any inconvenience this may cause.

This incident has been resolved.

We are investigating a spike in API response times that affected a number of clients' integrations yesterday (December 27th) between 12:00 and 22:00 UTC. Please contact support@openexchangerates.org with any questions or concerns related to this issue.

This incident was resolved with an update on Monday 27th August with no recurrence. We are contacting affected clients. Please email us at support@openexchangerates.org if you have any questions or concerns about this update.

We are investigating an issue affecting KRW (South Korean Won) rates available via our latest.json API endpoint on Sunday evening, during which clients may have received rates at a ratio of 1:100. We have put a temporary solution in place, and will publish more details as they become available.

We deployed our new platform infrastructure this morning, bringing a load-balanced, high-availability backend to our industry-leading API. Despite several weeks' extensive testing to prevent issues to our clients, this change resulted in an unforeseen SSL certificate issue, which meant that a subset of clients were unable to access our API via curl. Affected clients received errors like: *"curl: (60) SSL certificate problem: unable to get local issuer certificate"*, and could not access the API without changing their integration to non-verified SSL or plain HTTP. We posted a status page update at 08:47 UTC, shortly after first discovering the issue. As soon as we realised it would take longer than a few minutes to address, we redirected all traffic back to our previous infrastructure at 09:04 UTC, to allow us time to identify and deploy a solution. On investigation, we discovered that the issue was caused by a missing certificate-chain that was accidentally left out when our server certificate was created on AWS. To resolve this, we added the certificate bundle to our SSL certificate, and then directed traffic back to our new infrastructure at 09:30 UTC. We anticipate that fewer than 5% of clients were unable to connect for up to 45 minutes. Regrettably this issue didn't manifest during testing, because only clients that didn't have the latest certificates on their system were affected. In addition to the above, we have received several edge-case issue reports involving non-standard API integrations (in particular, where our legacy API was more lenient towards malformed parameters) and are working with affected clients to resolve any issues caused. Other than these, we're happy to report our new API infrastructure is fully operational. Please don't hesitate to contact us at support@openexchangerates.org if you experience any unexpected behaviour when connecting to our API. Open Exchange Rates

This incident has been resolved.

We have deployed a solution and continued with our infrastructure migration as planned. We'll publish a post-mortem shortly, detailing the issue and steps we took to resolve it. In the meantime, please email us at support@openexchangerates.org if you experience any further issues connecting.

We have redirected all API traffic to our previous architecture while we investigate an issue that prevented some clients from connecting to our API via curl. Please let us know at support@openexchangerates.org if you continue to experience any issues.

We have recently completed our migration to new infrastructure, and we are investigating an SSL certificate issue when attempting to access our API via curl. We will update this page as soon as we have more information.

We experienced an API issue yesterday, after making a small change to our platform in preparation for migrating to our revamped infrastructure next week. This change resulted in an unanticipated permissions conflict, meaning that about 400 clients were unable to access our "latest.json" API endpoint between approximately 03:00 and 06:20 UTC. Instead of their regular up-to-date exchange rate information, affected clients received an error message stating that their App ID was invalid. The change we made was in a section of our production environment data pipeline that lies outside of our regular deployment path, and was not picked up by our independent monitoring due to the specific conditions under which it occurred, so we were unable to catch the error ahead of time. As soon as we received notice that clients were unable to access our latest API endpoint at 06:00 UTC, we investigated, detected and deployed a fix for the error. From 06:20 UTC, affected clients were once again able to access our latest API. Any client who had cached a response locally during that time may have continued to experience errors in their integration until their cache was renewed. This incident was caused by human error. We have tightened up our pre-deployment review procedures in response, to ensure that it can not happen again. We apologise that this occurred and sincerely hope it didn't cause severe issues for you or your business. Please don't hesitate to contact support@openexchangerates.org with any questions or comments. William Crowcroft - Founder & CEO, Open Exchange Rates

We have resolved this issue, which affected around 400 users of our service who were unable to fetch rates for approximately 30 minutes, and will write a post-mortem report this afternoon. Thank you for your patience.

We have identified the issue and are deploying a fix.

We are investigating an issue affecting some users of our API and will post again as soon as we have an update. Apologies for any inconvenience and please contact support@openexchangerates.org with any questions.

Dear clients, In an issue related to yesterday's changes, certain alternative digital currency rates – including DASH, STR, XMR and XRP (but not including BTC, LTC and ETH) – were published as inverted prices throughout the night. This was due to a provider error, which has now been resolved, and we do not anticipate further related issues. Going forward, we are working on broad improvements to our line-up of digital currencies, which will enable us to feature new popular digital assets and a wider range and granularity of information. Please contact us at support@openexchangerates.org with any questions or concerns.

Dear clients, We have resolved an issue which caused some digital currency prices, including Dash (DASH), Monero (XMR) and Stellar (STR), to be delayed for up to 36 hours until this evening (Friday 15th September). While deploying changes to correct this issue, these and other prices in our "alternative" rates set may have become briefly unavailable and/or unstable for brief periods between 20:00 and 23:00 UTC. Prices for Bitcoin (BTC), Ethereum (ETH) and Litecoin (LTC) were not affected. We sincerely apologise for any inconvenience this may have caused. Please contact us at support@openexchangerates.org if you have any questions or concerns regarding this issue.

This incident has been resolved.

We have resolved the issue, and all digital currency rates are updating as normal. We will post a final update on this incident shortly, but please contact us if you have any comments or questions.

We have installed a temporary solution addressing the primary issue, which affected all digital currencies, as well as a small number of exotic and alternative currency rates. Rate updates may be delayed up to 60 minutes, while we establish a permanent fix. We'll provide more update as soon as possible.

We are looking into delays in rate updates for certain currency rates, including Bitcoin and other digital currencies, which began around midnight UTC. Major world currencies and the majority of exotic currencies are not affected. We will provide an update as soon as we have further information.

We have resolved this incident affecting five exotic currency rates. This issue began at approx. 10pm last night (16th August), when rates for IRR, STD, VND, IDR and KGS appeared to fluctuate widely, and was resolved at 8:35am today (17th August). The following currencies were affected: IDR - Indonesian Rupiah IRR - Iranian Rial KGS - Kyrgystani Som STD - São Tomé and Príncipe Dobra VND - Vietnamese Dong Rapid rate fluctuations were based on information received from contributors and passing safety checks, and we're continuing to look into how this happened to prevent it from happening again. We apologise for any trouble caused by this incident.

In an issue related to the fix that we made yesterday, rates for five currencies (IRR, STD, VND, IDR, KGS) fluctuated widely in error overnight. This was due to an issue at source for these rates, which we have now corrected. We are assessing the extent of the issue and will provide further update shortly.

The issue that affected your API service on June 29th was caused by an unusual underlying hardware failure at Amazon Web Services, relating to our Redis ElastiCache. AWS have informed us that the failover process (by which the master node is replaced by a replica in the event of failure) encountered a rare unrecoverable error, and manual intervention was needed by their technicians to correct it. There have not been any related issues since then.

We experienced an API outage this morning, caused by upstream issues at our infrastructure and cloud services provider, Amazon Web Services (AWS), in their US East (N. Virginia) region. This incident manifested as a high number of 5XX errors and timeouts for our API clients, lasting for a period of about 2 hours between approximately 06:05 and 08:07 UTC. Our platform is built on AWS for high availability, with multiple layers of automatic failover and redundancy. As soon as we realised failover was not happening as expected, we worked with AWS support to identify the issue and were told "There was a internal hardware failure, that is supposed to be automatically recovered, but the recovery process failed." They were able to resolve the issue and service returned to normal shortly after 8am. We are continuing to monitor throughout the day and waiting on further post-mortem from AWS. Going forward we are also investigating further safeguards or precautions we can take against such issues which arise outside of our control. While our API did not suffer a total outage, during the failure period clients received a high proportion of failures and extremely high latency for any successful responses. We sincerely apologise for any issues caused by this outage. If you have any questions or concerns about this incident, please don't hesitate to contact us at support@openexchangerates.org.

We have now resolved the underlying cause and all systems are back to full health. This was a caching issue, which caused slow responses and intermittent timeouts while connecting to the API, but did not result in any major outage. Please don't hesitate to contact us at support@openexchangerates.org with any questions or concerns.

We are investigating an issue causing slow API connections and occasional timeouts for some clients. We appreciate your patience and will provide further update as soon as possible.

This issue began at around midnight UTC on the 17th March, and was resolved at approximately 4am UTC, with full service restored by 4.45am. This was an uncharacteristic outage, triggered by a spike in requests occurring shortly after midnight UTC, combined with an unforeseen issue with AWS ElastiCache, which led to critically high database connections and CPU utilisation. At this point, clients began receiving timeouts, and began retrying their requests at a high frequency, which further multiplied the issue [1]. By this stage, our auto-scaling infrastructure was not able to mitigate the issue and manual intervention was required. After investigating to ascertain the root causes, we rolled out a temporary solution which resolved the immediate bottlenecks. This included temporarily switching off API usage logging, and doubling our overall database capacity (logging has since been restored and clients' usage statistics are fully up-to-date). We then worked to identify, implement and deploy a number of long-term solutions and caching improvements in response to the events that directly preceded this outage and the specific failures that they triggered, and we continued to monitor throughout the day. We are confident that the improvements we have made today will prevent this issue from happening again. We sincerely apologise for any inconvenience this outage may have caused you. Please don't hesitate to contact us at support@openexchangerates.org with any questions, comments or concerns about this incident. Kind regards, – Open Exchange Rates Team [1] Retrying failed requests is a common integration practice, although we strongly recommend waiting at least 1 second in between retries to maximise the chance of a successful response.

We have resolved the immediate issue and API service has returned to normal. We are continuing to monitor and apologise for any inconvenience caused.

We have identified an issue in our AWS caching infrastructure which began at approximately 00:00 UTC on March 17th and caused a large volume of 500 errors and timeouts on API requests. We have performed a number of maintenance procedures to stabilise the issue and are now working to implement a solution.

We are looking into an API platform issue, which is causing intermittent timeouts and 500 errors for API clients. We will update as soon as we have any further information.

This platform issue caused request timeouts for many of our API clients, between approximately 00:30 UTC and 13:00 UTC on January 1st. This resulted from an unprecedented number of API requests on New Year's Day, occurring in a way that did not allow our platform to efficiently auto-scale, due to an unexpected bottleneck between our database and cache. We began investigation as soon as we became aware of this issue, and resolved it with a deployment later in the day. Although a small number of clients continued to experience occasional timeouts for up to 48 hours afterwards, we have not experienced a recurrence of this issue. We have since made further infrastructure updates to safeguard your service. We sincerely apologise for any inconvenience this may have caused you. Please rest assured that we continue to closely monitor our API platform and responses for unexpected behaviour, providing you with the consistent and stable service availability you expect. Please don't hesitate to contact us if you have any questions or concerns about this incident. Warm regards, Open Exchange Rates Team

This incident caused connection timeouts for a large number of API clients. We have now deployed a fix and will continue to monitor throughout the day, with a post-mortem to follow shortly.

We are continuing to investigate this issue and will provide an update as soon as we have further information.

A number of clients have reported receiving timeouts while connecting to our API over the past few hours. We are investigating and will respond as soon as we have further information.

We have resolved this issue, and as of 4:00pm UTC all Time Series API requests are functioning as expected. Please don't hesitate to contact us with any questions or concerns.

We are investigating an issue affecting some clients using our Time Series (/time-series.json) API endpoint. The issue affects requests to `/time-series.json` which specify the same `start` and `end` dates (i.e. requests for a single day of data) and do not specify a subset of currencies via the `symbols` parameter. These requests incorrectly return a `400` error. All other API endpoints, and all other normal requests to the Time Series API (i.e. in all cases where a client requests multiple days of data or requests a specific subset of currencies via the `symbols` parameter), are unaffected. We will update this page as soon as we have resolved or have further information. Please contact us at support@openexchangerates.org with any questions or concerns.

This error occurred while upgrading our platform. We resolved this issue with missing historical data with a deployment on 17th December, and have taken steps to ensure that it will not happen again. Thank you for your patience.

We resolved this issue via a deployment at 12:45 UTC, and will publish a post-mortem shortly.

We have identified the issue and are working on a resolution.

A number of clients have reported data missing from our historical end-of-day API response for 17th December. We are currently investigating and will update as soon as we have further information. All other API endpoints and data are functioning as normal.

Dear clients, We have postponed our platform migration to Thursday 4th August. Our IP address will remain the same (185.24.96.251) until then. Your API service is not affected. In response to customer feedback, we're creating a static IP gateway for those who require a fixed IP address for their security infrastructure or firewall. Please contact us at support@openexchangerates.org if you need this facility, or if you have any other questions or comments. William J Crowcroft - Founder & CEO, Open Exchange Rates

Dear clients, From 03:00 UTC on Friday 22nd July, we will be serving your API requests from our new ultra-scalable, load-balanced infrastructure. This will enable us to serve you with responses up to 40x faster than before, but means we will no longer be able to provide a fixed (static) IP address. If you have previously whitelisted our server's IP address (185.24.96.251) in your firewall or proxy settings, you'll need to update your configuration to whitelist our domain instead ("https://openexchangerates.org"). If you haven't specifically whitelisted our IP address, you don't need to change anything. You also don't need to change anything in your integration (our API request and response formats will all remain exactly the same). If you need any support, or have any questions or concerns regarding this change, please don't hesitate to contact us at support@openexchangerates.org. - Your Open Exchange Rates Team

If you rely on our Belarusian ruble data, you may already be aware that a new Belarusian ruble will be introduced on Friday, July 1st, 2016, at a rate of 1 new ruble to 10,000 old rubles. We'll offer the new Belarusian ruble under its ISO 4217 code "BYN", in both our latest and historical APIs, as soon as the re-denomination goes into effect on July 1st. Old and new rubles will circulate in parallel until December 31, 2016, so we'll continue to provide the old ruble under its symbol BYR until the end of the year. Please don‘t hesitate to raise any questions or discuss any concerns with us at support@openexchangerates.org.

This incident was caused by an upstream issue at our web host, manifesting in delayed responses (30s+) and timeouts for a large number of our clients. It's our responsibility to safeguard the availability of our service to you; we've already deployed changes to our API platform to prevent a recurrence and our monitoring has not detected any further issue since May 4th. Thanks for your patience while we scale up to be able to serve you better. Please contact support@openexchangerates.org with any questions.

We experienced an unplanned service outage on both our primary API and website last night. We're looking into the cause right now and will update as soon as we know more. Sincere apologies for any inconvenience caused.

We have successfully deployed these changes. Please contact us at support@openexchangerates.org with any questions or feedback.

On Wednesday morning, we're adding two new alternative rates for Venezuelan Bolivar (VEF), for clients who specifically request them. *No other rates or endpoints are affected.* If you rely on our VEF data, please read on to see how this change may affect you. A new dual foreign exchange system recently came into effect in Venezuela, replacing the previous 'Simadi' system. This new official system consists of one rate "fixed" at 10 bolivars to the US dollar (named 'Dipro'), and another "floating", currently at a rate of approximately 250 bolivars to the US dollar (named 'Dicom'). We offer alternative, black market and niche digital currency rates via our 'show_experimental' API parameter (currently in stable beta). At 10:00am UTC on Wednesday, 30th March we'll be adding two corresponding symbols to these alternative rates, 'VEF_DIPRO' and 'VEF_DICOM', updated at least hourly. One week later, on Wednesday 6th April, we'll remove the previous 'Simadi' rate (listed as 'VEF_SIMADI'). We're continuing to provide live rates for the local Venezuelan black market (where US dollars currently fetch around 1,171 bolivars) under the symbol 'VEF_BLKMKT'. To access the new alternative rates, you can use the "experimental" parameter with our standard API responses. Please see documentation for details (information for Dipro and Dicom will be added along with the change on Wednesday): https://oxr.readme.io/docs/experimental-currencies Our standard API rate for Venezuelan Bolivar (listed as 'VEF') is still tracking with all other online sources, at approximately 6.33 to the US dollar, however we recommend clients with operations in Venezuela take care to choose the most appropriate rate for their integration. We're continuing to monitor the economic climate closely, to provide you with the best available data for your business. Please contact us at support@openexchangerates.org with any questions or feedback. Open Exchange Rates Team

We have successfully made the upgrades to our API infrastructure, with a total of 10m downtime. Please email support@openexchangerates.org with any questions or comments.

We're deploying server upgrades today to increase capacity and resolve recent short periods of downtime. Our API, website and client dashboard will be unavailable for approximately 10 minutes, at or shortly after 3pm UTC. Thank you for your patience and apologies for any inconvenience caused while we make these essential changes to improve our service. Please email support@openexchangerates.org if you need anything.

This outage was caused by an upstream server issue at our hosting provider, and we're taking steps to stop it happening again. Sincere apologies for any disruption caused.

We experienced an unidentified hosting provider issue last night resulting in approximately 5 minutes' outage on both the API and public website, from 12:35am UTC. All systems returned to normal without intervention. Sincere apologies for any disruption caused. We're investigating why this happened today and will post a debrief as soon as we have information.

We experienced an issue with our data warehouse between 00:09 UTC and 00:12 UTC on 20th January, affecting a subset of clients who requested live data from the API during that period. This was caused by a miscommunication between servers, resulting in failed response validation at the point of delivery to the client. Rather than deliver potentially inaccurate data, our system chose to return a non-specific error message. The issue resolved itself without intervention after approximately 3 minutes. We've been notified of this issue in the past, but until yesterday hadn't been able to replicate or determine the cause. We have now resolved this issue so it will not happen again. Please contact us at support@openexchangerates.org with any queries.

This incident has been resolved.

This has now been resolved, and we'll be publishing a more detailed postmortem on Monday.

We experienced an infrastructure issue affecting a certain number of our API clients, which caused historical requests for the 1st and 2nd of January 2016 to throw an error during delivery. Earlier dates and realtime/latest data were unaffected. This has now been resolved, and we'll be publishing a more detailed postmortem on our Status Page on Monday. Please accept our apologies for any inconvenience caused.

This incident has been resolved.

We're currently upgrading our front-end website and client account dashboard, in several stages. Visitors may see old pages alongside the new ones while we make the switch-over. This is a design and content issue only. The API is fully operational. Please contact us if you notice anything out of place or missing.

We experienced a short interruption in service today (approx. 20m) for a minority of clients, due to an upstream web host issue.

Slowdown was caused by a routine system maintenance task. We're taking steps to prevent similar issues. Please contact us if you experience any slow response times or timeouts.

We're investigating a short period (ca. 2 minutes) today where responses took longer than normal according to our monitoring. Functionality was otherwise unaffected.

Usage statistics are being displayed with up to 12 hours delay, otherwise functional. Please get in touch with any questions.

Usage statistics were temporarily delayed due to a non-critical database error. A fix has been deployed and usage stats will be recalculated for all clients over the next 2 days. At present and until further notice, API usage volume will take 24-48 hours to be reflected in your account dashboard. We apologise for any inconvenience caused.

Response times have returned to normal and we're continuing to monitor the situation. Please contact support@openexchangerates.org if you experience any connection issues.

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

We are investigating reports of API response times over 1000ms. Affected clients may be experiencing request timeouts.

A number of our clients received a blank response when attempting to access historical data for March 4th, between 00:00 and 10:00 today (March 5th). This has been resolved and new checks put in place to ensure it doesn't happen again.