Vendor Status Watch

← all vendors

Liferay status history

Current state: operational — “All Systems Operational” per https://status.liferay.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
1incidents, last 90 days
11incidents on record
Incidents per week, last 12 weeks:

How long do Liferay incidents last?

7.5 hmedian incident duration10 measured
34.3 h90th percentile1 in 10 ran longer
8.0 hmedian, major/critical only2 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-17 17:57 UTCIncorrect Auto-Scaling Email Notification for Search Serviceresolvednone9 d 2 h
2026-05-27 11:45 UTCIssues to display logs on the Cloud Consoleresolvedmajor8 h 01 min
2026-05-15 16:04 UTCSecurity Update: Critical Kubernetes Maintenance (CVE-2026-31431 in the Linux kernel)resolvednone0 min
2026-05-14 20:52 UTCIncident: Extended Maintenance for Liferay Kubernetes Upgraderesolvednone3 h 40 min
2026-03-20 20:41 UTCInstability in the Australia Southeast clusters impacting customer projectsresolvedminor1 h 05 min
2025-12-08 09:24 UTCIssues when retrieving logsresolvedminor7 h 02 min
2025-12-03 14:13 UTCOKTA Instabilityresolvednone3 h 04 min
2025-11-18 12:43 UTCCloudflare Instabilityresolvednone12 h 13 min
2025-09-16 14:28 UTCLA Datacenter ISP Outageresolvedcritical8 h 01 min
2025-09-12 07:23 UTCBuild failures for some customersresolvednone34 h 19 min
2025-09-04 08:47 UTCMaintenance notice before the planned timeresolvedmaintenance6 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
}