[RESOLVED] - We were able to isolate the issue to a database query which was not optimized. We've fixed the issue and the response times are back to normal status.
[INITIAL] - We are experiencing higher than normal API latency on one of the database segments and we are working on it.
