We immediately began investigating the issue and our engineers started working on identifying the root cause.
At 09:04 CET, our engineers identified the issue to be related to database resources.
At 09:13 CET, we upgraded our resources.
At 09:25 CET, the instance was scaled up and the issue was resolved. We have performed a Root Cause Analysis of this incident and are implementing solutions in order to prevent such instances from happening in the future.
We sincerely apologize for any inconvenience that this may have caused.