Litium Outage History

Started Sep 25, 2025, 11:55 AM UTC· resolved Sep 26, 2025, 08:00 AM UTC

1. investigating Sep 25, 2025, 11:55 AM UTC

   We are currently experiencing intermittent disruptions in Litium Serverless Cloud. Some workloads may be temporarily impacted, causing degraded performance or occasional errors. Our engineering team is investigating and working to restore full stability as quickly as possible. Further updates will follow as we learn more.

2. identified Sep 25, 2025, 01:05 PM UTC

   We have identified the root cause of the intermittent disruptions in Litium Serverless Cloud. Our team is currently implementing a fix, and workloads may still be affected until the solution is fully deployed. We will provide another update once the fix has been rolled out and we have verified that the platform is stable.

3. identified Sep 25, 2025, 02:02 PM UTC

   We are continuing to work on implementing the solution for the identified issue affecting Litium Serverless Cloud. Some workloads may still experience intermittent impact while we complete the deployment and monitoring of the fix. We will share another update once the solution is fully in place and stability has been confirmed.

4. identified Sep 25, 2025, 02:58 PM UTC

   Our team is still working on implementing the solution for the issue impacting Litium Serverless Cloud. Workloads may continue to be intermittently affected until the deployment is fully completed. We will provide another update as soon as we have more progress to share.

5. monitoring Sep 25, 2025, 03:48 PM UTC

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

6. resolved Sep 26, 2025, 08:00 AM UTC

   At 13:23 CET, our monitoring systems detected a brief service interruption where some customer sites reported increased response time. While services appeared to recover quickly, our engineering team initiated a thorough investigation to ensure platform stability. During the investigation, we identified irregularities in the orchestration layer and control components, which required corrective actions. These actions included restarting affected nodes and renewing internal certificates to restore full functionality. While restarts was made interruptions and connection issues was reported. By 17:30 CET, all systems were confirmed operational, and additional validation was performed to ensure service reliability for all customers. We sincerely apologize for the inconvenience this has caused. Further actions: The underlying cause of this incident is already mitigated in our new Compliant Cloud. The migration is started and will continue as planed.

Read the full incident report →

Started Sep 17, 2025, 05:00 AM UTC· resolved Sep 17, 2025, 05:00 AM UTC

1. resolved Sep 17, 2025, 01:20 PM UTC

   Incident Summary This morning, a small number of customers experienced a short period of downtime for their Litium applications hosted in Serverless Cloud. Timeline - 15 September 2025, 15:20 – An incorrect configuration was introduced during a routine update. - 17 September 2025, morning (UTC) - Automatic scaling moved some customers to new underlaying infrastructure. This caused a limited set of applications to restart and become unavailable. - 17 September 2025, 10.00-11:45 - Services were automatically restored after configuration was corrected. Only environments that had not been restarted since 11 September 2025 were affected. Impact The downtime affected a small portion of customers. Services were automatically restored after configuration was corrected. Next Steps We have adjusted our update process to ensure that similar configuration issues do not cause interruptions in the future.

Read the full incident report →

Started Sep 15, 2025, 10:06 AM UTC· resolved Sep 15, 2025, 11:17 AM UTC

1. investigating Sep 15, 2025, 10:06 AM UTC

   We are currently investigating reports of failed logins with Litium Account and are working to identify the cause. This issue affects login attempts to Litium Insights and the Serverless CLI. Further updates will follow.

2. resolved Sep 15, 2025, 11:17 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2025, 08:25 AM UTC· resolved Aug 15, 2025, 07:54 AM UTC

1. investigating Aug 13, 2025, 08:25 AM UTC

   We are currently experiencing issues affecting some requests in our serverless cloud environment. Our team is actively investigating the cause and working to resolve the problem. We will provide an update as soon as more information is available.

2. monitoring Aug 13, 2025, 05:13 PM UTC

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

3. resolved Aug 15, 2025, 07:54 AM UTC

   This incident has been resolved.

4. postmortem Aug 15, 2025, 07:55 AM UTC

   **Incident Summary – August 12–15, 2025** On August 12 at approximately 20:00 CEST, an infrastructure issue temporarily impacted a small number of customers. Of those affected, only a small fraction of requests experienced request timeouts \(where the system did not respond within the expected time\). No widespread service disruption occurred. Following the initial recovery, some customers experienced intermittent request timeouts on August 13. Targeted restarts were performed during the day, including two specific resources showing abnormal behavior, after which stability improved and error rates returned to normal. The incident remains open in monitoring until the morning of August 15 to confirm sustained normal operation before closure. We appreciate your patience and understanding. **Timeline** * **Aug 12, ~20:00** – An unexpected hardware event caused certain services to restart, leading to partial unavailability for some components. Services were automatically restarted and restored. * **Aug 13, morning** – Some customers experienced slightly increased response times and a small number of intermittent request timeouts related to the previous evening’s event. * **Aug 13, 11:00** – All services returned to normal redundancy and performance, though sporadic timeouts persisted for a subset of customers. * **Aug 13, 16:30–18:30** – Additional service restarts were performed to eliminate remaining issues. At this point, all systems were functioning as expected. * **Aug 14, 16:45–17:30** – Additional preventive maintenance was performed on multiple resources to help ensure continued stability. * **Aug 14 evening** – Services remain stable and are kept in monitoring to confirm sustained normal operation. **Impact** * Affected only a small number of customers. * For those affected, a small fraction of requests resulted in timeouts. **Resolution** The service team monitored and performed targeted restarts of affected components. Error rates returned to normal on the evening of August 13. The incident remained open in monitoring until the morning of August 15 to ensure continued stability before closure. **Next steps** We have updated our operational routines, enhanced monitoring, and refined recovery procedures to further reduce the impact of similar incidents occurring in the future.

