Liferay Outage History

Liferay is up right now

Liferay had 10 outages in the last 2 years totaling 95h 54m of downtime — averaging 0.4 incidents per month.

There were 10 Liferay outages since August 12, 2025 totaling 95h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.liferay.com

Major May 27, 2026

Issues to display logs on the Cloud Console

Detected by Pingoru
May 27, 2026, 11:45 AM UTC
Resolved
May 27, 2026, 07:46 PM UTC
Duration
8h 1m
Affected: Liferay Cloud Console
Timeline · 4 updates
  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)

Detected by Pingoru
May 15, 2026, 04:04 PM UTC
Resolved
May 15, 2026, 04:04 PM UTC
Duration
—
Affected: Tokyo, JapanInfrastructure ServicesMumbai, IndiaSydney, AustraliaHamina, FinlandLondon, EnglandFrankfurt, GermanyMontréal, CanadaSão Paulo, BrazilIowa, USAVirginia, USAOregon, USAJurong West, SingaporeDammam, Saudi ArabiaDoha, QatarZurich, Switzerland
Timeline · 1 update

Read the full incident report →

Notice May 14, 2026

Incident: Extended Maintenance for Liferay Kubernetes Upgrade

Detected by Pingoru
May 14, 2026, 08:52 PM UTC
Resolved
May 15, 2026, 12:32 AM UTC
Duration
3h 40m
Affected: Tokyo, JapanInfrastructure ServicesMontréal, CanadaSão Paulo, BrazilIowa, USAOregon, USADoha, QatarZurich, Switzerland
Timeline · 3 updates
  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

Detected by Pingoru
Mar 20, 2026, 08:41 PM UTC
Resolved
Mar 20, 2026, 09:47 PM UTC
Duration
1h 5m
Affected: Infrastructure ServicesSydney, AustraliaNetworking Services
Timeline · 2 updates
  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

Detected by Pingoru
Dec 08, 2025, 09:24 AM UTC
Resolved
Dec 08, 2025, 04:26 PM UTC
Duration
7h 2m
Affected: Infrastructure ServicesLiferay Cloud Console
Timeline · 2 updates
  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

Detected by Pingoru
Dec 03, 2025, 02:13 PM UTC
Resolved
Dec 03, 2025, 05:18 PM UTC
Duration
3h 4m
Affected: Europe (EU)North America (United States)Latin America (Brazil)
Timeline · 2 updates
  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

Detected by Pingoru
Nov 18, 2025, 12:43 PM UTC
Resolved
Nov 19, 2025, 12:57 AM UTC
Duration
12h 13m
Timeline · 2 updates
  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

Detected by Pingoru
Sep 16, 2025, 05:09 PM UTC
Resolved
Sep 16, 2025, 10:30 PM UTC
Duration
5h 20m
Affected: releases.liferay.com
Timeline · 8 updates
  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

Detected by Pingoru
Sep 12, 2025, 07:23 AM UTC
Resolved
Sep 13, 2025, 05:42 PM UTC
Duration
1d 10h
Timeline · 3 updates
  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

Detected by Pingoru
Aug 12, 2025, 01:58 PM UTC
Resolved
Aug 13, 2025, 11:04 AM UTC
Duration
21h 6m
Affected: Infrastructure ServicesFrankfurt, GermanyMontréal, Canada
Timeline · 2 updates
  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 →