We've now resolved the incident. Thanks for your patience. We are still working on removing the faulty component to prevent this from happening in the future.
We are experiencing 500 errors again on the OHLCV data and are working on resolving the problem.