Uniqkey incident
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
Uniqkey experienced a minor incident on August 19, 2026 affecting Browser Extension and Mobile App, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 19, 2026, 09:03 AM UTC
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.
- identified Aug 19, 2026, 10:39 AM UTC
The disruption has been identified as unexpected behavior on our service provider's end. We're awaiting further information from them.
- monitoring Aug 19, 2026, 11:30 AM UTC
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.
- resolved Aug 20, 2026, 09:41 AM UTC
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.