Maropost incident

Control Panel and Webstore Disruption

Major Resolved View vendor source →

Maropost experienced a major incident on May 3, 2026 affecting Merchant Store Fronts and Control Panel, lasting 3h 57m. The incident has been resolved; the full update timeline is below.

Started
May 03, 2026, 11:55 PM UTC
Resolved
May 04, 2026, 03:52 AM UTC
Duration
3h 57m
Detected by Pingoru
May 03, 2026, 11:55 PM UTC

Affected components

Merchant Store FrontsControl Panel

Update timeline

  1. investigating May 03, 2026, 11:55 PM UTC

    We are receiving reports of sites receiving "We will be back online shortly". Our Development Team are investigating now.

  2. monitoring May 04, 2026, 12:04 AM UTC

    We are receiving reports that services are returning to normal. We are continuing to monitor the situation.

  3. monitoring May 04, 2026, 12:09 AM UTC

    Some sites may still show "We will be back online shortly" intermittently. Our Development Team is working to resolve the issue as soon as possible.

  4. resolved May 04, 2026, 03:52 AM UTC

    This incident has been resolved.

  5. postmortem May 06, 2026, 02:02 AM UTC

    ### Summary On 4 May 2026, some merchants experienced intermittent access issues with their webstores and Control Panel. During this time, some sites may have displayed a “We will be back online shortly” message. ### Impact The issue caused intermittent availability issues for some merchant webstores and Control Panel access. The impact was not consistent across all sites, and some requests may have succeeded while others failed. ### Root Cause The issue was caused by a sudden spike in automated crawler traffic, which created increased load on the caching layer. This prevented some new connections from being established and resulted in intermittent availability issues. ### Resolution The traffic pattern was identified, and mitigation was applied to reduce the impact of the abnormal traffic while maintaining access for legitimate crawler activity. ### Preventative Actions We have strengthened traffic protection rules to better manage sudden high-volume crawler activity. We are also continuing to monitor traffic patterns and refine platform protections to reduce the risk of similar disruptions.