Liferay status history
Current state: operational — “All Systems Operational” per https://status.liferay.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Liferay incidents last?
From 10 incidents with a vendor-posted start and resolve time. Longest on record: Incorrect Auto-Scaling Email Notification for Search Service — 9.1 days (2026-08-17 17:57 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (11)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-17 17:57 UTC | Incorrect Auto-Scaling Email Notification for Search Service | resolved | none | 9 d 2 h |
| 2026-05-27 11:45 UTC | Issues to display logs on the Cloud Console | resolved | major | 8 h 01 min |
| 2026-05-15 16:04 UTC | Security Update: Critical Kubernetes Maintenance (CVE-2026-31431 in the Linux kernel) | resolved | none | 0 min |
| 2026-05-14 20:52 UTC | Incident: Extended Maintenance for Liferay Kubernetes Upgrade | resolved | none | 3 h 40 min |
| 2026-03-20 20:41 UTC | Instability in the Australia Southeast clusters impacting customer projects | resolved | minor | 1 h 05 min |
| 2025-12-08 09:24 UTC | Issues when retrieving logs | resolved | minor | 7 h 02 min |
| 2025-12-03 14:13 UTC | OKTA Instability | resolved | none | 3 h 04 min |
| 2025-11-18 12:43 UTC | Cloudflare Instability | resolved | none | 12 h 13 min |
| 2025-09-16 14:28 UTC | LA Datacenter ISP Outage | resolved | critical | 8 h 01 min |
| 2025-09-12 07:23 UTC | Build failures for some customers | resolved | none | 34 h 19 min |
| 2025-09-04 08:47 UTC | Maintenance notice before the planned time | resolved | maintenance | 6 h 59 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Liferay with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"liferay"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}