Lokalise incident
Lokalise main application degraded performance
Lokalise experienced a major incident on February 27, 2025 affecting Lokalise App, lasting 1d 21h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 28, 2025, 05:23 PM UTC
We are currently experiencing issues with UI import and bulk actions. We are investigating the issue.
- identified Feb 28, 2025, 06:01 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 28, 2025, 06:12 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 28, 2025, 06:40 PM UTC
This incident has been resolved.
- postmortem Mar 11, 2025, 11:07 AM UTC
Between February 27 and March 1, 2025, our service experienced performance degradation in background tasks that impacted essential processes including file imports, synchronization with content integrations, and some bulk actions. **What happened?** A faulty release unintentionally caused our background tasks to stop working as expected. Although the issue did not appear immediately, it became noticeable the next evening. Our team promptly identified the problem, initiated an investigation, and implemented a corrective patch, ensuring full service restoration. **Impact** * **February 27th, 2025, 20:00 UTC to March 1, 2025, 12:02 UTC**: Customers experienced slower performance. * **March 1, 2025, 14:30 UTC**: Corrective patch deployed. **What we are doing to prevent this in the future** We recognize the importance of this event, and are taking further steps to ensure it does not happen again. Our key actions include: * Additional monitoring of background tasks to quickly spot issues. * Exploring options for our system to recover automatically from minor errors. * Enhancing our test coverage to help identify potential issues earlier in the release process. We sincerely apologize for the inconvenience this incident caused. Thank you for your patience and understanding as we continue to improve Lokalise’s resilience and reliability. If you have any questions or require further assistance, please contact [[email protected]](mailto:[email protected]).