Time: July 13, 2018, 4:43 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 13, 2018, 2:08 p.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results.

Time: July 13, 2018, 1:59 p.m.

Status: Identified

Update: Our email processing provider confirms services are operating as expected. Email to your workspace has resumed. Items previously sent have been processed.

Time: July 13, 2018, 1:28 p.m.

Status: Identified

Update: Our email processing provider experienced an issue which affected both inbound and outbound email processing. They have implemented a fix and emails are processing again. While the service was disrupted, you would not have received a notification if someone commented at you, or if there was a change to an item you own or follow. If you replied to a previous notification from your personal email client, it was delayed and did not appear in the workspace as expected. Tasks were not created via email. There is no need to resend emails, the system received them and will complete the send cycle shortly. If you invited a new member to the workspace, please contact [email protected] if that invitation is not received.

Time: July 13, 2018, 1:10 p.m.

Status: Investigating

Update: Some customers have reported issues with email integration affecting the ability to comment or create tasks via email. We are working with our provider to understand the timing for resolution. This is related to notifications only, all other aspects of LiquidPlanner are functioning normally. There's no impact to customer data. We'll update you as we know more. Thank you for your patience.

Time: July 13, 2018, 4:43 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: July 13, 2018, 2:08 p.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results.

Time: July 13, 2018, 1:59 p.m.

Status: Identified

Update: Our email processing provider confirms services are operating as expected. Email to your workspace has resumed. Items previously sent have been processed.

Time: July 13, 2018, 1:28 p.m.

Status: Identified

Update: Our email processing provider experienced an issue which affected both inbound and outbound email processing. They have implemented a fix and emails are processing again. While the service was disrupted, you would not have received a notification if someone commented at you, or if there was a change to an item you own or follow. If you replied to a previous notification from your personal email client, it was delayed and did not appear in the workspace as expected. Tasks were not created via email. There is no need to resend emails, the system received them and will complete the send cycle shortly. If you invited a new member to the workspace, please contact [email protected] if that invitation is not received.

Time: July 13, 2018, 1:10 p.m.

Status: Investigating

Update: Some customers have reported issues with email integration affecting the ability to comment or create tasks via email. We are working with our provider to understand the timing for resolution. This is related to notifications only, all other aspects of LiquidPlanner are functioning normally. There's no impact to customer data. We'll update you as we know more. Thank you for your patience.

Time: May 17, 2018, 7:22 p.m.

Status: Resolved

Update: We 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.

Time: May 17, 2018, 6:37 p.m.

Status: Investigating

Update: Operations normal. We're monitoring systems.

Time: May 17, 2018, 6:27 p.m.

Status: Investigating

Update: Our team is investigating a service issue. Some customers reports seeing "site under heavy load" We'll update this page again as soon as we have more information to share. Thanks for your patience.

Time: May 17, 2018, 7:22 p.m.

Status: Resolved

Update: We 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.

Time: May 17, 2018, 6:37 p.m.

Status: Investigating

Update: Operations normal. We're monitoring systems.

Time: May 17, 2018, 6:27 p.m.

Status: Investigating

Update: Our team is investigating a service issue. Some customers reports seeing "site under heavy load" We'll update this page again as soon as we have more information to share. Thanks for your patience.

Time: April 24, 2018, 4:13 p.m.

Status: Resolved

Update: After 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.

Time: April 24, 2018, 4:13 p.m.

Status: Resolved

Update: After 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.

Time: April 24, 2018, 2:04 a.m.

Status: Monitoring

Update: The LiquidPlanner application is working as expected following the update. We are continuing to monitor the systems closely.

Time: April 24, 2018, 2:04 a.m.

Status: Monitoring

Update: The LiquidPlanner application is working as expected following the update. We are continuing to monitor the systems closely.

Time: April 24, 2018, 12:57 a.m.

Status: Identified

Update: 6pm - 7pm Pacific Daylight time, LiquidPlanner is undergoing maintenance to improve performance. The application is available, but you may experience delays in scheduling and page loads while changes roll out across the system.

