LiquidPlanner status history
Current state: operational — “All Systems Operational” per http://status.liquidplanner.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
2incidents, last 30 days
2incidents, last 90 days
18incidents on record
Incidents on record (18)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-03 22:15 UTC | Application errors with subset of features | resolved | major | 57 min |
| 2026-09-03 22:12 UTC | Degraded performance | resolved | none | 1 h 02 min |
| 2025-09-05 16:07 UTC | 500 Error when accessing member profile or accepting invitations | resolved | none | — |
| 2025-09-05 16:07 UTC | Email delivery issues | resolved | none | — |
| 2025-09-05 16:07 UTC | Slow load times and intermittent timeout | resolved | none | — |
| 2025-09-05 16:07 UTC | Delays and increased error rates | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner notifications delayed | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Service Alert | resolved | none | — |
| 2025-09-05 16:07 UTC | Slow load times and intermittent timeout | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Service Report | resolved | none | — |
| 2025-09-05 16:07 UTC | Inbound Notifications Delayed | resolved | none | — |
| 2025-09-05 16:07 UTC | Slow network traffic due to vendor issue | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Service Report | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Classic: Inbound & Outbound Notifications Delayed | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Classic: Inbound Notifications Error | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Classic: inbound & outbound email processing issue | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Website & Support pages unavailable | resolved | none | — |
| 2025-09-05 16:07 UTC | LiquidPlanner Service Report | resolved | none | — |
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 LiquidPlanner with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"liquidplanner"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}