The incident has been resolved. Browser extension 5.11.1 and API 5.11.0 are now available. If you're still experiencing the issue, please ensure your browser extension is updated to 5.11.1. If the problem persists, update your API to 5.11.0 as well.
The main issue has been identified and the incident has been resolved.