Resolved -
Between 12:47 and 19:00 UTC, a subset of users running test sessions on Chrome 149 and 150 experienced an elevated rate of idle timeouts. This was caused by an configuration change, which has since been identified and rolled back.
The issue is now fully resolved, and sessions on Chrome 149/150 are operating normally.
Jul 7, 19:00 UTC
Investigating -
We are currently investigating this issue.
Jul 7, 12:47 UTC