Is Uniqkey down?

We are investigating the issue. All data is available in the Uniqkey mobile app.

The issue has been resolved, and data is available across all Uniqkey platforms as usual.

Some users may have experienced delays, lack of in-app notifications, and connectivity issues. It should be resolved now, but we're monitoring the situation closely.

Some users still report lack of in-app notifications, delays, etc., and we're working to restore service for everyone. In the meantime, data is still available in the Uniqkey mobile app. We sincerely apologise for the inconvenience.

The issue should be resolved for everyone, but we're still keeping a close eye on all systems.

Between 22:04 on 13 October and 08:08 on 14 October (CEST), some features were unavailable or delayed. This affected approving requests in the mobile app, in-app notifications, connecting new devices, sharing, and import/export.   The disruption started during scheduled maintenance at our hosting provider. We're improving our setup and monitoring so that a similar issue is handled automatically and faster in the future.

Some users may experience longer loading times or timeouts with the Uniqkey browser extension. We're investigating the cause, and will update our status page as new information becomes available.   In the meantime, all data is still available in the Uniqkey mobile app.   We sincerely apologise for the inconvenience.

The incident is tied to technical issues on our service provider's side. We've reached out to them, and are following the situation closely. Uniqkey users may also experience inability to access data stored in extension even though the accounts are visible, grey icons in login forms, being asked to resume onboarding, or other unfamiliar errors. This is all caused by the current incident, and will be resolved once our provider is up and running again.

The issue with our service provider has been resolved, and all systems are slowly coming back online. Please allow for an additional 10-15 minutes of longer loading times and sporadic issues until everything is back to normal.

Users can experience connectivity issues in the browser extension. We're investigating the problem and will update with further information as soon as it's available. In the meantime, data is still visible in the Uniqkey mobile app. We apologise for the inconvenience.

All systems should be up and running again.

Some users might experience brief moments of connection issues to our servers. We're investigating the issue. All data is still available in the Uniqkey mobile app.

The disruption has been identified as unexpected behavior on our service provider's end. We're awaiting further information from them.

Service was fully restored at 13:10 CEST. All applications are operating normally. We identified the cause and applied a fix ourselves, restoring service without waiting for the provider. The disruption was caused by an infrastructure migration performed by our managed database provider, which changed the database connection endpoint and left the previous one non-functional. Our platform was unable to reach the database as a result. All data written before the incident began is intact. Actions attempted during the disruption failed visibly with an error and were not partially applied - please retry anything that did not complete. Impact window: 10:43-13:10 CEST (2 hours 27 minutes) We are following up with our provider on why this migration ran during business hours and outside the schedule they communicated, and we are making changes to remove this dependency so a similar provider-side change cannot affect our service again. We apologise for the disruption.

Service has been stable since restoration at 13:10 CEST on 19 August, and we are closing this incident. Impact window: 10:43-13:10 CEST on 19 August (2 hours 27 minutes), affecting the The cause was an infrastructure migration performed by our managed database provider, which upgraded our managed database provider without proper notice. We have raised a formal case with the provider covering both the migration itself and how it was communicated, and we are reviewing the affected part of our infrastructure to reduce our reliance on it. We apologise for the disruption.