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

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.

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.

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.

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.

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.

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

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

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.

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.

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

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

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 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.

This incident has been resolved.

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.

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.

We have been monitoring overnight, and all services are now normal. The issue was related to an unexpected problem with the control plane in our main application cluster. We will continue to investigate the root cause to ensure this does not happen again. We apologize for the inconvenience this has caused and thank you for your patience during this incident.

The services are fully operational and back to a normal state. We will continue to monitor the situation and investigate the root cause of the incident. If no further issues arise, the next update will be provided tomorrow morning. Thank you for your patience.

Sites are up and running since 19:46 but might still experience some intermittent issues. We are currently working on stabilizing the services. We will provide an update as soon as more information is available. Thank you for your patience.

We keep working on resolving the issue affecting sites in our serverless cloud. We will provide an update as soon as more information is available. Thank you for your patience.

We have identified the cause of the issue affecting some sites in our serverless cloud environment and are now working on implementing a solution. We will provide further updates as soon as we have more information. Thank you for your patience and understanding.

We are still actively working to resolve the issue affecting some sites in our serverless cloud environment. Our team is making progress, and we will share further updates as soon as possible. Thank you for your continued patience and understanding.

We are currently experiencing issues affecting some sites 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. Thank you for your patience.

Support emails are now working.

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

This incident has been resolved.

We have identified and resolved the issue affecting one of our database cluster. All services are now back to normal. During the incident, some customers experienced intermittent long connection times and occasional connection timeouts. We will continue to monitor the situation closely to ensure stability. Additionally, we are investigating the root cause and will implement measures to prevent a recurrence. Thank you for your patience and understanding.

We are experiencing an issue with one of our database cluster. We are investigating this issue.

We encountered an issue where the job status information returned to users via the CLI client was outdated due to caching. While all jobs were executed correctly, the status information provided did not reflect the most recent changes. We apologize for the inconvenience this have caused and appreciate your understanding and patience during the incident.

This incident has been resolved.

All services are now fully operational. Note that it may take some extra time for all jobs to process since jobs has queued up.

Litium Search is now fully operational. We continuing to monitor for any further issues.

Since the fix has been rolled out majority of workload is working as normal, but some customers may still affected, we are continuing to monitor and resolving remaining issues.

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

We have identified an issue affecting Litium Search. Our team is actively working on a solution and we are making progress toward implementing a fix. We will provide further updates as soon as possible. We appreciate your patience and understanding during this time.

We are continuing to investigate this issue.

Issues with some sites in Serverless Cloud reported. We are currently investigating this issue.

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

Some jobs in Serverless Cloud CLI is stuck in "pending" status. We are currently investigating this issue.

All systems are now online and nominal. We will continue to investigate to determine how to avoid similar problems in the future.

We are continuing to monitor for any further issues.

We experienced an issue with our database service that prevented read and write operations. Our team has implemented a solution and we are currently monitoring the situation to ensure stability. We apologize for the inconvenience this have caused and appreciate your patience.

We have implemented a fix for the issue and all databases is now operational.

We are currently investigating this issue.

Phones are now operational.

Support phones for SLA customers are currently unreachable. All urgent issues must be reported by email until further notice. Please use support@litium.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 pleased to inform you that the incident has been resolved. The root cause was identified as a major hardware failure. The issue was resolved by rerouting the traffic to get the services online. We are now working closely with our supplier to gather all details and determine how this occurred and how it can be prevented in the future. Additionally, we are preparing a post-mortem report to thoroughly analyze the incident and improve our processes. Thank you for your patience and understanding throughout this process.

All services remain operational. We are now working closely with our supplier to identify the root cause of the incident, which has been determined to be network-related within the data center. We will continue to monitor the situation to ensure ongoing stability. Thank you for your patience and understanding.

We are pleased to inform you that all services are now operational. Our team will continue to monitor the situation closely to ensure ongoing stability. We appreciate your patience and understanding throughout this process.

Our team continues to work diligently on resolving the incident affecting all services. We understand the impact this has on your operations and sincerely apologize for the inconvenience. Your patience is greatly appreciated, and we will provide further updates as soon as we have more information.

