We have now resolved the incident. Thank you for your patience.
We've fixed the core issue related to the endpoint randomly responding with 500 errors, but further looking at possibilities to lower the response time.
We are working on lowering the absolute value of response time and also the stability of response time (variance) for the OHLCV endpoint. Apologies for the inconvenience and thank you for your patience.