Is Liferay down?
Last checked 3m agoNo incidents right now.
Liferay is operational right now. Last checked 3m ago; the most recent incident resolved 17d ago.
Real-time Liferay status, recent outages, and incident history — pulled directly from Liferay's official status page at https://status.liferay.com every 5 minutes. Pingoru tracks 36 Liferay services and has captured 5 incidents in the last 90 days (99.86% uptime). Get email, Slack, Discord, or webhook alerts the moment Liferay reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Liferay Cloud Console
Timeline · 4 updates
- investigating · May 27, 2026, 11:45 AM UTC
Some customers noticed issues to properly display some logs on the Cloud Console. The team is currently investigating the matter.
- identified · May 27, 2026, 11:48 AM UTC
The issue has been identified and the fix is under development.
- monitoring · May 27, 2026, 04:32 PM UTC
A fix has been implemented for this issue. A new deploy of DXP is needed to recover access to the logs. Important to note that no log information has been lost. We are sorry for this inconvenience. If the issue still persist after the deployment please reach out to our support for further investigation.
- resolved · May 27, 2026, 07:46 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Tokyo, JapanInfrastructure ServicesMumbai, IndiaSydney, AustraliaHamina, FinlandLondon, EnglandFrankfurt, GermanyMontréal, CanadaSão Paulo, BrazilIowa, USA
Timeline · 1 update
- resolved · May 15, 2026, 04:04 PM UTC
Yesterday, the Liferay Cloud Infrastructure team performed emergency maintenance across our Kubernetes clusters. This action was taken to patch a critical vulnerability identified as CVE-2026-31431 in the Linux kernel. Reason for Emergency Action: Due to the high criticality of this vulnerability, we opted for an immediate rollout and minimal initial disclosure to mitigate the risk of exploitation. Providing detailed information before the patch could have alerted malicious actors, potentially leading to attacks. Technical Details & Risk: The vulnerability (CVE-2026-31431) allowed an attacker with shell access to perform a container escape, gaining root access to the host GKE node. Actions Taken: - All GKE clusters were updated to the latest secure version. - The maintenance was executed during off-peak hours for each region to minimize impact. - Our infrastructure team remains on high alert throughout Thursday and Friday for continuous monitoring. Security Commitment: Protecting our customers' data and infrastructure is our top priority. We thank you for your understanding regarding the lack of prior notice in this exceptional circumstance.
Latest: Yesterday, the Liferay Cloud Infrastructure team performed emergency maintenance across our Kubernetes clusters. This action was taken to patch a critical vulnerability identified …
-
- Tokyo, JapanInfrastructure ServicesMontréal, CanadaSão Paulo, BrazilIowa, USAOregon, USADoha, QatarZurich, Switzerland
Timeline · 3 updates
- investigating · May 14, 2026, 08:52 PM UTC
Due to the large number of nodes involved in the Liferay Kubernetes upgrade, it was necessary to extend the maintenance window.
- identified · May 14, 2026, 08:54 PM UTC
As part of this maintenance, a brief restart of some services may happen. High Availability customers should not experience downtimes.
- resolved · May 15, 2026, 12:32 AM UTC
This incident has been resolved. Maintenance completed.
Latest: This incident has been resolved. Maintenance completed.
-
- Infrastructure ServicesSydney, AustraliaNetworking Services
Timeline · 2 updates
- investigating · Mar 20, 2026, 08:41 PM UTC
Investigating: We are aware of performance issues in the Australia Southeast region starting at 18:07 UTC. Teams are on the case.
- resolved · Mar 20, 2026, 09:47 PM UTC
The issue with the cloud provider has been resolved.
Latest: The issue with the cloud provider has been resolved.
-
- Started May 27, 2026, 11:45 AM UTC · Resolved May 27, 2026, 07:46 PM UTC · 8h 1m
- Started May 15, 2026, 04:04 PM UTC · Resolved May 15, 2026, 04:04 PM UTC · —
- Started May 14, 2026, 08:52 PM UTC · Resolved May 15, 2026, 12:32 AM UTC · 3h 40m
- Started Mar 20, 2026, 08:41 PM UTC · Resolved Mar 20, 2026, 09:47 PM UTC · 1h 5m