Is Lokalise Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

We have identified the issue, and new async exports are now processing fine. We are implementing a fix to allow stuck processes to finish.

We are currently investigating this issue.

Async export processes that have been triggered between 07:15 and 08:15 UTC time today got stuck and didn’t complete. We will share more details in the postmortem message.

This incident has been resolved.

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

Lokalise application is experiencing issues with processing search, filtering and statistics in the UI. We are currently investigating this issue.

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 [hello@lokalise.com](mailto:hello@lokalise.com).

This incident has been resolved.

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

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

We are currently experiencing issues with UI import and bulk actions. We are investigating the issue.

This incident has been resolved.

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

Lokalise is experiencing issues with AI translation tasks and MT orders processing. We are currently investigating this issue.

On February 19, 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 morning. Our team promptly investigated and mitigated the problem, quickly restoring full service. **Impact** * 08:54 UTC to 09:23 UTC: Customers experienced slower performance. **What we are doing to prevent this in the future** We recognize the importance of this event, and we are taking 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. 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 [hello@lokalise.com](mailto:hello@lokalise.com).

This incident has been resolved.

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

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

We have restored the functionality to unblock customers. We are continuing to investigate the root cause.

All functionality that is relying on background processes is affected. We are continuing to investigate this issue.

Some actions like file import, bulk actions are not being processed. We are investigating this issue.

On February 10, 2025, our service experienced a 16-minute outage followed by 39 minutes of degraded functionality due to an issue with a system configuration. **What happened?** While improving our disaster recovery process, a misconfiguration in the system was introduced unintentionally. Initially, this did not cause issues, but when we attempted to roll back the change, it led to unexpected complications. As a result, our service platform became temporarily unavailable, requiring the reconstruction of certain system components to restore full functionality. **Impact** * **12:30 – 12:46 UTC**: Service outage. * **12:46 – 13:25 UTC**: Service degradation—APP and API were operational. Some services remained unavailable \(OTA, Workflows, Connectors, Review Center\). **What we are doing to prevent this in the future** We recognize the importance of this event, and we have taken steps to ensure it does not happen again. Our key actions include: * Improving validation and monitoring processes to identify configuration issues before deployment. * Enhancing our tools and automations for faster services restoration. * Implementing blue-green deployment techniques, or equivalent, for seamless system upgrades. We sincerely apologize for the disruption this caused and appreciate your patience as we work to make our systems more resilient. If you have any questions, please reach out to [support@lokalise.com](mailto:support@lokalise.com).

This incident has been resolved.

We have applied the fix and monitoring for issues.

We are investigating the slowness of application and Lokalise OTA service unavailable.

We are investigating the slowness of application and Lokalise OTA service unavailable.

We are continuing to monitor for any further issues.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

On February 5, 2025, we experienced a major service degradation affecting our Import functionality. The incident began at 11:00 UTC and during this time, customers were unable to perform imports in the UI or utilize Git integrations, which may have disrupted their workflows. Services have been fully restored by 13:26 UTC. The outage was caused by a misconfiguration during our migration to a new infrastructure system. To resolve the issue, our team rolled back to the previous system. In response to this incident, we are implementing several measures to prevent similar occurrences in the future: * We will enhance our deployment health checks to cover a previously missing set of dependencies, so that we can catch misconfiguration before newly deployed instances start to be used. * Additional monitoring and alerting systems will be established to quickly identify and address issues as they arise. * We are increasing coverage of our automated tests to ensure all the critical functionality is covered. We sincerely apologize for the inconvenience this incident caused to our customers. We understand how crucial these services are for your operations, and we appreciate your patience as we work to improve our systems and ensure reliable service in the future. Your trust is important to us, and we are committed to enhancing our processes to prevent such occurrences. Thank you for your understanding.

This incident has been resolved.

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

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

We are seeing issues with import and export functionality of the Lokalise app. We are investigating the issue.

