Uniqkey incident

As part of scheduled maintenance by our hosting provider IONOS, Uniqkey was mistakenly assigned a public IP address not associated with our service. As a result, our browser extension was unable to connect to our servers. The issue has now been resolved, and all Uniqkey platforms are operating normally again. We would like to emphasize that this was only a network availability issue, and not a security breach. No data was wrongfully accessed or compromised. We are currently working with IONO

Minor Resolved

Uniqkey experienced a minor incident on June 17, 2026 affecting Browser Extension, lasting 3h 4m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2026, 06:18 AM UTC
Resolved
Jun 17, 2026, 09:23 AM UTC
Duration
3h 4m
Detected by Pingoru
Jun 17, 2026, 06:18 AM UTC

Affected components

Browser Extension

Update timeline

  1. investigating Jun 17, 2026, 06:18 AM UTC

    Users might have experienced connection issues in the Uniqkey browser extension. This should be resolved now, and we're investigating the root cause. Further information will be shared as soon as possible. We sincerely apologise for the inconvenience. In case of connection issues with the extension, all data is still available in the Uniqkey mobile app.

  2. resolved Jun 17, 2026, 09:23 AM UTC

    As part of scheduled maintenance by our hosting provider IONOS, Uniqkey was mistakenly assigned a public IP address not associated with our service. As a result, our browser extension was unable to connect to our servers. The issue has now been resolved, and all Uniqkey platforms are operating normally again. We would like to emphasize that this was only a network availability issue, and not a security breach. No data was wrongfully accessed or compromised. We are currently working with IONOS to prevent this from happening again, and have taken measures to protect our service against similar mistakes from our providers. We sincerely apologise for the inconvenience. If you have any further questions, please reach out to [email protected].