Resolved after 2 hours 33 minutes, affecting Merchant Store Fronts and Control Panel, on March 3, 2026.
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.
Affected components
Update timeline
- investigating Mar 03, 2026, 04:14 AM UTC
We are investigating reports of intermittent access issues affecting some merchant storefronts and the Control Panel. In some cases, pages may return a 503 error (for example, “We will be back online shortly”) and access may be inconsistent. Our team is working to identify the cause and will provide updates as we learn more.
- monitoring Mar 03, 2026, 05:06 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 03, 2026, 05:21 AM UTC
We are continuing to monitor for any further issues.
- resolved Mar 03, 2026, 06:47 AM UTC
This incident has been resolved.
- postmortem Mar 27, 2026, 03:28 AM UTC
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.
Your product runs on more than Maropost
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