Liferay Outage History

Liferay is up right now

Pingoru has recorded 49 incidents for Liferay: 8 in the last 12 months and 1 in the last 90 days.

Source: status.liferay.com

49incidents recorded
8last 12 months
1last 90 days
32 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Liferay in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026312 of 744 (2%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 20261218 of 744 (29%)
September 202600 of 720 (0%)
October 202600 of 526 (0%)

Incidents, newest first

Notice August 17, 2026 Incorrect Auto-Scaling Email Notification for Search Service 9d 2h Tokyo, Japan, Mumbai, India, Sydney, Australia, Hamina, Finland and 13 more

Started Aug 17, 2026, 05:57 PM UTC· resolved Aug 26, 2026, 08:16 PM UTC

  1. investigating Aug 17, 2026, 05:57 PM UTC

    We are investigating an issue where some Liferay Cloud customers are receiving incorrect auto-scaling notification emails for their Search service. If you have already received one of these emails, no action is required on your end.

  2. investigating Aug 17, 2026, 07:36 PM UTC

    During our investigation, we confirmed that incorrect Auto-Scaling email notifications were triggered for Liferay UAT and DEV environments. We are continuing to investigate; if needed, please feel free to open a support ticket.

  3. identified Aug 18, 2026, 06:46 PM UTC

    The incorrect Auto-Scaling email notifications were caused by a bug triggered during a Search service volume resize in non-production environments. The resize has been completed and this issue will not recur. If you received any Auto-Scaling emails regarding the Search service, please disregard them — no action is required on your end.

  4. monitoring Aug 18, 2026, 06:46 PM UTC

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

  5. resolved Aug 26, 2026, 08:16 PM UTC

    Fix applied in production

Read the full incident report →

Major May 27, 2026 Issues to display logs on the Cloud Console 8h 1m Liferay Cloud Console

Started May 27, 2026, 11:45 AM UTC· resolved May 27, 2026, 07:46 PM UTC

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

  2. identified May 27, 2026, 11:48 AM UTC

    The issue has been identified and the fix is under development.

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

  4. resolved May 27, 2026, 07:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 15, 2026 Security Update: Critical Kubernetes Maintenance (CVE-2026-31431 in the Linux kernel) – Tokyo, Japan, Infrastructure Services, Mumbai, India, Sydney, Australia and 12 more

Started May 15, 2026, 04:04 PM UTC· resolved May 15, 2026, 04:04 PM UTC

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

Read the full incident report →

Notice May 14, 2026 Incident: Extended Maintenance for Liferay Kubernetes Upgrade 3h 40m Tokyo, Japan, Infrastructure Services, Montréal, Canada, São Paulo, Brazil and 4 more

Started May 14, 2026, 08:52 PM UTC· resolved May 15, 2026, 12:32 AM UTC

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

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

  3. resolved May 15, 2026, 12:32 AM UTC

    This incident has been resolved. Maintenance completed.

Read the full incident report →

Minor March 20, 2026 Instability in the Australia Southeast clusters impacting customer projects 1h 5m Infrastructure Services, Sydney, Australia, Networking Services

Started Mar 20, 2026, 08:41 PM UTC· resolved Mar 20, 2026, 09:47 PM UTC

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

  2. resolved Mar 20, 2026, 09:47 PM UTC

    The issue with the cloud provider has been resolved.

Read the full incident report →

Minor December 8, 2025 Issues when retrieving logs 7h 2m Infrastructure Services, Liferay Cloud Console

Started Dec 08, 2025, 09:24 AM UTC· resolved Dec 08, 2025, 04:26 PM UTC

  1. investigating Dec 08, 2025, 09:24 AM UTC

    We are currently seeing missing or fewer logs available. We are investigating the problem with our cloud provider.

  2. resolved Dec 08, 2025, 04:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 3, 2025 OKTA Instability 3h 4m Europe (EU), North America (United States), Latin America (Brazil)

Started Dec 03, 2025, 02:13 PM UTC· resolved Dec 03, 2025, 05:18 PM UTC

  1. investigating Dec 03, 2025, 02:13 PM UTC

    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

  2. resolved Dec 03, 2025, 05:18 PM UTC

    The issue impacting the core authentication service for customers in Okta has been resolved

Read the full incident report →

Notice November 18, 2025 Cloudflare Instability 12h 13m

Started Nov 18, 2025, 12:43 PM UTC· resolved Nov 19, 2025, 12:57 AM UTC

  1. investigating Nov 18, 2025, 12:43 PM UTC

    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

  2. resolved Nov 19, 2025, 12:57 AM UTC

    The Cloudflare incident has been resolved.

Read the full incident report →

Critical September 16, 2025 LA Datacenter ISP Outage 8h 1m releases.liferay.com

Started Sep 16, 2025, 02:28 PM UTC· resolved Sep 16, 2025, 10:30 PM UTC

  1. monitoring Sep 16, 2025, 02:28 PM UTC

    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.

  2. monitoring Sep 16, 2025, 03:15 PM UTC

    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.

  3. monitoring Sep 16, 2025, 04:13 PM UTC

    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.

  4. monitoring Sep 16, 2025, 05:09 PM UTC

    Service provider has notified us that the ETR remains unchanged, and the repair is ongoing.

  5. monitoring Sep 16, 2025, 06:10 PM UTC

    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.

  6. monitoring Sep 16, 2025, 07:21 PM UTC

    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.

  7. monitoring Sep 16, 2025, 10:21 PM UTC

    The fiber restoration is complete, and services are back online. Thank you for your patience.

  8. resolved Sep 17, 2025, 07:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 12, 2025 Build failures for some customers 1d 10h

Started Sep 12, 2025, 07:23 AM UTC· resolved Sep 13, 2025, 05:42 PM UTC

  1. investigating Sep 12, 2025, 07:23 AM UTC

    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.

  2. monitoring Sep 12, 2025, 10:31 PM UTC

    All images but 2025.q1.13 have been updated. We are monitoring the issue and working to mitigate the remaining image.

  3. resolved Sep 13, 2025, 05:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2025 CI service issue after Certificate renewal 21h 6m Infrastructure Services, Frankfurt, Germany, Montréal, Canada

Started Aug 12, 2025, 01:58 PM UTC· resolved Aug 13, 2025, 11:04 AM UTC

  1. monitoring Aug 12, 2025, 01:58 PM UTC

    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

  2. resolved Aug 13, 2025, 11:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2025 Infrastructure Services Instability 3h 52m Infrastructure Services, Liferay Cloud Console, Liferay Cloud API

Started Jun 12, 2025, 07:28 PM UTC· resolved Jun 12, 2025, 11:21 PM UTC

  1. investigating Jun 12, 2025, 07:28 PM UTC

    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.

  2. monitoring Jun 12, 2025, 08:29 PM UTC

    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.

  3. resolved Jun 12, 2025, 11:21 PM UTC

    The incident has been resolved and all systems are operational

Read the full incident report →

Minor June 5, 2025 Kubernetes-upgrades 23h 53m Tokyo, Japan, Sydney, Australia, Hamina, Finland, Montréal, Canada and 2 more

Started Jun 05, 2025, 08:11 PM UTC· resolved Jun 06, 2025, 08:05 PM UTC

  1. investigating Jun 05, 2025, 08:11 PM UTC

    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

  2. monitoring Jun 05, 2025, 08:12 PM UTC

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

  3. monitoring Jun 05, 2025, 08:46 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jun 06, 2025, 03:03 AM UTC

    The incident has ended. Our team will continue to actively monitor system performance to ensure a complete return to normal.

  5. monitoring Jun 06, 2025, 08:48 AM UTC

    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.

  6. resolved Jun 06, 2025, 08:05 PM UTC

    The issue has been resolved.

Read the full incident report →

Notice April 9, 2025 api.liferay.com down because of expired SSL certifitace 1h 58m

Started Apr 09, 2025, 01:42 PM UTC· resolved Apr 09, 2025, 03:41 PM UTC

  1. investigating Apr 09, 2025, 01:42 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 09, 2025, 03:40 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 09, 2025, 03:41 PM UTC

    The cert used on our haproxy-vm had expired and has been replaced

Read the full incident report →

Notice March 31, 2025 files.liferay.com and releases.liferay.com were temporarily down –

Started Mar 31, 2025, 06:00 PM UTC· resolved Mar 31, 2025, 06:00 PM UTC

  1. resolved Mar 31, 2025, 06:50 PM UTC

    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.

Read the full incident report →

Notice March 31, 2025 We are experiencing an outage on our main firewalls that are handling the incoming traffic of the LAX DataCenter. –

Started Mar 31, 2025, 12:30 PM UTC· resolved Mar 31, 2025, 12:30 PM UTC

  1. resolved Mar 31, 2025, 01:09 PM UTC

    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.

Read the full incident report →

Notice March 29, 2025 Brief infrastructure downtime in South America – Infrastructure Services, Storage Services, São Paulo, Brazil

Started Mar 29, 2025, 01:18 PM UTC· resolved Mar 29, 2025, 01:18 PM UTC

  1. resolved Mar 29, 2025, 01:18 PM UTC

    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.

Read the full incident report →

Notice March 28, 2025 Certificate on releases.liferay.com will expire 4/8/25 –

Started Mar 28, 2025, 08:19 PM UTC· resolved Mar 28, 2025, 08:19 PM UTC

  1. resolved Mar 28, 2025, 08:19 PM UTC

    The certificate for releases.liferay.com has been renewed and is being applied to the server. Downtime expected to be about 10 minutes

Read the full incident report →

Notice March 28, 2025 Brief infrastructure downtime in Europe West – Infrastructure Services, Storage Services, Frankfurt, Germany

Started Mar 28, 2025, 06:59 PM UTC· resolved Mar 28, 2025, 06:59 PM UTC

  1. resolved Mar 28, 2025, 06:59 PM UTC

    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.

Read the full incident report →

Notice March 24, 2025 The releases.liferay.com unreachable 2h 52m

Started Mar 24, 2025, 01:30 PM UTC· resolved Mar 24, 2025, 04:22 PM UTC

  1. resolved Mar 25, 2025, 10:54 PM 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

Read the full incident report →

Notice March 17, 2025 Certificate on customer.liferay.com has expired 2h 26m

Started Mar 17, 2025, 05:00 PM UTC· resolved Mar 17, 2025, 07:26 PM UTC

  1. resolved Mar 25, 2025, 10:59 PM UTC

    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

Read the full incident report →

Notice February 27, 2025 Brief infrastructure downtime in many regions – Tokyo, Japan, Infrastructure Services, Mumbai, India, Sydney, Australia and 10 more

Started Feb 27, 2025, 02:15 PM UTC· resolved Feb 27, 2025, 02:15 PM UTC

  1. resolved Feb 27, 2025, 02:15 PM 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.

Read the full incident report →

Major February 14, 2025 Builds page on Cloud Console not showing content 4d 4h Liferay Cloud Console

Started Feb 14, 2025, 01:51 PM UTC· resolved Feb 18, 2025, 06:43 PM UTC

  1. investigating Feb 14, 2025, 01:51 PM UTC

    Some customers are not able to see the list of Builds on the Cloud Console. The issue is intermittent. We are currently investigating.

  2. identified Feb 14, 2025, 05:33 PM UTC

    The issue was identified, and we applied the workaround. We continue working on the final fix.

  3. monitoring Feb 16, 2025, 01:38 PM UTC

    The issue is has been mitigated and no customer should have the problem anymore. The permanent fix will be deployed on Tuesday Feb 18th.

  4. resolved Feb 18, 2025, 06:43 PM UTC

    Fix applied. This incident has been resolved.

Read the full incident report →

Major February 13, 2025 Instability in the US-Central cluster impacting customer projects 19h 5m North America (United States), Iowa, USA

Started Feb 13, 2025, 05:35 PM UTC· resolved Feb 14, 2025, 12:40 PM UTC

  1. investigating Feb 13, 2025, 05:35 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 13, 2025, 07:03 PM UTC

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

  3. resolved Feb 14, 2025, 12:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 12, 2025 Customers are experiencing deployment issues in many regions 18h 21m Liferay Cloud API

Started Feb 12, 2025, 12:11 PM UTC· resolved Feb 13, 2025, 06:33 AM UTC

  1. investigating Feb 12, 2025, 12:11 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 12, 2025, 03:08 PM UTC

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

  3. resolved Feb 13, 2025, 06:33 AM UTC

    This incident has been resolved.

Read the full incident report →