Mailchimp's WooCommerce integration stopped connecting properly for 2h 44m on 10 November 2026, starting at 14:51 UTC. The fault sat on Mailchimp's side of that connection.
Started
14:51 UTC
Duration
Lasted 2h 44m
Source
IsDown
Next time
Mailchimp is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Mailchimp logged one incident on this day, titled "Issues connecting WooCommerce integration", starting at 14:51 UTC and running for 2h 44m. Mailchimp's own record carries no updates for this incident: no cause, no progress notes, no resolution message beyond the start and the eventual close. No components are listed as affected in the record, so there is no breakdown of which part of the integration pipeline was involved. No user reports were filed during the window, which is unusual for an incident of this length but is what the record shows. Mailchimp's status page is the only source here, and a single filing with no updates means you're relying on Mailchimp's word that the issue started and ended when they say it did, with no detail on severity or scope in between. Over the past 90 days Mailchimp has logged 8 incidents with a median duration of 3 hours 28 minutes, so this one ran shorter than typical for the service. Across all time, Mailchimp averages 2.4 incidents a month, putting this in line with a service that has recurring, if usually brief, trouble. There's no indication in the record of whether this was isolated to WooCommerce specifically or part of a wider integration problem, because nothing further was published.
Learning
This incident sat in the connection between Mailchimp and WooCommerce, a layer that your own uptime checks on your storefront would never touch, because your site can stay up and green while the sync between it and Mailchimp fails quietly in the background. That's the general shape of integration failures: your endpoint reports healthy, the third party's endpoint reports healthy, and the breakage happens in the handshake between the two, which neither side's self check is built to catch. Mailchimp's own status page is the only record of this one, with no updates explaining cause or scope, so you're left trusting a single filing. Over 30 days UptimeRobot recorded 4 incidents for Mailchimp with a median resolution time of 4h 8m, a different vantage point than Mailchimp's own 90 day median of 3h 28m, and that gap is worth noticing rather than reconciling away. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.