All Systems Operational
Infrastructure Services
Operational
Database Services
Operational
Storage Services
Operational
Monitoring and Logging Services
Operational
Networking Services
Operational
Liferay Cloud Console
Operational
Liferay Cloud API
Operational
Liferay Cloud Platform Regions
Operational
Tokyo, Japan
Operational
Osaka, Japan
Operational
Mumbai, India
Operational
Sydney, Australia
Operational
Hamina, Finland
Operational
London, England
Operational
Frankfurt, Germany
Operational
Montréal, Canada
Operational
São Paulo, Brazil
Operational
Iowa, USA
Operational
Virginia, USA
Operational
Oregon, USA
Operational
Jurong West, Singapore
Operational
Dammam, Saudi Arabia
Operational
Doha, Qatar
Operational
Zurich, Switzerland
Operational
Delhi, India
Operational
Liferay Experience Cloud Regions
Operational
Europe (EU)
Operational
North America (United States)
Operational
Latin America (Brazil)
Operational
Liferay Systems
Operational
customer.liferay.com
Operational
releases.liferay.com
Operational
support.liferay.com
Operational
Analytics Cloud Website - analytics.liferay.com
Operational
Analytics Cloud Regions
Operational
Sao Paulo, Brazil
Operational
London, England
Operational
Frankfurt, Germany
Operational
Oregon, United States
Operational
Mumbai, India
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Database Upgrade (MySQL 8.4) - Non-Production Environments Oct 15, 2026 08:00-20:00 PDT
We are initiating our MySQL 8.4 upgrade strategy. On October 15th, we will perform the database upgrade for your non-production environments (UAT/DEV/SIT/PREPROD).
Please note that a separate, complementary scheduled maintenance has also been created for your Production environments, scheduled for November 5th.
- Execution Details & Customer Impact:
Maintenance is executed in regional waves strictly outside local business hours (between 6:00 PM and 5:00 AM customer local time).
Each customer environment will experience an expected downtime of approximately 20 to 30 minutes while services are restarted.
No customer action is required.
- Who is affected:
This only applies to customers running Liferay DXP 2024.Q1 or later who are using the MySQL 8.0 database.
- Compatibility and Downtime:
Versions 8.0 and 8.4 are fully compatible. This upgrade has already been successfully executed on more than 100 DXP customer databases without any detected impact or blockers. We expect a downtime of only 20 to 30 minutes for this process (restricted to the restart required to apply the new version).
- Impact on Restores (Backups):
The only functional impact during the transition period is that version 8.4 backups (snapshots) cannot be restored to version 8.0 databases. Therefore, during the gap between the UAT/DEV upgrade and the Production upgrade, you will not be able to restore data from a non-production environment to a production one. The reverse path (restoring from 8.0 to 8.4) will continue to work normally.
- Actions and Exceptions:
If this maintenance window causes any impact on your business or you do not agree with the proposed plan, please open a Support ticket to request rescheduling the maintenance outside this window.
Posted on Sep 30, 2026 - 11:39 PDT
Please note that a separate, complementary scheduled maintenance has also been created for your Production environments, scheduled for November 5th.
- Execution Details & Customer Impact:
Maintenance is executed in regional waves strictly outside local business hours (between 6:00 PM and 5:00 AM customer local time).
Each customer environment will experience an expected downtime of approximately 20 to 30 minutes while services are restarted.
No customer action is required.
- Who is affected:
This only applies to customers running Liferay DXP 2024.Q1 or later who are using the MySQL 8.0 database.
- Compatibility and Downtime:
Versions 8.0 and 8.4 are fully compatible. This upgrade has already been successfully executed on more than 100 DXP customer databases without any detected impact or blockers. We expect a downtime of only 20 to 30 minutes for this process (restricted to the restart required to apply the new version).
- Impact on Restores (Backups):
The only functional impact during the transition period is that version 8.4 backups (snapshots) cannot be restored to version 8.0 databases. Therefore, during the gap between the UAT/DEV upgrade and the Production upgrade, you will not be able to restore data from a non-production environment to a production one. The reverse path (restoring from 8.0 to 8.4) will continue to work normally.
- Actions and Exceptions:
If this maintenance window causes any impact on your business or you do not agree with the proposed plan, please open a Support ticket to request rescheduling the maintenance outside this window.
Posted on Sep 30, 2026 - 11:39 PDT
Database Upgrade (MySQL 8.4) - Production Environments Nov 5, 2026 08:00-20:00 PST
Following our MySQL 8.4 upgrade strategy, and subsequent to the non-production upgrades, we will roll out the update for your Production environments(PRD/PRD1/PRD2/DR/PROD) on November 5th.
As detailed in the Non-Production communication, versions 8.0 and 8.4 are fully compatible.
- Execution Details & Customer Impact:
Maintenance is executed in regional waves strictly outside local business hours (between 6:00 PM and 5:00 AM customer local time).
Each customer environment will experience an expected downtime of approximately 20 to 30 minutes while services are restarted.
No customer action is required.
- Actions and Exceptions:
If this maintenance window causes any impact on your business or you do not agree with the proposed plan, please open a Support ticket to request rescheduling the maintenance outside this window.
Posted on Sep 30, 2026 - 11:41 PDT
As detailed in the Non-Production communication, versions 8.0 and 8.4 are fully compatible.
- Execution Details & Customer Impact:
Maintenance is executed in regional waves strictly outside local business hours (between 6:00 PM and 5:00 AM customer local time).
Each customer environment will experience an expected downtime of approximately 20 to 30 minutes while services are restarted.
No customer action is required.
- Actions and Exceptions:
If this maintenance window causes any impact on your business or you do not agree with the proposed plan, please open a Support ticket to request rescheduling the maintenance outside this window.
Posted on Sep 30, 2026 - 11:41 PDT