We've optimized the database working set size to resolve this issue.
The API has returned to normal operational capacity.
