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.
Posted about 1 year ago. Dec 20, 2016 - 09:33 UTC
We resolved this issue via a deployment at 12:45 UTC, and will publish a post-mortem shortly.
Posted about 1 year ago. Dec 18, 2016 - 13:23 UTC
We have identified the issue and are working on a resolution.
Posted about 1 year ago. Dec 18, 2016 - 11:14 UTC
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.