Resolved on June 4, 2025.
### **What Happened** On the morning of Jun 4th, our system experienced a period of degraded performance, followed by a temporary outage. This began when several routine tasks and increased user activity placed unexpected strain on our servers. As a result, the platform became slow and eventually unavailable for a short period. ### **What Caused It** The root cause was related to an increase in memory utilization on our web servers - the short-term "working space" our system needs to function. When that memory unexpectedly ran low, performance dropped sharply and some parts of the system stopped responding. This was not due to any malicious activity, but rather a combination of regular system tasks and higher-than-expected traffic happening at the same time. We restored service by upgrading our systems to add additional resources to support the unexpected load. This resolved the issue and brought the platform back online. ### **What We’re Doing to Prevent It** To make sure this doesn’t happen again, we’re taking several steps: * **Upgrading infrastructure** to better handle high demand. * **Improving how we schedule internal system tasks** to reduce the overall load on servers. * **Enhancing monitoring tools** so we can spot and address early warning signs faster. * **Reviewing system design** to increase efficiency and resilience under heavy load. ### **Looking Ahead** We’re very sorry for the disruption and the inconvenience it may have caused. Our team is committed to delivering a reliable, high-performing experience, and we appreciate your continued trust as we work to strengthen our systems.
Update timeline
- resolved Nov 25, 2025, 10:29 PM UTC
Issues with accessing the Loopio platform are subsiding, and our Support and Engineering Teams will continue to monitor the system's performance.
- postmortem Dec 10, 2025, 04:49 PM UTC
### **What Happened** On the morning of Jun 4th, our system experienced a period of degraded performance, followed by a temporary outage. This began when several routine tasks and increased user activity placed unexpected strain on our servers. As a result, the platform became slow and eventually unavailable for a short period. ### **What Caused It** The root cause was related to an increase in memory utilization on our web servers - the short-term "working space" our system needs to function. When that memory unexpectedly ran low, performance dropped sharply and some parts of the system stopped responding. This was not due to any malicious activity, but rather a combination of regular system tasks and higher-than-expected traffic happening at the same time. We restored service by upgrading our systems to add additional resources to support the unexpected load. This resolved the issue and brought the platform back online. ### **What We’re Doing to Prevent It** To make sure this doesn’t happen again, we’re taking several steps: * **Upgrading infrastructure** to better handle high demand. * **Improving how we schedule internal system tasks** to reduce the overall load on servers. * **Enhancing monitoring tools** so we can spot and address early warning signs faster. * **Reviewing system design** to increase efficiency and resilience under heavy load. ### **Looking Ahead** We’re very sorry for the disruption and the inconvenience it may have caused. Our team is committed to delivering a reliable, high-performing experience, and we appreciate your continued trust as we work to strengthen our systems.
Your product runs on more than Loopio
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services