17th July 2019

Resolved

Issue has been resolved and API performs normally again. The issue was caused by a faulty migration database query.