Maropost incident

Service Disruption for Control Panels and Storefronts

Critical Resolved View vendor source →

Maropost experienced a critical incident on July 8, 2026 affecting Merchant Store Fronts and Control Panel, lasting 1h 36m. The incident has been resolved; the full update timeline is below.

Started
Jul 08, 2026, 05:00 PM UTC
Resolved
Jul 08, 2026, 06:36 PM UTC
Duration
1h 36m
Detected by Pingoru
Jul 08, 2026, 05:00 PM UTC

Affected components

Merchant Store FrontsControl Panel

Update timeline

  1. investigating Jul 08, 2026, 05:00 PM UTC

    We are experiencing a service disruption for the Neto Control Panel and Storefronts. We are investigating the solution and will post an update as soon as possible.

  2. identified Jul 08, 2026, 05:21 PM UTC

    We have identified the issue and have traced to a corruption in the Network File System. We have made the appropriate corrections and the system has begun recovering.

  3. monitoring Jul 08, 2026, 05:38 PM UTC

    The fix to the Network File System is resolved and service is restored. We are continuing to monitor the platform to ensure its availability and stability.

  4. resolved Jul 08, 2026, 06:36 PM UTC

    On 8 July 2026, we experienced an infrastructure issue that affected all Neto merchant webstores and cPanels for approximately 1 hour and 30 minutes. The incident was caused by a failure within our shared file system infrastructure, which prevented critical services from accessing the files required to serve websites and cPanels. As a result, the platform automatically blocked new requests to protect data consistency, leading to service disruption across all Neto stacks. Our engineering team responded immediately by restoring the affected file system services, failing over to a healthy infrastructure instance, and replacing impacted virtual machines. Once these recovery actions were completed, all webstores and cPanels were restored to normal operation. We are continuing our investigation to determine the underlying reason for the file system process failure. Based on our findings, we will implement additional monitoring and alerting, along with any necessary infrastructure improvements, to help detect and prevent similar incidents in the future.