Elevated 503 errors in accessing the API

Resolved

We are currently investigating the cause of it, but we possess all the required information and the reproduction steps of this case to make sure it will be eliminated for the future.

In the maintenance window related to the historical API access we had a period where the API could respond with the deliver the 503 error.

Began at: