Root causes of this issue ware the same as in case of incident https://status.mews.li/incidents/3l5f7xp2t0b2. So the postmortem of that incident applies here as well. Unfortunately, we were provided with RCA of the previous issue by our cloud provider only two weeks after it happened, therefore we could not apply solutions on time to prevent this incident happening.