Neto by Maropost Status Page

Aug 17, 2026 · resolved Aug 17

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

Aug 11, 2026 · resolved Aug 17

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

Aug 3, 2026 · resolved Aug 3

On Aug 4, 2026 through Aug 6, 2026, some customers experienced intermittent slowness and errors across parts of the system during several short periods. Our team identified elevated traffic and processing load as the cause, reduced the load, and restored stable performance. The incidents were caused by a large increase of sophisticated bots that Cloudflare miscategorized and treated as human traffic. The issue is resolved and we continue to monitor the system. We are collaborating with Cloudflare to improve detection of these requests and reduce their impact going forward.

Jul 27, 2026 · resolved Jul 27

On 27 July 2026, a subset of merchants experienced an issue accessing their control panels. Affected users were shown a “We will be back online shortly” message after attempting to log in. The incident began at **11:48 AM AEST** and was resolved at **1:17 PM AEST**, for a total duration of **1 hour and 29 minutes**. ## What happened During a production software release, a change affecting a security-related control panel configuration caused authenticated requests to fail for a subset of control panels. The issue only affected control panels where the relevant security feature was enabled. Users could reach the login page, but after authentication they were unable to access the control panel. ## Impact Some merchants were temporarily unable to access their control panels and complete administrative tasks. The disruption was limited to a subset of control panels. Services returned to normal once the affected configuration was disabled. ## Timeline * **11:48 AM AEST** – Reports were received of control panels displaying “We will be back online shortly,” and the Development Team began investigating. * **12:35 PM AEST** – The cause of the issue was identified and remediation work began. * **12:55 PM AEST** – A fix was deployed and the service was placed under monitoring. * **1:17 PM AEST** – The issue was confirmed as resolved and services were operating normally. ## Root cause A change included in the production release caused an incorrect security reporting configuration to be generated for affected control panels. This produced a response header that exceeded the supported size limit, causing authenticated control panel requests to fail. ## Resolution The affected security feature was disabled, immediately restoring access to impacted control panels. A permanent code correction is also being implemented so the feature can operate without generating the invalid configuration. ## Preventive actions To reduce the likelihood of a similar incident, we are: * Adding regression coverage for authenticated control panel access when security-reporting features are enabled. * Expanding staging validation for response-header size and security configuration changes. * Improving release checks for feature-toggle combinations before production deployment. * Implementing the permanent code correction and validating it before re-enabling the affected feature. We apologise for the disruption and appreciate the patience of affected merchants while our teams worked to restore access.

Jul 24, 2026 · resolved Jul 24

On Jul 24, 2026, some customers experienced intermittent slowness across parts of the service during two short periods. Our team identified elevated traffic and processing load as the cause, took action to reduce the load, and restored stable performance. The issue is now resolved and we are continuing to monitor closely. We are taking steps to improve resilience and help prevent similar issues from recurring.

Is Neto by Maropost down right now?

No — Neto by Maropost is up. All systems operational as of Aug 19, 10:45 PM UTC.

What is Neto by Maropost's current status?

Neto by Maropost: All Systems Operational. Alert24 checks Neto by Maropost's status page continuously and can notify you the moment it changes.

How do I get alerted when Neto by Maropost goes down?

Alert24 monitors Neto by Maropost and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.