Uniqkey incident
Server Communication Failure in Extension Displaying "No Response from Server" Error
Uniqkey experienced a major incident on September 18, 2024 affecting Extension API and Mobile API, lasting 1h 25m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Sep 18, 2024, 08:17 AM UTC
Incident Details: We are currently investigating an issue reported by multiple users where the extension is displaying a "No response from server" error. This issue has affected users across all browsers, preventing successful communication between the extension and the server. Current Findings: - The issue has been identified and resolved. If you are still experiencing issues, please try restarting the extension and/or your browser or clearing your browser cache. Next Steps: - Monitoring of the system will continue to ensure stability and prevent recurrence. Timeframe: - Start Time: 18th September 2024, 09:55 UTC+2 Contact Information: If you have any questions or need further assistance, please contact our support team at [email protected]. We're here to help and provide any necessary information or support.
- monitoring Sep 18, 2024, 08:29 AM UTC
As of 18th September 2024 10:06 UTC+2, our servers are reporting normal operations on the backend. If you're still experiencing issues, please try closing all browser tabs and restarting your browser to force the extension to refresh the connection. Contact Information: If you have any questions or need further assistance, please contact our support team at [email protected].
- resolved Sep 18, 2024, 09:42 AM UTC
Incident Closure: We are pleased to inform you that the incident regarding the "No response from server" error in the extension has been fully resolved. Incident Closure: - The issue was caused by the recent upgrade our Web Application Firewall (WAF), which unexpectedly consumed more resources than intended and impacted several of our services, including the extension's communication with the server. - Although the WAF had been in place for several days without issues, this particular problem only surfaced recently due to a gradual increase in resource usage. - To resolve the issue, we adjusted system limits and added additional CPU resources to ensure stable performance moving forward. - The backend is now operating normally, and all services have been restored. Users should no longer experience any issues after restarting their browser or clearing the extension cache. - The incident is now officially closed. Timeframe: - Start Time: 18/09/2024, 09:55 UTC+2 - Resolution Time: 18/09/2024, 10:06 UTC+2 Contact Us: If you have any questions or need further assistance, please contact our support team at [email protected].