Neto by Maropost Incident History

1. postmortemAug 18 · 00:02 UTC

   ## What Happened Our investigation identified a significant increase in automated bot traffic targeting product filtering, category and search requests. This traffic placed additional load on parts of the Neto platform, resulting in short periods of degraded performance and intermittent 503 errors for some merchants and their customers. ## Resolution We introduced an **interim solution** by adding additional Cloudflare protections to identify and challenge this automated traffic before it reached the Neto platform. Following implementation of these protections on 13 August, platform performance stabilised and we did not observe further significant 503 spikes during the monitoring period. Some visitors may briefly see a **“Checking your connection”** message when accessing certain filtered product and category pages. This check completes automatically and is designed to prevent automated traffic from placing excessive load on the platform. ## Preventive Actions We are continuing to monitor traffic patterns, 503 errors and platform performance closely. We are also continuing to work with Cloudflare on improvements to bot detection so that changing automated traffic patterns can be identified and mitigated more effectively. We apologise for the disruption this incident caused and appreciate your patience while our teams worked to restore and improve platform stability.

Reported by Neto by Maropost on their status page.

1. postmortemAug 18 · 00:07 UTC

   ## What happened A feature configuration was enabled for some Neto stores before the corresponding application changes had completed deployment to the production environment. This created an unexpected state for those stores and prevented users from successfully loading the Control Panel after login. ## Impact Affected merchants were temporarily unable to access their Neto Control Panel. The issue was limited in scope, with no broader Neto platform disruption identified. ## Resolution Once the cause was identified, the feature configuration was disabled for the affected stores, restoring Control Panel access. Our teams then monitored the affected environments to confirm that Control Panel access and supporting services remained stable. ## Preventive actions To reduce the likelihood of this occurring again, we are strengthening the deployment process around feature configuration changes. This includes: * Verifying that the required application version has been fully deployed before enabling associated features. * Adding additional checks around deployment and configuration sequencing. * Performing validation and smoke testing immediately following feature activation. * Improving coordination and confirmation of production deployment status before configuration changes are rolled out. We apologise to the merchants affected by this disruption and appreciate their patience while our teams worked to restore access.

Reported by Neto by Maropost on their status page.