On December 19, 2024, we experienced a significant service degradation affecting several content integrations, including Contentful, Storyblok, Zendesk Guide, HubSpot, and ContentStack. The incident began at 22:32 UTC and lasted approximately 9 hours, primarily impacting our customers in the US and APAC regions during their business hours. The issue was first reported by one of our customers. The incident was triggered by a late release that introduced a misconfiguration on our production environment. Upon receiving the customer complaint at 01:00 UTC on December 20, our team promptly initiated a rollback of the faulty release. By 08:15 UTC, we successfully restored services to a stable state. If you had scheduled imports or exports during the affected hours, it is likely that they failed due to this incident. We understand how important these operations are for your business, and we apologize for any disruption this may have caused. To prevent similar incidents in the future, we are taking the following steps: * We will ensure consistent configurations across all environments to catch potential issues early. * We are enhancing our testing protocols to include scenarios that replicate customer-reported issues. * We will reassess our release schedule, particularly regarding significant changes, to avoid late releases before critical periods. We sincerely apologize for the inconvenience this incident caused to our customers. We appreciate your understanding and patience as we work to improve our systems and ensure reliable service in the future. Your trust is important to us, and we are committed to enhancing our processes to prevent such occurrences.

Several content integrations were affected including Contentful, Storyblok, Zendesk Guide, HubSpot, and ContentStack.

This incident has been resolved.

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.

This incident has been resolved.

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

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

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.

This incident has been resolved.

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.

Lokalise Github, GitLab and Bitbucket are fully operational.

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

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.

This incident has been resolved.

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

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.

This incident has been resolved.

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

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.

This incident has been resolved.

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.

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.

This incident has been resolved.

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

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.

This incident has been resolved.

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.

The incident has been resolved. However, we're continuing to look into restoring sign up feature and planning to share more insights in the follow-up postmortem.

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

Log-in via Microsoft accounts is restored, however signing up to new Lokalise teams via this authentication method is not available. Our team continues to look into restoring full functionality of this feature.

Log-in via Microsoft accounts is temporarily unavailable due to necessary system updates. This doesn't affect API access. You can continue using Lokalise as usual, but please avoid logging out while our team is actively working to restore the feature. Thank you for your patience and understanding.

The incident has been resolved. We apologise for any inconvenience. Please, in case you have some failed background jobs, retry them.

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

We are continuing to work on a fix for this issue.

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

Lokalise background operations are degraded. We are investigating the functionalities affected.

This incident has been resolved.

There is an issue accessing Lokalise's OTA v3 service. We are currently working on identifying the root cause and will provide more information as soon as possible.

This incident has been resolved.

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

This incident has been resolved.

There is an issue accessing Lokalise's OTA v3 service. We are currently working on identifying the root cause and will provide more information as soon as possible.

This incident has been resolved.

There is an issue accessing Lokalise's OTA v3 service. We are currently working on identifying the root cause and will provide more information as soon as possible.

To better handle the growing amount of data and users in Lokalise, we constantly work on scaling resources for the application. After a routine operational change that was previously executed multiple times and tested on staging environment successfully, Elasticsearch cluster that powers many Lokalise features has become suddenly overloaded. Once more users have started coming online the service began struggling with the load leading to increased latency and general slowness of Lokalise application. We have turned off filters, search, and statistics to make application performant again while in limited mode, and continued to work on resolving the issue. The source of the issue has been established quickly, however full performance restoration took more than an hour before we could re-enable all functionality. It took this long because the Elasticsearch index that had to be relocated was very large. The root cause of the incident was an incorrect estimation of the resources required for scaling the backend service. This was unexpected as it turned out that metrics we have in place did not reveal the full extent of the actual service’s load. We apologize for the inconvenience and frustration caused by the downtime experienced by our customers. Our team takes this incident seriously and is committed to taking all necessary measures to prevent similar incidents from occurring in the future. We appreciate your patience and understanding and will continue to work diligently to improve our system’s performance and reliability for you.

This incident has been resolved.

A fix has been implemented and the search, filtering, and statistics functionality are restored. We are monitoring the results.

