Time: Aug. 22, 2024, 6:11 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: Aug. 22, 2024, 3:39 a.m.

Status: Investigating

Update: The Lokalise main application (https://app.lokalise.com) is experiencing performance issues related to the project functionalities. Our team is investigating the root cause of these issues and working diligently to resolve them immediately.

Time: July 4, 2024, 4:08 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 4, 2024, 1:50 p.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results.

Time: July 4, 2024, 11:22 a.m.

Status: Identified

Update: The issue has been identified and a fix is being implemented.

Time: July 4, 2024, 10:07 a.m.

Status: Investigating

Update: Lokalise main application (https://app.lokalise.com) is experiencing issues related to search and filter functionalities in the user interface. We have found the cause and are currently working on fixing the issue.

Time: June 13, 2024, 6:27 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: June 13, 2024, 3:49 a.m.

Status: Investigating

Update: The Lokalise platform (https://app.lokalise.com/) is experiencing performance issues related to the project functionalities. Our team is investigating the root cause of these issues and working diligently to resolve them immediately.

Time: April 1, 2024, 3:15 p.m.

Status: Resolved

Update: Lokalise Github, GitLab and Bitbucket are fully operational.

Time: April 1, 2024, 3:13 p.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results and performance of the the Lokalise Github, GitLab and Bitbucket apps.

Time: April 1, 2024, 3:11 p.m.

Status: Identified

Update: There is an issue affecting the performance of the Lokalise Github, GitLab and Bitbucket apps. We are currently working on identifying the root cause and fixing it. We will provide more information as soon as possible.

Time: Feb. 12, 2024, 5:09 p.m.

Status: Postmortem

Update: An unexpected malfunction occurred in one of the services provided by Lokalise at approximately 2:00 UTC. This disruption resulted from a failure of one of the hardware units that host our clusters. This failure led to performance degradation \(perceived both via the UI and/or our REST API\) and induced a delay or lack of responsiveness in functionality such as comments, file uploads, AI LQA, style guide, QA, translation memory, translation orders, machine translation, auto-close actions for tasks, notifications and events, git integrations, and screenshots. In addition to these, other non-user-facing services and processes were also affected, which may have led end-users to experience suboptimal performance levels. By approximately 8:00 UTC, we identified the source of the issue and embarked on the necessary steps to ensure all Lokalise services were reinstated to optimal performance levels. By 10:30 UTC, all functionalities had been fully restored. We sincerely apologize for any inconvenience our customers may have experienced during this incident. We want to assure everyone that we are treating this occurrence with the utmost seriousness and are dedicated to enhancing our distributed message-queuing services to prevent similar occurrences in the future. Your patience and understanding during this time are greatly appreciated. We pledge our commitment to tirelessly work towards improving Lokalise's performance and reliability.

Time: Jan. 30, 2024, 9:18 a.m.

Status: Resolved

Update: This incident has been resolved.

Time: Jan. 30, 2024, 9:17 a.m.

Status: Investigating

Update: There is an issue accessing Lokalise's main application. We are currently working on identifying the root cause and will provide more information as soon as possible.