https://approjects-vendor-status-watch.static.hf.space/v/liquidplanner.htmlIncidents from LiquidPlanner's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000http://status.liquidplanner.comliquidplanner:2026-09-03T22:15:31ZThu, 03 Sep 2026 22:15:31 +0000We're no longer seeing errors in the affected region. We'll continue to monitor, but no further issues are expected.http://status.liquidplanner.comliquidplanner:2026-09-03T22:12:00ZThu, 03 Sep 2026 22:12:00 +0000This incident has been resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:54ZFri, 05 Sep 2025 16:07:54 +0000This incident has been resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:54ZFri, 05 Sep 2025 16:07:54 +0000Some customers reported issues with email delivery (sending invitations, password reset, comments, recent change notifications, daily digest). Mail had been queued on our local servers following the release this weekend (7am Pacific, Saturday, November 4). Email notifications are flowing as expected now. We apologize for the inconvenience. You will receive all mail that had been generated, and you do not need to resend anything that was initiated while the mail was in queue.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:53ZFri, 05 Sep 2025 16:07:53 +0000We determined that a particular request pattern with poor performance consumed all of a webserver's available resources. This caused our health check to pull that host out of the load-balancing pool. The increased traffic to other hosts caused them to become overwhelmed as well, resulting in a brown-out of the entire application. There was no impact to customer data during this period. The application is accessible and operating as expected at this time.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:52ZFri, 05 Sep 2025 16:07:52 +0000After thorough investigation, we determined that we hit some unforeseen I/O limits with our database. The combination of a cache flush due to a restart, recalculation of some statistics, and peak load resulted in brownouts and occasional errors in our application. To remediate this type of resource exhaustion, we've purchased additional I/O capacity from AWS. As always, we'll continue to monitor and tune our database configuration in response to the large amounts of data that we process. There was no impact to customer data during this period. The application is accessible and operating as expected at this time.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:51ZFri, 05 Sep 2025 16:07:51 +0000This incident has been resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:51ZFri, 05 Sep 2025 16:07:51 +0000We determined that a particular request pattern with poor performance consumed all of a webserver's available resources. This caused our health check to pull that host out of the load-balancing pool. The increased traffic to other hosts caused them to become overwhelmed as well, resulting in a brown-out of the application. Our team acted quickly and service restored in ten minutes. There was no impact to customer data during this period. The application is accessible and operating as expected at this time.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:50ZFri, 05 Sep 2025 16:07:50 +0000Our team investigated the incident and determined that some of the recurring automated tuning operations performed by the PostgreSQL database platform created a bottleneck in the LiquidPlanner operating environment. Requests backed up and some users experienced slow operations and errors. We've since added additional database I/O capacity and adjusted the automated tuning operations to prevent this issue in the future. Thanks for your continuing support and patience.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:50ZFri, 05 Sep 2025 16:07:50 +0000Degraded performance in a back up system resulted in isolated slow-downs in service. That infrastructure has stabilized and this incident is resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:49ZFri, 05 Sep 2025 16:07:49 +0000Our email service provider resolved the issue and systems have returned to normal.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:48ZFri, 05 Sep 2025 16:07:48 +0000This incident has been resolved. Our provider confirms that service is operating normally.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:47ZFri, 05 Sep 2025 16:07:47 +0000AWS confirms that the incident is resolved and systems are operating normally.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:45ZFri, 05 Sep 2025 16:07:45 +0000Our notification queue is now empty, and notifications are functioning normally. This incident has been resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:43ZFri, 05 Sep 2025 16:07:43 +0000This incident has been resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:42ZFri, 05 Sep 2025 16:07:42 +0000Our service provider reported their email services are fully operational again and this incident is resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:41ZFri, 05 Sep 2025 16:07:41 +0000This incident has been resolved.http://status.liquidplanner.comliquidplanner:2025-09-05T16:07:40ZFri, 05 Sep 2025 16:07:40 +0000This incident has been resolved.