[RESOLVED] - The root cause of the issue was related to an error in performing a lookup for checking user permissions. We've identified and deployed a fix to resolve the issue. Operations are restored to normal status.
[INITIAL] - We are experiencing higher than normal API latency on one of the database segments and we are working on it.