The issue has been identified, and a fix is being implemented. The app is accessible now, however we disabled search, filtering, and statistics functionality to work on the root cause.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

The Lokalise platform (https://app.lokalise.com/) is experiencing performance issues related to loading times, navigation speed within projects, and search functionality. API is also affected. Our team is investigating the root cause of these issues and working diligently to resolve them immediately.

Landing page was unavailable for 2.5 hours

This incident has been resolved.

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

The incident has been resolved and orders are processing normally. Please feel free to place your orders. We will follow up with affected customers to clarify on further actions. We apologize for the inconvenience.

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

Lokalise is experiencing temporary issues with order processing. Please hold on before placing your order until further notice. We are looking into fixing it ASAP.

This incident has been resolved.

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

We experienced an incident resulting in some customers being unable to use the Lokalise App. The root cause of the incident was identified as an issue with the new release process, which did not properly publish some assets to the CDN. This resulted in errors in the App when a browser attempted to load the missing assets. To prevent similar incidents in the future, we are implementing additional checks and tests to catch issues with asset publishing during the release process. Also, adding monitoring for CDN asset availability to our monitoring system to quickly detect and alert on any potential issues. We apologize for any inconvenience this incident may have caused. We are taking steps to prevent similar incidents from occurring in the future.

This incident has been resolved.

We are experiencing temporary performance limitation with filtering and search functionalities. Our team is working on identifying the underlying cause.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We have restored the app's functionality, while still looking into identifying the cause for the incident.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

Payments for translations orders and Lokalise subscriptions were not processed properly. The issue has been found and resolved.

This incident has been resolved.

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

This incident has been resolved.

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

This incident has been resolved.

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

This incident has been resolved.

We are currently investigating this issue.

Some customers were receiving an unexpected amount of email copies from Lokalise. We have identified the cause, and resolved the issue. We are sorry for the inconvenience.

This incident has been resolved. If you still cannot access Lokalise application, please try clearing your browser's cache.

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

We are currently investigating this issue.

This incident has been resolved. If you still cannot access Lokalise application, please try clearing your browser's cache.

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.

Our team has identified high RAM usage by snapshot creation process. It was impacting bulk actions successful completion. The issue was already known to the Engineering team who were developing a long-term solution. As a short-term fix we decided to move forward with a workaround. On July 22nd, 2022 our team released an option for users to deactivate the snapshot creation for bulk actions. That helped to avoid the limitation and unblock few affected customers. We then prioritized the long-term solution to reduce RAM consumption during snapshot creation. After doing a proper testing it was released on July 14th, 2022. Further performance monitoring showed the solution has helped to restore bulk actions and snapshot functionality in full. Please note that now snapshot creation takes more time for bigger projects with millions of entities like keys, translation history, etc. We had to find a better balance for RAM vs. time usage to make snapshot creation more stable and scalable.

Earlier today we experienced a MySQL database connection issue that made the application and API inaccessible. It was caused by data migration in one of the releases. We successfully rolled back and restored full functionality. We appreciate your understanding and are sorry for the inconvenience.

This incident has been resolved.

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

This incident has been resolved. Thank you for your understanding, and we apologize for the inconvenience.

The issue has been resolved, but we'll continue monitoring.

We have identified the root cause. There is a network incident in one of our underlying service providers. We have restored our service, and we will continue monitoring.

The Lokalise platform (https://app.lokalise.com/) is experiencing performance degradation. Our team is working on identifying the underlying cause and will provide more information as soon as possible.

This incident has been resolved.

The Lokalise platform (https://app.lokalise.com/) is experiencing performance degradation. We are currently working on identifying the root cause and will provide more information as soon as possible.

We have identified the cause and resolved the issue. Thank you for your patience, and we are sorry for the inconvenience.

We are experiencing temporary limitation with import functionality. Our team is working on identifying the underlying cause. We will update in you in the next 30 minutes.

This incident has been resolved.

We have identified the cause for the issue, and looking further into resolving it.

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

This incident has been resolved.

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