Neto by Maropost Status Page

May 26, 2026 · resolved May 26

This incident has been resolved.

May 5, 2026 · resolved May 5

This incident has been resolved.

May 4, 2026 · resolved May 4

This incident has been resolved.

May 3, 2026 · resolved May 4

### 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.

Apr 29, 2026 · resolved Apr 30

### Summary On 30 April 2026, some merchants experienced intermittent disruption when accessing storefronts and the Control Panel. During the incident, some storefront pages may have intermittently displayed a “We’ll be back online shortly” message, while some Control Panel access may also have been affected. The incident was caused by a significant spike in automated traffic directed at the platform, which placed abnormal load on the caching and application layers. This resulted in intermittent availability and degraded performance for affected services. ### Root Cause The disruption was caused by a large volume of automated traffic targeting the platform. This traffic created abnormal load on the caching layer, which is used to support efficient delivery of storefront and Control Panel content. As traffic volumes increased, the caching and application layers became degraded, resulting in intermittent access issues for some merchants. ### Resolution Our teams identified the unusual traffic pattern and implemented targeted mitigation rules to reduce the impact of the automated traffic. Once the mitigation was applied, the caching and application layers stabilised, and services returned to normal. We continued monitoring after service recovery to ensure the platform remained stable. ### Preventative Actions To reduce the likelihood and impact of similar events in future, we have taken the following actions: * Strengthened traffic filtering and mitigation rules for abnormal request patterns. * Improved monitoring for sudden traffic spikes and automated traffic fingerprints. * Reviewed the traffic behaviour with our traffic protection provider to better identify similar patterns in future. * Continued tuning of platform protection rules to reduce the impact of high-volume automated traffic.