Time: April 24, 2018, 12:57 a.m.

Status: Identified

Update: 6pm - 7pm Pacific Daylight time, LiquidPlanner is undergoing maintenance to improve performance. The application is available, but you may experience delays in scheduling and page loads while changes roll out across the system.

Time: April 23, 2018, 10:16 p.m.

Status: Identified

Update: The LiquidPlanner application is accessible. Some users may find it slow to reschedule or load pages. We'll address these issues in a release going out at 6pm Pacific Daylight time today, April 23, 2018. Thank you for your continued patience.

Time: April 23, 2018, 10:16 p.m.

Status: Identified

Update: The LiquidPlanner application is accessible. Some users may find it slow to reschedule or load pages. We'll address these issues in a release going out at 6pm Pacific Daylight time today, April 23, 2018. Thank you for your continued patience.

Time: April 23, 2018, 8:33 p.m.

Status: Identified

Update: To minimize further disruption, we moved our planned update outside of US business hours. Changes will release at 6pm Pacific Daylight time. We apologize for the performance issues today and thank you for your patience while we determine the best course of action to rectify the situation.

Time: April 23, 2018, 7:25 p.m.

Status: Identified

Update: At 2pm Pacific Daylight time our team will release an update to address performance issues. There may be a degradation in service while changes roll out until the system stabilizes.

Time: April 23, 2018, 6:35 p.m.

Status: Identified

Update: We've identified the source of the performance issues, and will make changes later this afternoon (Pacific time) to correct the problem. There may be intermittent performance issues in the meantime (slow page loads and scheduling). We're currently analyzing site traffic history to determine the optimum time to make updates. We'll post again prior to updating to make you aware of the time we expect to make changes. The app will be accessible during the maintenance period.

Time: April 23, 2018, 6:35 p.m.

Status: Identified

Update: We've identified the source of the performance issues, and will make changes later this afternoon (Pacific time) to correct the problem. There may be intermittent performance issues in the meantime (slow page loads and scheduling). We're currently analyzing site traffic history to determine the optimum time to make updates. We'll post again prior to updating to make you aware of the time we expect to make changes. The app will be accessible during the maintenance period.

Time: April 23, 2018, 5:13 p.m.

Status: Identified

Update: We continue to see improved performance although some monitors still show slower response times than normal. All areas of the application are accessible. We will update this page until resolved.

Time: April 23, 2018, 5:13 p.m.

Status: Identified

Update: We continue to see improved performance although some monitors still show slower response times than normal. All areas of the application are accessible. We will update this page until resolved.

Time: April 23, 2018, 4:04 p.m.

Status: Identified

Update: Engineers have made changes to reduce load, and application performance is back to normal levels. We're still monitoring the situation, and will provide a more thorough update soon. We apologize for the inconvenience and appreciate your patience.

Time: April 23, 2018, 4:04 p.m.

Status: Identified

Update: Engineers have made changes to reduce load, and application performance is back to normal levels. We're still monitoring the situation, and will provide a more thorough update soon. We apologize for the inconvenience and appreciate your patience.

Time: April 23, 2018, 3:16 p.m.

Status: Identified

Update: Some customers are seeing a message that the website is under heavy load. We're tracking down the cause.

Time: April 23, 2018, 3:16 p.m.

Status: Identified

Update: Some customers are seeing a message that the website is under heavy load. We're tracking down the cause.

Time: April 23, 2018, 2:22 p.m.

Status: Investigating

Update: We are experience slow load times. The app is accessible and performance is improving. Our team is monitoring continuously and working to resolve.

Time: April 23, 2018, 2:02 p.m.

Status: Investigating

Update: We are experiencing a service disruption. Our team was notified and they are investigating the issue. This page will be updated again as soon as we have more information about impact and scope.

Time: April 23, 2018, 2:02 p.m.

Status: Investigating

Update: We are experiencing a service disruption. Our team was notified and they are investigating the issue. This page will be updated again as soon as we have more information about impact and scope.