Is there an Lokalise outage?
Lokalise status: Systems Active
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Lokalise and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Lokalise and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Lokalise.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Lokalise API | Active |
| Lokalise App | Active |
| Lokalise.com | Active |
| Lokalise OTA | Active |
View the latest incidents for Lokalise and check for official updates:
Description: 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.
Status: Postmortem
Impact: Critical | Started At: Jan. 30, 2024, 9:06 a.m.
Description: 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.
Status: Postmortem
Impact: Critical | Started At: Jan. 30, 2024, 1:38 a.m.
Description: 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.
Status: Postmortem
Impact: Critical | Started At: Jan. 30, 2024, 1:33 a.m.
Description: 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.
Status: Resolved
Impact: None | Started At: July 17, 2023, 1:51 p.m.
Description: The incident has been resolved. We apologise for any inconvenience. Please, in case you have some failed background jobs, retry them.
Status: Resolved
Impact: Minor | Started At: June 22, 2023, 5:44 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
