Uniqkey incident
Uniqkey extension not working on Legacy platform (1.0)
Uniqkey experienced a critical incident on April 25, 2024 affecting [Legacy] Uniqkey Extension API, lasting 1h 51m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 25, 2024, 09:14 AM UTC
We are currently experiencing an issue with the Uniqkey extension on our legacy platform. This incident does not affect our customers on the Uniqkey 2.0 platform. Some customers may be unable to use the browser extension. Our engineering team has been notified and is actively investigating the root cause of this problem. We will provide further updates as more information becomes available. In the meantime, we apologize for any inconvenience this may cause. Thank you for your patience and understanding.
- identified Apr 25, 2024, 09:21 AM UTC
Our engineers have identified the root cause of the issue affecting the Uniqkey extension on our legacy platform. They are currently working on implementing a fix. We expect the problem to be resolved soon. Thank you for your patience and understanding while we work to resolve this matter.
- monitoring Apr 25, 2024, 09:40 AM UTC
The issue with the Uniqkey extension on our legacy platform has been resolved. Users should now be able to use the legacy version of Uniqkey without problems. Our engineering team is currently investigating the root cause of the issue to prevent similar occurrences. We will provide updates on our findings and any necessary preventive measures. Thank you for your patience and understanding during this incident.
- resolved Apr 25, 2024, 11:06 AM UTC
The issue with the Uniqkey extension on our legacy platform has been fully resolved. Our investigation determined that the root cause was faulty storage operations. The storage system was not optimizing operations correctly, resulting in an outage for some of our services. This caused the Uniqkey extension to malfunction and prevent it from operating properly. We have addressed the underlying issue, and the system is now operating as intended. Thank you again for your patience and understanding during this incident.