Loopio experienced a notice incident on March 6, 2025, lasting 2h. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Nov 25, 2025, 10:31 PM UTC
Issues with accessing the Loopio platform are subsiding, and our Support and Engineering Teams will continue to monitor the system's performance. Our Engineering Team will continue to monitor our system for any changes to performance.
- postmortem Dec 10, 2025, 04:48 PM UTC
On March 6th, 2025 at 7:49 am EDT the Loopio platform experienced an issue with its infrastructure that caused a service disruption primarily impacting search requests in the platform for approximately 2 hours. During this time, certain search requests may have failed or users may have experienced intermittent errors performing search requests in the platform. The interruption was caused by an unanticipated issue that was identified as high CPU utilization triggered by an upgrade of our OpenSearch AWS cluster. This high CPU usage resulted in a backlog of requests and a cascading increase in web requests, ultimately leading to HTTP 500 errors \(internal server errors\) for many users. The immediate resolution involved scaling down indexing operations to reduce the load on the system, while in parallel increasing the instance sizes within our OpenSearch cluster, which introduced stability to the platform. We are conducting a full investigation into the root cause of this issue. This will allow us to evaluate how to prevent problems like this in the future, and minimize the length of time a failure like this affects our customers. The Loopio team values transparency when it comes to any production issue. Your trust and confidence in Loopio is extremely important to us. If you have any questions, please don't hesitate to contact our support team.