- Detected by Pingoru
- Aug 17, 2026, 05:57 PM UTC
- Resolved
- Aug 26, 2026, 08:16 PM UTC
- Duration
- 9d 2h
Affected: Tokyo, JapanMumbai, IndiaSydney, AustraliaHamina, FinlandLondon, EnglandFrankfurt, GermanyMontréal, CanadaSão Paulo, BrazilIowa, USAVirginia, USAOregon, USAJurong West, SingaporeDammam, Saudi ArabiaDoha, QatarZurich, SwitzerlandOsaka, JapanDelhi, India
Timeline · 5 updates
-
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.
-
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.
-
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.
-
monitoring Aug 18, 2026, 06:46 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 26, 2026, 08:16 PM UTC
Fix applied in production
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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 →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
-
resolved Dec 08, 2025, 04:26 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
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 →
- Detected by Pingoru
- Nov 18, 2025, 12:43 PM UTC
- Resolved
- Nov 19, 2025, 12:57 AM UTC
- Duration
- 12h 13m
Timeline · 2 updates
-
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
-
resolved Nov 19, 2025, 12:57 AM UTC
The Cloudflare incident has been resolved.
Read the full incident report →
