We've optimized the database working set size to resolve this issue.
The API has returned to normal operational capacity.
We're investigating an issue that is causing high latency in the API.
No incidents reported
