All Systems Operational
Exchange Rate API ? Operational
Website ? Operational
Account Dashboard ? Operational
Status Page ? Operational
API Documentation ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Dear clients,

On 31 March 2017, we will remove four officially deprecated currencies from our 'latest.json' API. These are:

– Estonian Kroon (ISO currency code: EEK), succeeded by the Euro on 1 January 2015.
– Maltese Lira (ISO currency code: MTL), succeeded by the Euro on 1 January 2008.
– Lithuanian Litas (ISO currency code: LTL), succeeded by the Euro on 1 January 2015.
– Latvian Lats (ISO currency code: LVL), succeeded by the Euro on 1 January 2014.

These currencies were convertible for a short period of time following their replacement by the Euro and were available in our live API for historical reference.

They will continue to be available in our 'historical' API and this change will not involve any outage or downtime.

You can learn more about each of these currencies below:

https://en.wikipedia.org/wiki/Estonian_kroon
https://en.wikipedia.org/wiki/Maltese_lira
https://en.wikipedia.org/wiki/Lithuanian_litas
https://en.wikipedia.org/wiki/Latvian_lats

Please don't hesitate to contact us if you have any questions, comments or concerns about this change.

Open Exchange Rates
support@openexchangerates.org
Posted on Jan 30, 17:06 UTC
System Metrics Month Week Day
API Uptime ?
Fetching
Past Incidents
Mar 27, 2017
Completed - The scheduled maintenance has been completed.
Mar 27, 07:53 UTC
Scheduled - Dear clients,

We are pleased to announce that on 27 March 2017, we will add two new currencies to our API. These are:

– South Sudanese Pound (ISO currency code: SSP)
– Chinese Yuan 'Offshore' (ISO currency code: CNH)

Both will appear in our standard `rates` response. They will also be available in our `historical`, `time-series` and `convert` API endpoints beginning on the same date, and each will be available as a `base` currency.

This change will not involve any API downtime and there is no change to any of the API request or response formats.

You can learn more about each of these currencies below:

https://en.wikipedia.org/wiki/South_Sudanese_pound
https://en.wikipedia.org/wiki/Renminbi#Other_markets

Please don't hesitate to contact us if you have any questions or comments about this change.

Open Exchange Rates
support@openexchangerates.org
Mar 13, 14:33 UTC
Mar 26, 2017

No incidents reported.

Mar 25, 2017

No incidents reported.

Mar 24, 2017

No incidents reported.

Mar 23, 2017

No incidents reported.

Mar 22, 2017

No incidents reported.

Mar 21, 2017

No incidents reported.

Mar 20, 2017

No incidents reported.

Mar 19, 2017

No incidents reported.

Mar 18, 2017

No incidents reported.

Mar 17, 2017
Resolved - 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.
Mar 17, 19:15 UTC
Monitoring - We have resolved the immediate issue and API service has returned to normal. We are continuing to monitor and apologise for any inconvenience caused.
Mar 17, 04:38 UTC
Update - 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.
Mar 17, 04:21 UTC
Identified - 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.
Mar 17, 02:33 UTC
Mar 16, 2017

No incidents reported.

Mar 15, 2017

No incidents reported.

Mar 14, 2017

No incidents reported.

Mar 13, 2017

No incidents reported.