This incident has been resolved.
Our data processing infrastructure is running behind which is causing delays in the OHLCV data. System should be caught up shortly.
14:53 UTC - 4 May 2018