Maropost Outage History

**Summary:** A temporary service disruption impacted storefront and cPanel availability. During this period’s, some requests could not be served, resulting in degraded platform performance. **Root Cause:** A configuration change within storefront template logic introduced inefficient processing behaviour, which caused excessive CPU and memory consumption. This led to elevated load on the caching layer and prevented the platform from serving incoming requests during the incident window. **Resolution:** The affected configuration was identified and reverted, which reduced system load and restored normal service shortly after.

We experienced a temporary service disruption that affected site availability. Early findings show that some application instances became unhealthy, which placed increased pressure on the caching layer and prevented new connections from being established. The issue has been mitigated, and services are currently stable. Our engineering team is continuing a deeper investigation to identify the root cause, including reviewing application logs and system behavior. This is not yet the final summary, and further analysis is ongoing

During March 2026, we experienced three intermittent service incidents caused by non-legitimate automated traffic targeting storefronts. These events occurred on **3 March**, **9 March**, and **17 to 18 March 2026**, and resulted in temporary slowness, intermittent availability issues, and in some cases **“We will be back shortly”** messages. The underlying cause was evolving bot traffic patterns that were not fully addressed by the existing protection controls in place at the time. We implemented a series of mitigation changes across the incidents, including refined bot protection, stronger request limiting, and additional filtering for suspicious traffic. Since these changes were applied, we have continued to improve our protections and monitoring to reduce the risk of recurrence and strengthen platform reliability.