Our team is still actively working on resolving the incident affecting all services. We understand the inconvenience this may cause and appreciate your continued patience. We will keep you informed with further updates as soon as possible.

We are still investigating the incident affecting all services. Our team is working diligently to resolve the issue as quickly as possible. We appreciate your patience and will provide further updates as soon as we have more information.

We are currently investigating this issue.

Litium insights is now online. Reload or refresh the page to see the latest logs.

We are currently having issues with collecting logs from several systems. The underlaying systems are performing as normal but Litium Insights is not presenting latest log data. Investigation is ongoing.

The incident has been fully resolved. Our team, in collaboration with our suppliers, is currently conducting a thorough investigation to determine the root cause of the incident. We will share a post-mortem report once we have gathered more information. We thank you for your patience and apologize for the inconvenience caused. Your understanding and support are greatly appreciated.

The issue has been identified as a network issue affecting communication to some of our shared services. The issue has been resolved and normal service has been restored. We are now in a monitoring phase to ensure stability. Please be aware that while all services should be fully accessible again, you may experience some reduced performance as the system returns to optimal functioning. We appreciate your patience and understanding during this time. Should you encounter any further issues, please do not hesitate to contact our support team.

We're experiencing network related issues and our Infrastructure-team investigating it.

This incident has been resolved.

The service is now operational, but with degraded performance. We will keep this incident open until tomorrow morning. We apologize for any inconvenience this has caused!

We are currently experiencing an interruption with Litium Account service. This issue is due to a problem at Microsoft Azure B2C service. We apologize for any inconvenience this cause and appreciate your patience while this matter is being addressed. This issue affects the ability to log in to Litium Insights and Litium Serverless Cloud. Users may encounter difficulties accessing these services until the problem is resolved. This do NOT affect any customer sites running on Litium Cloud.

This incident has been resolved.

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

One of our DNS suppliers are having issues due to an external DDOS attack. Litium are not the target and our sites are working but can be hard to reach at the moment.

We are pleased to announce that the issues affecting creating new apps that require database services in Serverless Cloud have been fully resolved, and we have successfully lifted the temporary restrictions on creating new apps with database resources. We understand the inconvenience this may have caused and want to extend our deepest gratitude for your patience and understanding. As always, we are committed to providing you with the highest quality of service. Should you have any questions or need further assistance, please do not hesitate to contact our support team at support@litium.com

Our team has been relentlessly working on implementing a robust solution to the recent database service issues in Serverless Cloud. Our focus remains on taking all necessary steps to ensure the stability and reliability of our services, allowing us to lift the temporary restrictions on creating new apps with database resources as swiftly as possible. We continue to target the beginning of this week to remove these limitations. Rest assured, we are closely monitoring our progress and will keep you updated with any new developments or changes to this timeline. In the meantime, we appreciate your understanding and patience. Note - This doesn't affect the stability and reliability of existing apps.

As part of our precautionary measures, the ability to create new apps requiring a database resource remains temporarily disabled. We are making steady progress and are focused on ensuring the long-term stability and reliability of our platform. Our current estimate is to lift this restriction by the beginning of next week. We understand the impact this may have on your plans and projects, and we appreciate your patience and support as we work through these necessary steps. We are committed to keeping you informed and will provide another update as soon as more information becomes available or if we can restore full functionality sooner than anticipated. This does not affect existing and already live apps and database.

In light of the recent issues we experienced with our database services in Serverless Cloud, we have taken a precautionary step to temporarily disable the creation of new apps that require a database resource. This measure is to ensure the stability and reliability of our services as we continue to monitor the effects of the recent fix closely. We understand this may be an inconvenience for some of our users, and we want to assure you that this is a temporary measure taken with the utmost consideration for the security and performance of your applications and data. We are working diligently to lift this restriction as soon as we are confident in the stability of our services, and we will keep you updated on our progress. In the meantime, we appreciate your understanding and patience.

This incident has been resolved.

