Our team has identified an issue related to a long-running database migration script. The problem was fixed and the API is available again.
