Maropost experienced a minor incident on August 17, 2026 affecting Control Panel, lasting 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 17, 2026, 05:38 AM UTC
We are receiving reports of control panels receiving "We will be back online shortly". Our Development Team are investigating now.
- identified Aug 17, 2026, 06:00 AM UTC
We have identified the issue and our Development Team is working to resolve it as soon as possible.
- monitoring Aug 17, 2026, 06:09 AM UTC
The issue has been resolved and services are operating as normal. Our team is closely monitoring the situation.
- resolved Aug 17, 2026, 06:32 AM UTC
The issue has been resolved and services are operating as normal.
- postmortem Aug 18, 2026, 12:07 AM 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.