Liferay had 28 outages in the last 2 years totaling 919h 9m of downtime — averaging 1.2 incidents per month.
There were 28 Liferay outages since May 20, 2024 totaling 919h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
Due to the large number of nodes involved in the Liferay Kubernetes upgrade, it was necessary to extend the maintenance window.
As part of this maintenance, a brief restart of some services may happen. High Availability customers should not experience downtimes.
This incident has been resolved. Maintenance completed.
Investigating: We are aware of performance issues in the Australia Southeast region starting at 18:07 UTC. Teams are on the case.
The issue with the cloud provider has been resolved.
We are currently seeing missing or fewer logs available. We are investigating the problem with our cloud provider.
This incident has been resolved.
We would like to inform you that our customers using OKTA are experiencing instability. This is an external issue, caused by an incident on the Okta Services - Core Platform. Restoration is expected as soon as the incident is resolved by them. You can follow the official status here: https://status.okta.com/#incident/a9CWR00000012EI2AY
The issue impacting the core authentication service for customers in Okta has been resolved
We would like to inform you that our customers using Cloudflare are experiencing instability or downtime. This is an external issue, caused by a large-scale incident on the Cloudflare global network . Restoration is expected as soon as the incident is resolved by them. You can follow the official status here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
The Cloudflare incident has been resolved.
at 4:30am Pacific time our IT Infrastructure team noticed an outage in our Los Angeles datacenter. After triage, it was discovered that the cause was due to the fiber bundle owned by the ISP running to the data center had been damaged. Repair crews are on site and are working on re-splicing the fiber. ETR is within 4-6 hours.
Our service provider has added additional details: They are working now to repair the 432 count fiber bundle that was vandalized. Updates will be provided hourly, with an estimated repair completion time of 2:00 PM Pacific Time today, 9/16.
Service Provider Construction team continues to run fiber. The estimated time for service to be restored is still 9/16/2025 2:00 PM Pacific Time. We will continue to send updates regularly or as conditions change.
Service provider has notified us that the ETR remains unchanged, and the repair is ongoing.
Service Provider Construction team continues to run second 432ct fiber for repair. The estimated time for service to be restored remains 9/16/2025 2:00 PM Pacific Time.
The Service Provider Construction team has added another update. Due to the additional 432ct fiber impacted the updated estimated time for service to be restored has been pushed back to 9/16/2025 6:00 PM Pacific Time. We will continue to send regular updates or as conditions change.
The fiber restoration is complete, and services are back online. Thank you for your patience.
This incident has been resolved.
We are currently investigating build failures affecting some customers. The issue is related to the Ubuntu version used in our some of our Docker base images, which can no longer access required repositories.
All images but 2025.q1.13 have been updated. We are monitoring the issue and working to mitigate the remaining image.
This incident has been resolved.
Following a recent Cloud certificate update, some customers may experience issues with the CI service. This is due to a Build Retention Policy change that was announced in early 2025. To resolve this, affected customers need to update their CI image to liferaycloud/jenkins:2.492.3-lts-jdk21-6.1.0. It might be required to delete the CI service before deploying the new version. You can review the details of the policy change here: https://help.liferay.com/hc/pt/articles/34379092287885-Build-Retention-Policy
This incident has been resolved.
We are experiencing issues with our infrastructure provider. We are monitoring to mitigate any potential impact. Symptoms on our platform are unavailability of the Cloud Console, Deployment failures and backup failures. In some cases there are issues to retrieve documents from the Document Library. Some of our customer's are also experiencing downtimes.
Root cause has been identified by the infrastructure provider and recovery of all services are underway. Some services take longer to recover than others. We are monitoring the situation taking necessary actions to recover all services.
The incident has been resolved and all systems are operational
Our infrastructure provider is performing kubernetes upgrades from 8:00 AM Pacific time to 8:00 PM Pacific time and customers on standard availability might suffer a brief downtime
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
The incident has ended. Our team will continue to actively monitor system performance to ensure a complete return to normal.
Some customers may observe that the database service may show an Unhealthy status and continuously logs the following error message: ER_SPECIFIC_ACCESS_DENIED_ERROR: Access denied; you need (at least one of) the SUPER privilege(s) for this operation. Impact: There is no impact on database functionality or data integrity. Recommended Action: Please restart the database service. If the status remains Unhealthy, open a support ticket and reference this notice. Next Steps: We will provide further updates as more information becomes available.
The issue has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The cert used on our haproxy-vm had expired and has been replaced
Some systems were unable to verify the validity of the new certificate for the liferay.com domain, so we had to update the CA certificate chain on the web server and this required restarting the web server. The systems are now accessible and operational.
All inbound traffic to the Diamond Bar DataCenter was being blocked due to an error in our inbound firewalls. This affected access to services hosted there such as releases.liferay.com and files.liferay.com. The firewalls have been fixed. The DataCenter is operational again.
A service interruption on March 29, 2025, impacted the southamerica-east1-p3-c1 cluster, causing temporary downtime for projects hosted within it. This disruption was caused by increased latency on the File System during a routine file system maintenance of the service provided by our cloud infrastructure partner. All services are fully restored.
The certificate for releases.liferay.com has been renewed and is being applied to the server. Downtime expected to be about 10 minutes
A service interruption on March 28, 2025, impacted the europe-west3-p6 cluster, causing temporary downtime for projects hosted within it. This disruption was caused by increased latency on the File System during a routine file system maintenance of the service provided by our cloud infrastructure partner. All services are fully restored.
Date and time it occurred: March 17th 17:05 UTC Description: The certificate that was renewed was not reloaded on the webserver of the LFU server, which is responsible for storing the large customer.liferay.com files. Resolution: IT restarted the webserver to reload the new certificate and the certificate reload automation was configured. Date of resolution: March 17th 19:26 UTC
Date and time it occurred: March 24th 13:34 UTC Description: The webserver hosting releases.liferay.com crashed due to a locked process on the host. Resolution: IT restarted the web server. Date of resolution: March 24th 16:22 UTC
We identified that a brief period of downtime affected some customers using older DXP versions. Liferay's self healing capabilities restored all environments promptly. This disruption was caused by increased latency on the File System during a routine file system maintenance of the service provided by our cloud infrastructure partner. The maintenance happened on Feb 25th. To mitigate the risk of recurrence, we strongly recommend upgrading to the 2025.Q1 release. This release enables a transition to improved file systems, designed to enhance performance and stability.
Some customers are not able to see the list of Builds on the Cloud Console. The issue is intermittent. We are currently investigating.
The issue was identified, and we applied the workaround. We continue working on the final fix.
The issue is has been mitigated and no customer should have the problem anymore. The permanent fix will be deployed on Tuesday Feb 18th.
Fix applied. 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.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some users experience issues with logging into the cloud console when not using SSO. The team is currently investigating.
A fix has been implemented and we are monitoring the results.
The team is still monitoring and working on the issue as the issue might happen on rare occasions.
The issue was resolved. We continue monitoring to grant platform availability.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Our infrastructure provider has an ongoing issue with resource allocation that prevents backup restoration activities for services hosted in Dammam, Saudi Arabia Region. We're closely monitoring the situation and will provide updates as soon as possible.
A mitigation was identified. If you need to perform backup restorations in this region, please reach our Help Center.
Our infrastructure provider has informed us that they are actively working to fix the issue. They estimate a resolution by the second week of November.
We have successfully resolved the issue impacting backup restoration activities in the Dammam, Saudi Arabia region.