Mailchimp favicon

Mailchimp outage on 2026-10-28

mailchimp.com
October 2026 28 Major incident

Mailchimp had an outage lasting 5h 32m starting at 12:57 UTC on 28 October 2026, titled "Access Issues and Errors Across Mailchimp" on its status page. The fault sat with Mailchimp, not with anything in your own setup.

Started

12:57 UTC

Duration

Lasted 5h 32m

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's status page logged one incident on this day, called "Access Issues and Errors Across Mailchimp", starting at 12:57 UTC and running for 5h 32m before it was marked resolved. Mailchimp did not publish any updates against this incident, so there is no record of what broke inside Mailchimp's systems, which users were affected, or when the problem was first noticed internally. No components are listed as affected on the status page for this incident. No user reports were filed in the window covered by this page, so there is no first-hand account to set alongside the vendor's own title. The title itself, "Access Issues and Errors Across Mailchimp", points at login or general access problems and errors across the product, but with zero updates published, that single line is the only thing on the record. Mailchimp's status page history shows this is not a one-off: in the past 90 days there have been 8 incidents with a median duration of 4 hours 21 minutes, and across all time Mailchimp has logged 156 incidents at a rate of roughly 2.4 per month. This incident's 5h 32m duration is close to that 90-day median, so it falls within the pattern Mailchimp has shown recently rather than standing out as unusual. Because Mailchimp filed no updates, you are left with the start time, the end time, and the title, and nothing that explains cause or scope in between.

Learning

UptimeRobot's own 30-day checks on Mailchimp recorded 2 incidents, both resolved, with a median duration of 76h 26m, a much longer figure than the 5h 32m Mailchimp reported for this one. That gap exists because external uptime checks and a vendor's own incident log measure different things: a check from outside can keep failing, or keep passing, independently of what a provider's internal dashboard calls open or closed. If your own monitoring stayed green through this window, that simply means your half of the connection, your integration, your API calls, your webhooks, kept behaving the way you configured them to behave, while the fault sat inside Mailchimp's infrastructure where your probes never look. Access issues of the kind Mailchimp titled this incident typically live in authentication or routing layers that sit behind the parts you can reach from outside, which is exactly why pinging your own endpoints would not have surfaced it. The practical shape of this kind of failure is that your product can look fine from your side while people trying to reach Mailchimp features hit errors that have nothing to do with your code. Your monitoring covers your half of that connection. UptimeRobot now watches the provider's half too, so next time something breaks you know which side it was without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.