Uniqkey experienced a major incident on January 23, 2026 affecting Browser Extension App, lasting 6h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 23, 2026, 06:58 AM UTC
We have received reports of the Uniqkey extension not loading in Edge, which we're currently investigating. In the meantime, other browsers like Chrome, Safari and Firefox should work as intended. We apologise for the inconvenience.
- identified Jan 23, 2026, 07:53 AM UTC
Current research indicates that this might be related to an general issue with Microsoft edge version 144 and not Uniqkey itself. Downgrading to a previous version, or upgrading to the Edge beta version 145 can resolve the issue.
- identified Jan 23, 2026, 07:54 AM UTC
Current research indicates that this might be related to an general issue with Microsoft edge version 144 and not Uniqkey itself. Downgrading to a previous version, or upgrading to the Edge beta version 145 can resolve the issue.
- monitoring Jan 23, 2026, 11:40 AM UTC
After investigating the situation, we have managed to create a hotfix to work around the bug introduced in the latest version of Chromium (Version 144). The issue impacts all extensions using modern asynchronous messaging patterns, not just Uniqkey. This new version of Uniqkey will ensure seamless communication between the extension and mobile app, regardless of the bug introduced in the Chromium build. Our fix has been sent to review in the app stores, and we expect it to be live at the beginning of next week. Once it has been published, your extension will be updated automatically. In the meantime, other browsers are still reliable alternatives, and all data is available in the Uniqkey mobile app as well. Uniqkey extensions for supported browsers can be found here: https://www.uniqkey.eu/install Any questions can be directed to our Support team via [email protected].
- resolved Jan 23, 2026, 02:13 PM UTC
Microsoft has made some changes behind the scenes, which now allows extensions to function as usual. If any issues persist, relaunching the browser should resolve it. We're still expecting our hotfix to be deployed next week, but it's not necessary to wait for this to use Uniqkey in Edge again.