Liferay incident

Kubernetes-upgrades

Minor Resolved View vendor source →

Liferay experienced a minor incident on June 5, 2025 affecting Tokyo, Japan and Sydney, Australia and 1 more component, lasting 23h 53m. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2025, 08:11 PM UTC
Resolved
Jun 06, 2025, 08:05 PM UTC
Duration
23h 53m
Detected by Pingoru
Jun 05, 2025, 08:11 PM UTC

Affected components

Tokyo, JapanSydney, AustraliaHamina, FinlandMontréal, QuébecSão Paulo, BrazilOregon, USA

Update timeline

  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.