LILT Website Down
Timeline · 2 updates
- monitoring Jun 17, 2026, 04:47 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 17, 2026, 09:01 PM UTC
This incident has been resolved.
Lilt had 41 outages in the last 2 years totaling 102h 43m of downtime — averaging 1.7 incidents per month.
There were 41 Lilt outages since September 20, 2024 totaling 102h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We’ve identified this as a regional and browser-specific issue. We are reviewing the impact.
This incident has been resolved.
We are actively investigating this issue. This impacts both Instant Translate and pre-translation.
The issue has been identified and we've pushed a fix; we're monitoring to ensure its efficacy.
The issue with batch translation has been resolved.
AI Review is currently experiencing high load, which may result in slower response times. Our team is actively working to restore normal performance.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
Job search has been restored, but projects with spaces in their names are still impacted and not appearing in the search results. We’re working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of an ongoing issue with loading of segments in LILT. We are working on resolving this issue.
This incident has been resolved
Documents are all failing to open after a recent upgrade, a rollback is occurring to resolve the immediate issue.
Documents are now opening normally.
This incident has been resolved.
We are currently investigating this issue.
The resolution is live in production. We are now actively monitoring the system to confirm stability.
We are actively backfilling project stats (word counts, etc.) for all affected jobs. Please expect minor processing delays for any newly submitted jobs during this period.
This incident has been fixed.
API calls to /translate and batch translation within LILT is experiencing performance degradations. CAT editor translation continue to work normally.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The cause of the outage has been identified and service has been restored.
We are currently experiencing downtime with our SSO login flow due to an outage from our SSO provider.
We are waiting for an update from our SSO provider.
This incident has been resolved.
Some LILT users are experiencing degraded performance broadly on LILT.com. We are investigating the root cause.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Due to heavier than normal workloads, and limited GPU availability, Instant Translate API performance has been temporarily degraded. We are working on a solution and will notify once normal operation of this API is restored.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Lilt is currently experiencing some issues with the following services due to an ongoing ClickHouse Cloud Incident: - LILT Analytics - AI Review - Revision Reports The majority of the LILT Platform is usable but we recommend not advancing workflows during this time. Should you have any questions, you can email us at [email protected] or open a support ticket with us. A link to their incident can be found here: https://statuspage.incident.io/clickhousecloud/incidents/01K45E88VAD9EF4A283Z1E72XG This incident from our Third Party Provider is affecting the LILT platform. Thank you for your patience in this matter.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
Job creation in LILT is restricted to fewer languages than usual. We are investigating the cause of the issue.
This incident has been resolved.
We are aware of several large latency spikes on APIs used by the CAT editor. We are investigating, and will update with more information once we have it.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers using the XTM <> LILT integration will not see jobs delivered. We are currently investigating the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
GCP, our cloud services provider is currently completely unavailable. This is impacting all LILT Platform operations, resulting in a general service unavailability. We will notify you once GCP service has been restored.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
Google Cloud Platform outage is still ongoing. As a result, LILT Platform is experiencing a general service unavailability. Incident status updates from Google are available at https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW We will notify you once Google Cloud Platform service has been restored, as this should resolve all issues with LILT Platform services.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigating the issue. Login is still available via direct link at https://lilt.com/signin
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.