We are delighted to announce that the fix for the database issues in our Serverless Cloud has been fully implemented, and all services are now fully operational. Our team worked tirelessly to ensure a swift and effective resolution, and we will continue to closely monitor the situation to prevent any further disruptions. We want to extend our deepest gratitude for your patience and understanding. Rest assured, we are taking steps to enhance our systems to ensure the reliability and stability of our services moving forward.

We are pleased to inform you that our team has identified a solution to the database issues in our Serverless Cloud and is currently rolling out the fix. While we are optimistic about this resolution, we are closely monitoring the situation to ensure stability and effectiveness across all affected systems. It may take some time for the fix to be fully implemented and for services to return to normal for everyone. We will continue to provide updates as the situation progresses and more information becomes available. Our next update will be at 20:00, or sooner should there be significant developments. Thank you for your patience and understanding.

As we continue to address the database issues in our Serverless Cloud, we want to assure you that our team is working relentlessly to find a resolution. Although we do not have new developments to report at this moment, please know that this remains our utmost priority. We are fully committed to restoring full service as quickly and safely as possible. Your patience and understanding during this time are incredibly valuable to us. We will provide our next update at 19:00. Thank you once again for your continued patience.

Our team is still diligently working to identify and resolve the problem as swiftly as possible. Although we do not have new information to share at this moment, please rest assured that addressing this issue continues to be our highest priority. We understand the impact this may have on your operations and truly appreciate your continued patience and support during this time. We will provide another update by 18:00, or sooner if there are any developments. Thank you for your understanding.

We are actively investigating an issue affecting databases in our Serverless Cloud and are working to resolve it as quickly as possible. This is our top priority. While we do not yet have an estimated resolution time, we commit to providing updates every hour until the issue is resolved. We appreciate your patience and understanding during this time and apologize for any inconvenience this may cause.

We are continuing to monitor for any further issues.

Update - We are still experiencing issues with database creation. And working on a solution to fix this. This has caused some downtime for live databases for some customers - we are prioritizing to get this up and running as soon as possible. We are sorry for any inconvenience this may cause.

Currently not possible to create new databases. Note that this doesn't affect live sites.

We are continuing to monitor for any further issues.

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 an issue that causes jobs not to execute. E.g. creating apps, deploying artifacts etc. Note - this does not affect existing workloads or already published apps.

This incident has been resolved.

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

We're experiencing authentication issues in Serverless Cloud that affects authenticating with Service Principals and are currently looking into the issue.

The issue has been resolved. The fault was due to an error in third-party software responsible for automatically renewing certificates used for the service. We have implemented additional monitoring and alerts to prevent similar occurrences in the future. Configuration changes have also been made to the software in question. We apologize for any inconvenience caused and are committed to ensuring this does not happen again.

The issue was due to an expired certificate in the chain. We are working on gathering all the facts on how this happened and how we can ensure it does not happen again.

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

This incident has been resolved.

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

We're experiencing a disturbances on serverless cloud. Issue has been identified and a fix is being applied.

Earlier today, we encountered a brief internet outage lasting about 2.5 minutes due to a router issue. We are currently working closely with our supplier to prevent such occurrences in the future. We apologize for the inconvenience this has caused.

This incident has been resolved.

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

We are currently investigating this issue.

The maintenance on the Litium Search node has been successfully completed, and the incident is now resolved. While performing the necessary maintenance, a brief disturbance in performance may have been observed. Thank you for your patience.

We are currently experiencing an issue on one of our nodes in Litium Search. No customers are currently affected. Our team is actively working to resolve the issue, and we will be performing maintenance on the affected node. This maintenance is not expected to impact any customers. We appreciate your understanding and patience as we work to ensure the continued smooth operation of our services

The SQL server back online. The only service affected was platform documentation (docs.litium.com).

We have detected an issue with one of our SQL servers. Different services are affected. Investigation is ongoing.

Issue have been solved!

We are currently investigating this issue. If you need to contact our on-call team, use our email address support@litium.com

Some customers may have experienced worse response times against the Litium Search service. The degraded performance could be seen between 14:30 and 21:55 today. The issue was due to a configuration error associated with adding more capacity to the service.

