Maropost Outage History
Maropost is up right nowPingoru has recorded 52 incidents for Maropost: 39 in the last 12 months and 10 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 6 | 147 of 720 (20%) |
| May 2026 | 5 | 18 of 744 (2%) |
| June 2026 | 1 | 3 of 720 (0%) |
| July 2026 | 7 | 15 of 744 (2%) |
| August 2026 | 3 | 125 of 744 (17%) |
| September 2026 | 1 | 0 of 720 (0%) |
| October 2026 | 6 | 15 of 589 (3%) |
Incidents, newest first
Minor March 3, 2026 Intermittent 503 errors and access issues 2h 33m Merchant Store Fronts, Control Panel
Started Mar 03, 2026, 04:14 AM UTC· resolved Mar 03, 2026, 06:47 AM UTC
- investigating Mar 03, 2026, 04:14 AM UTC
We are investigating reports of intermittent access issues affecting some merchant storefronts and the Control Panel. In some cases, pages may return a 503 error (for example, “We will be back online shortly”) and access may be inconsistent. Our team is working to identify the cause and will provide updates as we learn more.
- monitoring Mar 03, 2026, 05:06 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 03, 2026, 05:21 AM UTC
We are continuing to monitor for any further issues.
- resolved Mar 03, 2026, 06:47 AM UTC
This incident has been resolved.
- postmortem Mar 27, 2026, 03:28 AM UTC
During March 2026, we experienced three intermittent service incidents caused by non-legitimate automated traffic targeting storefronts. These events occurred on **3 March**, **9 March**, and **17 to 18 March 2026**, and resulted in temporary slowness, intermittent availability issues, and in some cases **“We will be back shortly”** messages. The underlying cause was evolving bot traffic patterns that were not fully addressed by the existing protection controls in place at the time. We implemented a series of mitigation changes across the incidents, including refined bot protection, stronger request limiting, and additional filtering for suspicious traffic. Since these changes were applied, we have continued to improve our protections and monitoring to reduce the risk of recurrence and strengthen platform reliability.
Minor January 23, 2026 Third-party email delivery delays (Microsoft Outlook) 3h 24m Upstream Provider
Started Jan 23, 2026, 04:15 AM UTC· resolved Jan 23, 2026, 07:40 AM UTC
- monitoring Jan 23, 2026, 04:15 AM UTC
We’re aware of delays delivering system emails (order confirmations, password resets, notifications) to Microsoft-hosted email services such as Outlook and Office 365. Neto systems are operating normally. This issue is caused by degraded services on Microsoft’s side, which is impacting email delivery retries across multiple platforms. Emails are generally delayed rather than lost. We are monitoring the situation and will update once Microsoft confirms resolution.
- resolved Jan 23, 2026, 07:40 AM UTC
Microsoft has confirmed that services are now operating normally: https://status.cloud.microsoft/ Neto systems remained fully operational throughout this period, and email delivery is returning to normal.
Notice January 14, 2026 Unable to Log In to Control Panel 10m Control Panel
Started Jan 14, 2026, 04:51 AM UTC· resolved Jan 14, 2026, 05:02 AM UTC
- investigating Jan 14, 2026, 04:51 AM UTC
We are currently investigating this issue.
- monitoring Jan 14, 2026, 04:52 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jan 14, 2026, 04:57 AM UTC
We are continuing to monitor for any further issues.
- resolved Jan 14, 2026, 05:02 AM UTC
This incident has been resolved.
Notice January 7, 2026 Intermittent 503 errors on merchant webstores 2h 30m
Started Jan 07, 2026, 12:00 AM UTC· resolved Jan 07, 2026, 02:30 AM UTC
- resolved Jan 08, 2026, 12:20 AM UTC
Some merchants experienced intermittent website access issues, where pages returned a 503 error (for example “We will be back online shortly”), and in some cases inconsistent access to cPanel. The issue was intermittent, which meant some refreshes worked while others failed.
- postmortem Jan 08, 2026, 12:20 AM UTC
**Incident:** Intermittent 503 errors on merchant webstores **Date:** Tuesday, 7 January 2026 \(AEST\) **Severity:** P1 \(High\) CCP-Multiple sites reporting pa… ### What happened On the morning of 7 January 2026, some merchants experienced intermittent website access issues, where pages returned a **503 error** \(for example “We will be back online shortly”\), and in some cases inconsistent access to cPanel. The issue was intermittent, which meant some refreshes worked while others failed. ### Customer impact * **Impacted services:** Merchant webstores \(and intermittent access issues reported for cPanel\) * **Symptom:** Pages timing out and returning 503 errors * **Duration:** Approximately **10:00 AM to 12:30 PM AEST** \(around 2.5 hours\) * **Scope:** Multiple merchants across the platform CCP-Multiple sites reporting pa… ### Timeline \(AEST\) * **10:00 AM:** Incident begins, reports of 503 errors start coming in * **Morning:** Team investigates platform performance and confirms the issue is intermittent * **Around 12:15 PM:** 503 errors are no longer observed in edge logging \(stabilising\) * **12:30 PM:** Service considered resolved C ### Root cause \(plain English\) The incident was caused by a problem affecting **one instance within a cache layer** in the production stack. Backend threads on that cache instance increased and did not scale down as expected, which led to resource saturation and contributed to the observed 503 errors. Contributing factor: an **automated daily process** that refreshes/replaces instances \(to prevent backend threads from continually increasing\) **failed on the day**, which allowed older instances to keep running instead of being replaced. ### Resolution To restore service, we **rolled out new cache layer instances**, which resolved the abnormal backend thread behaviour and returned webstore responsiveness to normal. ### What we are doing to prevent this happening again We are strengthening detection and recovery around the rollout process, including: * Enhancing alerting so that if tests fail during instance rollout, notifications are raised to operational channels * Improving safeguards around the daily refresh pipeline to reduce the chance of older instances remaining active when they should be replaced. ### What merchants need to do No action is required. If you continue to experience intermittent 503 errors after **12:30 PM AEST on 7 January 2026**, please contact Support via [https://share.hsforms.com/1PF2VNMWnS2al3GnLh8msNQrp8ms](https://share.hsforms.com/1PF2VNMWnS2al3GnLh8msNQrp8ms) with: * Your store URL * Approximate time of occurrence \(including timezone\) * Any screenshots or error messages ### Apology We apologise for the disruption and any impact this may have had on your trading. Thank you for your patience while we investigated and resolved the issue.
Notice December 5, 2025 Neto service disruption 27m Merchant Store Fronts
Started Dec 05, 2025, 09:11 AM UTC· resolved Dec 05, 2025, 09:38 AM UTC
- investigating Dec 05, 2025, 09:11 AM UTC
We are currently investigating this issue.
- monitoring Dec 05, 2025, 09:13 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 05, 2025, 09:28 AM UTC
We experienced a brief outage earlier today that affected the accessibility of websites. This issue was caused by a widespread Cloudflare service disruption, which temporarily impacted network traffic and routing. Cloudflare has since resolved the incident, and all services are now fully operational. Our monitoring confirms that Neto sites are functioning normally again. We apologise for the inconvenience and appreciate your patience.
- resolved Dec 05, 2025, 09:38 AM UTC
This incident has been resolved.
Minor August 6, 2025 Shipping and Tracking API Degradation - Australia Post 1h 1m Carrier Labelling Integrations
Started Aug 06, 2025, 03:25 AM UTC· resolved Aug 06, 2025, 04:27 AM UTC
- investigating Aug 06, 2025, 03:25 AM UTC
Australia Post is currently experiencing intermittent technical issues affecting lodgement, pricing, and label printing services, and their team is working to resolve them. You can monitor the incident directly on their status page here: https://status.developers.auspost.com.au/incidents/lhqbdldvj8yt
- monitoring Aug 06, 2025, 03:52 AM UTC
Australia Post has implemented a fix and they are monitoring the results.
- resolved Aug 06, 2025, 04:27 AM UTC
Australia Post has marked the incident as resolved.
Major May 8, 2025 Intermittent Slowness - Control Panel and Web Store 4h 43m Merchant Store Fronts, Control Panel
Started May 08, 2025, 01:22 AM UTC· resolved May 08, 2025, 06:05 AM UTC
- investigating May 08, 2025, 01:22 AM UTC
We have received reports of intermittent slowness affecting the control panel and website for some merchants, leading to timeout errors. Our Development Team is actively investigating the issue.
- identified May 08, 2025, 01:32 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 08, 2025, 04:22 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 08, 2025, 06:05 AM UTC
This incident has been resolved.
Major March 26, 2025 Maropost Commerce Disruption 4h 31m Merchant Store Fronts, Control Panel
Started Mar 26, 2025, 01:21 AM UTC· resolved Mar 26, 2025, 05:53 AM UTC
- investigating Mar 26, 2025, 01:21 AM UTC
We have received reports of "We will be back shortly" messages affecting the control panel and website for some merchants. Our Development Team is actively investigating the issue.
- investigating Mar 26, 2025, 01:59 AM UTC
We are continuing to investigate issues related to sales order and inventory pages in the control panel not loading correctly.
- monitoring Mar 26, 2025, 04:40 AM UTC
Services have returned to normal, and we are actively monitoring the situation. However, we are continuing to investigate an issue affecting SFTP access for some users.
- resolved Mar 26, 2025, 05:53 AM UTC
All services are now running normally. We will continue to monitor the situation.
Minor December 11, 2024 Degraded performance on batch processing 1h 12m Batch Processing
Started Dec 11, 2024, 07:37 AM UTC· resolved Dec 11, 2024, 08:49 AM UTC
- investigating Dec 11, 2024, 07:37 AM UTC
Our engineers are investigating an issue with automated batch processing which may cause degraded performance.
- monitoring Dec 11, 2024, 08:25 AM UTC
Our automated batch processing is returning to normal. Our engineers are continuing to monitor.
- resolved Dec 11, 2024, 08:49 AM UTC
This incident is resolved. Batch processing automation back to normal operation.
Minor December 3, 2024 Intermittent Slowness and Degraded Performance - Control Panel and Web Store 3h 48m Merchant Store Fronts, Control Panel
Started Dec 03, 2024, 10:52 PM UTC· resolved Dec 04, 2024, 02:41 AM UTC
- investigating Dec 03, 2024, 10:52 PM UTC
We are receiving reports that some merchants are experiencing intermittent issues with control panel and website slowness and displaying a message, "We'll be back online shortly". Our Development Team are investigating now.
- identified Dec 04, 2024, 12:22 AM UTC
We have identified the issue, and our Development Team is actively working on a fix.
- monitoring Dec 04, 2024, 12:45 AM UTC
Our team has deployed a fix and is closely monitoring the situation to ensure performance returns to optimal levels. If you continue to experience any issues, please reach out to our support team.
- resolved Dec 04, 2024, 02:41 AM UTC
The issue has been resolved, and services are operating as normal. We are continuing to monitor the situation.