Maropost experienced a critical incident on October 30, 2025 affecting Merchant Store Fronts and Control Panel, lasting 3h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 30, 2025, 06:35 AM UTC
We’re aware of an ongoing service interruption. Our engineering team is actively investigating the root cause and working to restore services as quickly as possible. We’re treating this as a top priority and will share updates as soon as they’re available.
- investigating Oct 30, 2025, 06:50 AM UTC
We are continuing to investigate this issue.
- identified Oct 30, 2025, 07:17 AM UTC
We have identified the issue, our team is working to resolve the issue as soon as possible. Please continue to refresh this page or subscribe for updates.
- identified Oct 30, 2025, 07:44 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 30, 2025, 07:49 AM UTC
We are receiving reports of services returning back to normal. We are continuing to monitor the situation.
- monitoring Oct 30, 2025, 07:50 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 30, 2025, 10:06 AM UTC
This incident has been resolved.
- postmortem Oct 30, 2025, 10:20 PM UTC
# **Neto service disruption: Thursday, 30 October 2025** ## Summary On Thursday, 30 October 2025, some Neto storefronts experienced errors and became temporarily unavailable. The issue was caused by an error during a routine maintenance change. Service was restored the same afternoon. ## Dates and times \(AEST\) * Start: ~4:23 pm AEST * Full restoration: ~5:50 pm AEST ## Impact * Some storefronts returned errors and checkout was unavailable during the incident window. ## What happened During routine maintenance, an incorrect build was deployed. This introduced a dependency mismatch which caused application errors. Once identified, the change was rolled back. ## ## What we are doing to prevent this in future * Tightening release controls to ensure test-only changes cannot be promoted into production * Separating configuration and build artefacts by environment * Adding extra pre-deployment validation to catch dependency mismatches before release ## Next steps * We will complete a full internal review of our release and change-management process and implement further guardrails as required. We know outages interrupt your business and we sincerely apologise for the impact. We will continue to make improvements to prevent a reoccurrence. If you have any issues or questions relating to this incident, please contact Support with “**Neto 30 Oct incident”** in the subject so we can prioritise your case.