Support phone lines are now operational.

Support phone lines are currently down. All urgent support cases must be sent by email to support@litium.com Current assessment is that phones are be back 22.00.

This incident has been resolved.

All sites are operational. We will continue to closely monitor performance for the rest of the day.

The issue has been identified and the sites are coming back online.

We are currently seeing reduced performance. Some sites may also be unreachable. Investigation is ongoing.

This incident has been resolved.

The storage server has been back online for a few minutes and we are currently monitoring the recovery of all affected customers.

One of our storage servers is offline due to a backup job that do not work as intended. We are working with our supplier on getting the server online as fast as possible.

We are currently investigating this issue.

This incident has been resolved.

The error has been identified and a solution has been applied. All affected websites are now working as expected. We will continue to monitor the fix.

We are currently investigating this issue.

Issued resolved. Forum site is working normally after contact with the service provider.

Our forum site (forum.litium.com) is having intermittent login issues. Investigation is ongoing.

This incident has been resolved.

The issue has been identified and fixed. The interreruption is related to last nights patch round.

We are currently investigating this issue.

Network has been nominal since last status update. We have identified the reason as a faulty configuration. Only a few customers within the legacy load balancer setup was affected.

The network has been restored. We will continue monitor the status until Friday morning.

We have detected isolated network issues. Investigation is ongoing.

The night between Sunday and Monday, between 00:03 and 00:34, one of our SQL clusters had problems with communication and synchronization between participating nodes. The cluster was unavailable or had degraded performance at that time. The problem was escalated and troubleshooting started. The error was resolved shortly afterwards. We are currently working with our suppliers to find the cause of the issue. We are sorry for any inconvenience this have caused. And we will work to ensure that something similar does not happen again.

No other issues have been seen due to this incident. The issue was related to DNS lookup issues on a few nodes in the cluster. This resulted in some indices being marked as unreachable. After we found and solved the cause on the affected nodes, they could be put back into operation. As soon as the nodes were operational, the affected indices became reachable again. The incident only affected a number of customers and in different ways depending on which indices were affected by the disturbance. We are sorry for any inconvenience this have caused. We are now working to ensure that something similar does not happen again.

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

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

We are continuing to investigate this issue.

We are currently investigating issues affecting performance on Litium Search.

The service is stable and the incident is now resolved.

We have now recovered all services for the affected customers. We will monitor the state and investigate on the cause of this incident.

The issue has been identified and we are working on restoring the service for the affected customers.

We have experienced degraded performance for one of our shared web servers. We saw an increased number of 500 errors starting around 12:30. After initial investigation and troubleshooting, we restarted the web service. after the restart the errors was resolved. Impact Some customers may have experienced error codes on their site. Between 13.14 and 13.16 the service was restarted. We will investigate what caused the problem and take steps to prevent it from happening again.

Support phones are now working.

Phone network operator Telia has technical issues and wide outages. Currently it is difficult to call the Litium support number. Email is working normally.

No other connectivity issues have been seen due to this incident. The issue will be investigated, and measures will be taken to mitigate issues like this. We are sorry for any inconvenience this have caused.

The cause has been identified as an network interruption. Connection was restored by a fail-over. We are still investigating the reason of this fail-over. All system are operating as normal and we continue monitoring.

We are continuing to investigating this issue

We have identified a sudden drop in incoming requests starting around 15:40 and for about 8 minutes. We are investigating the cause. Current state of the services is normal.

Our customers and partners started reporting performance issues around 11:52. Only customers on one of our SQL-clusters was affected. We identified that the issue was caused by problems with data synchronization to the secondary node. The issue was resolved 12:02. We are now working with our suppliers and Microsoft to investigate the cause and prohibit the issue from recurring.

We have had an issue related to Redis services. The issue has been identified to the infrastructure that is hosting one of our Kubernetes clusters. A fix has been implemented and we are monitoring the results.