Read the full incident report →

Started Aug 12, 2025, 09:39 PM UTC· resolved Aug 12, 2025, 10:05 PM UTC

1. investigating Aug 12, 2025, 09:39 PM UTC

   We are currently investigating this issue.

2. monitoring Aug 12, 2025, 10:03 PM UTC

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

3. resolved Aug 12, 2025, 10:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2025, 10:58 AM UTC· resolved Mar 12, 2025, 10:47 AM UTC

1. investigating Mar 11, 2025, 10:58 AM UTC

   We have detected issues with the App Services for LCC serverless. Investigation is ongoing. More information will be provided shortly.

2. identified Mar 11, 2025, 11:48 AM UTC

   We have identified an underlaying cause of the issue and working together with the supplier to mitigate.

3. identified Mar 11, 2025, 12:20 PM UTC

   We are currently experiencing issues due to underlying hardware problems at our supplier. Our team is actively collaborating with them to resolve the issue as quickly as possible. We appreciate your patience and understanding during this time.

4. identified Mar 11, 2025, 01:04 PM UTC

   Our supplier's technical team is currently on-site at the datacenter, working to replace and fix the faulty hardware causing the issues. We are closely monitoring the situation and will provide further updates as soon as possible. Thank you for your continued patience and understanding.

5. identified Mar 11, 2025, 02:32 PM UTC

   Some systems are already back online, and our team continue to work diligently to restore normal operations on the remainder.

6. identified Mar 11, 2025, 04:19 PM UTC

   Additional systems are now online. The team continue to work on restoring the rest.

7. identified Mar 11, 2025, 05:37 PM UTC

   We are continuing our efforts to restore all systems to full operational status. Our team is exploring multiple approaches to ensure a swift resolution. We appreciate your patience and will keep you informed of any further developments.

8. identified Mar 11, 2025, 06:55 PM UTC

   We are pleased to inform you that another key service has been restored, and most customers should now be operational. However, there are still some services that we are actively working on. Our team remains dedicated to resolving all issues as quickly as possible. Thank you for your continued patience and support.

9. identified Mar 11, 2025, 08:24 PM UTC

   Most services are now up and running. We are still working on resolving issues with our Litium Search service. Our team is dedicated to restoring full functionality as quickly as possible. Thank you for your patience and understanding.

10. monitoring Mar 11, 2025, 10:33 PM UTC

    All services are now up and running. We will continue to monitor the situation closely until tomorrow morning to ensure stability. Following this, we will initiate our incident review process to thoroughly analyze the cause and impact of the disruption. Thank you for your patience and understanding.

11. resolved Mar 12, 2025, 10:47 AM UTC

    We have monitored the situation closely overnight and can confirm that all services have remained functioning normally throughout the night. If anyone continues to experience issues, please contact support. The incident was caused by underlying hardware problems at our supplier and affected some of our cloud services. We will continue our analysis of the incident, create a detailed incident report, and take necessary measures to prevent this from happening again. We sincerely apologize for the inconvenience caused by the incident.

Read the full incident report →

Started Jan 29, 2025, 08:07 AM UTC· resolved Jan 29, 2025, 03:06 PM UTC

1. investigating Jan 29, 2025, 08:07 AM UTC

   We are currently experiencing issues with the installation of apps and deployments in our serverless cloud environment. Please note that this issue does not affect the uptime or performance of already installed or deployed workloads. Our team is actively investigating the situation, and we will provide an update as soon as more information becomes available. Thank you for your patience and understanding.

2. identified Jan 29, 2025, 09:43 AM UTC

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

3. monitoring Jan 29, 2025, 10:34 AM UTC

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

4. resolved Jan 29, 2025, 03:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 24, 2025, 01:26 PM UTC· resolved Jan 24, 2025, 02:26 PM UTC

1. identified Jan 24, 2025, 01:26 PM UTC

   We are currently experiencing issues with one of our Cloud API, which may affect users' ability to deploy changes to solutions in Serverless Cloud. Our team is working diligently to resolve the problem as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. We will provide updates as soon as we have more information. Thank you for your understanding.

2. resolved Jan 24, 2025, 02:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 13, 2025, 02:00 AM UTC· resolved Jan 13, 2025, 02:00 AM UTC

1. resolved Jan 13, 2025, 08:46 AM UTC

   Serverless service experienced an issue that caused request timeouts for our customers. During this period, customers may have encountered delays or failures when attempting to access services. The issue was resolved by restarting one of our controller nodes. We are currently investigating the root cause of the problem to prevent future occurrences. We apologize for the inconvenience this have caused and appreciate your patience as we work to ensure the reliability of our services.

Read the full incident report →

Started Nov 25, 2024, 11:06 AM UTC· resolved Nov 26, 2024, 05:34 AM UTC

1. investigating Nov 25, 2024, 11:06 AM UTC

   All incoming emails are delayed due to outage in external mail traffic. For urgent cases please use the support phone : 036-210 33 30

2. resolved Nov 26, 2024, 05:34 AM UTC

   Support emails are now working.

Read the full incident report →