User impersonation for Connect apps is not working

On 28th Feb between 12:15 UTC and 15:20 UTC Connect apps were unable to perform user impersonation operations. We have identified fault and resolved it by scaling up the infrastructure. The incident is now resolved.

We will now engage in post incident review and detailed root cause investigation, which will be shared in form of public PIR.

Starting from 13:15 UTC, all user impersonation operations done by Connect apps in all regions using ACT_AS_USER scope were failing.

We have scaled up the underlying service responsible for tokens generation and we're seeing an improvement in response times and success rates. We continue to investigate the root cause and will provide the next update by 18:00 UTC, in 2h from now.

We have identified a problem with Connect apps where user impersonation is not working properly. We are investigating the root cause and will provide another update by 14:30 UTC.