# Report summary On June 13 connectivity to our primary data center was lost. As a consequence, customer websites were not reachable from the internet. All backend services, infrastructure and network were still functional. The connectivity problem was not isolated to Litium but affected many other hosting providers in the same data center. Our subcontractor began working immediately to find the cause of the problem. The problem was identified to electrical problems for the core router cluster in connection with a maintenance job performed by the data center provider. Technicians started to work on the identified issue to fix the problem and they were able to get the core router functional again. As the problem was solved all connectivity and website accessibility was restored. # Description 08:09 – Connectivity to our primary data center was lost 08:10 – Escalation to subcontractor and troubleshooting was started 08:40 – Verification from our subcontractor that Litium backend services and infrastructure was not affected. The problem was isolated to internet communication. 09:49 – Connectivity was restored, all Litium services and customer websites are now working again 09:50 – Verification process by Litium was initiated 13:02 – The incident was closed # Actions Litium have an ongoing dialog with our subcontractor on how this type of incident will be avoided in the future. We take this very seriously and work hard to ensure that our customers have the best possible service at all times. Actions are already taken by our subcontractor to ensure that maintenance jobs like this will not affect services. They are also working with the data center provider to implement better policies and routines to ensure this kind of situation is avoided. We are sorry for the inconvenience this incident has caused!

This incident has been resolved. The problem was in one of our data centers and affected the connection to the internet. We are now working to gather all the information about what caused the problem. We apologize for the inconvenience this incident has caused. Once we have gathered all the information about the issue, we will post a post-mortem report here.

The issue is fixed and all services is now operational. We will keep monitoring and start our post-mortem investigation. More information regarding this incident will be posted here.

The issue is identified to one of our data centers. The incident is affecting communication and technicians are working on resolving the issue.

The incident is not isolated to Litium Cloud. We are still investigating the extent of this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved for all affected customers. We are now focused on gather all information around this incident and a post-mortem report will be available for the affected customers later next week.

As this incident only affect a few customers and that the affected customers has a implemented intermediate solution, all communication forward, will be directly with those affected customers and their partners individually. We will still keep this incident open but with less updates.

We are continuing to work on a fix for this issue. We have also implemented a intermediate solution for affected customers to get them up and running.

We are continuing to work on a fix for this issue. The disk scan is still in progress. We are also investigating other possible solution to get affected sites up and running.

The error is due to a faulty windows file system. We are currently running disk scan to fix the corruption. We do not currently have an ETA on when the scan is completed. As a proactively measure we have also started a restore of the faulty disk from backup. This as a secondary measure.

We are still work on a fix for this issue. We will continuously update the status as we have more information to provide.

The cause has been identified and we are now working on a fix.

Storage service is partly down. Investigation is ongoing.

As an effect of the incident on Friday, we see some disruption to a number of support services. The services work but risk problems. As a proactive measure, we will restart these services. This will mean a short downtime but will only affect sFTP, RDG and SMTP. No customers are expected to have a direct impact on their websites. Integrations and e-mails may be affected for a short period. Access to customers' environments will be affected. We expect the restart to take about 10 min.

We have now monitored all services for 24 hours and everything is stable. The preliminary investigation of the incident says that the disruption was caused by a bug in Microsoft Windows. This in turn made one of our SQL clusters unstable and the cluster service no longer worked as expected. We apologize for the inconvenience this have caused.

Full availability is restored.

The interruption is now identified and located to one SQL server.

We are still investigating the cause to the interruption.

We are currently seeing service interruption. Investigation is ongoing.

No further issues during the night. The service is fully functional. The source of the problem has been identified to a Microsoft cluster component and we will continue the dialogue with the vendor about any further action.

The service has worked well after the problem but we will continue to monitor any further problems. At the same time, we are also investigating the root cause of the problem.

One database cluster had reduced performance for a short moment. We continue to monitor the situation.

We have monitored the implemented fix during the night and the service is fully operational. We apologize for any inconvenience this have caused to our customers.

The implemented solution has solved the problem and the service is now fully operational. We will keep monitoring the state over the night.

The problem has been identified and a solution has been implemented. We will monitor the condition and take action accordingly.

We are currently investigating this issue.