Mailchimp sending was disrupted for 6h 57m on 13 November 2026, starting at 15:31 UTC. The incident title names Microsoft as the cause of the sending problems, placing the fault outside Mailchimp's own systems.
Started
15:31 UTC
Duration
Lasted 6h 57m
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 "Microsoft Outage Currently Affecting Some Mailchimp Sending". It started at 15:31 UTC and ran for 6h 57m before resolution. Mailchimp's status page recorded no updates during that window, so there is no timestamped account of what was tried or what changed before it cleared. No components are listed as affected on the record, and no user reports were filed during the window. The title itself is the only detail Mailchimp published: it attributes the disruption to a Microsoft outage affecting some of Mailchimp's sending capability, without further explanation of scope or which accounts were hit. One filing with no follow-up updates is thin evidence to build a full picture from, but it is what Mailchimp put on record for this incident. Over the past 90 days Mailchimp has logged 9 incidents with a median duration of 4 hours 12 minutes, so this one ran longer than typical for the service. Across all time Mailchimp has recorded 159 incidents, averaging 2.4 per month. No post-mortem has been published explaining why the Microsoft-side issue affected Mailchimp sending or what was done to resolve it.
Learning
UptimeRobot's own 30 day monitoring of Mailchimp recorded 5 incidents, all resolved, with a median duration of 5h 32m, a figure closer to this incident's length than the 90 day median on Mailchimp's own page. Sending failures that trace back to a dependency like Microsoft often will not show up as a dead front end or a failed login page, because the part you can see from outside may keep responding normally while mail simply does not go out. That is the general shape of this kind of fault: the layer that broke sits behind the interface, in the delivery pipeline, where an external check watching your own site has no visibility at all. If your product relies on Mailchimp for transactional or marketing email, an uptime check against your own endpoints would have stayed green throughout this 6h 57m window while mail silently failed to send. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.