Skip to content

Outage tracker / Mailchimp

Is Mailchimp down?

I'm having a problem

Operationalchecked 14 minutes ago

We reached Mailchimp from all 10 regions we check.

As of Oct 5, 2026, 8:02 PM UTC, Mailchimp answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 32 min on Oct 4, 2026 (API, from US-Central).

our independent probeslive · checked Oct 5, 2026, 8:02 PM UTC
US-East386 msOperational
US-West652 msOperational
Europe723 msOperational
Asia-Pacific956 msOperational
US-Central145 msOperational
Canada586 msOperational
UK309 msOperational
Southeast Asia789 msOperational
Australia880 msOperational
South America1592 msOperational
their status pagetheir claim, not our reading

Mailchimp publishes no status feed we can read, so the only independent reading here is ours on the left.

Mailchimp response time, by region

US-East
552msp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 426ms2026-09-07 UTC: p95 447ms2026-09-08 UTC: p95 3.2s2026-09-09 UTC: p95 4.1s2026-09-10 UTC: p95 3.3s2026-09-11 UTC: p95 3.1s2026-09-12 UTC: p95 3.9s2026-09-13 UTC: p95 4.1s2026-09-14 UTC: p95 4.1s2026-09-15 UTC: p95 2.0s2026-09-16 UTC: p95 2.3s2026-09-17 UTC: p95 2.8s2026-09-18 UTC: p95 4.1s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 3.2s2026-09-21 UTC: p95 4.7s2026-09-22 UTC: p95 4.1s2026-09-23 UTC: p95 4.4s2026-09-24 UTC: p95 4.5s2026-09-25 UTC: p95 3.0s2026-09-26 UTC: p95 3.3s2026-09-27 UTC: p95 4.5s2026-09-28 UTC: p95 4.6s2026-09-29 UTC: p95 4.5s2026-09-30 UTC: p95 4.6s2026-10-01 UTC: p95 462ms2026-10-02 UTC: p95 493ms2026-10-03 UTC: p95 546ms2026-10-04 UTC: p95 439ms2026-10-05 UTC: p95 552ms
Sep 6Sep 20Oct 5
US-West
716msp95 · latest
10s5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 622ms2026-09-07 UTC: p95 643ms2026-09-08 UTC: p95 2.9s2026-09-09 UTC: p95 3.7s2026-09-10 UTC: p95 3.3s2026-09-11 UTC: p95 3.4s2026-09-12 UTC: p95 3.2s2026-09-13 UTC: p95 5.2s2026-09-14 UTC: p95 3.4s2026-09-15 UTC: p95 3.1s2026-09-16 UTC: p95 3.1s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 4.5s2026-09-19 UTC: p95 3.7s2026-09-20 UTC: p95 2.7s2026-09-21 UTC: p95 4.5s2026-09-22 UTC: p95 3.3s2026-09-23 UTC: p95 3.6s2026-09-24 UTC: p95 4.9s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 3.0s2026-09-27 UTC: p95 4.3s2026-09-28 UTC: p95 4.4s2026-09-29 UTC: p95 4.7s2026-09-30 UTC: p95 4.1s2026-10-01 UTC: p95 562ms2026-10-02 UTC: p95 550ms2026-10-03 UTC: p95 558ms2026-10-04 UTC: p95 562ms2026-10-05 UTC: p95 716ms
Sep 6Sep 20Oct 5
Europe
797msp95 · latest
10s5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 900ms2026-09-07 UTC: p95 989ms2026-09-08 UTC: p95 3.3s2026-09-09 UTC: p95 4.3s2026-09-10 UTC: p95 3.5s2026-09-11 UTC: p95 4.3s2026-09-12 UTC: p95 3.9s2026-09-13 UTC: p95 4.8s2026-09-14 UTC: p95 3.9s2026-09-15 UTC: p95 2.6s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 2.4s2026-09-18 UTC: p95 4.7s2026-09-19 UTC: p95 3.8s2026-09-20 UTC: p95 4.7s2026-09-21 UTC: p95 4.0s2026-09-22 UTC: p95 3.3s2026-09-23 UTC: p95 3.9s2026-09-24 UTC: p95 4.7s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 4.2s2026-09-28 UTC: p95 4.7s2026-09-29 UTC: p95 4.7s2026-09-30 UTC: p95 5.3s2026-10-01 UTC: p95 968ms2026-10-02 UTC: p95 950ms2026-10-03 UTC: p95 978ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 797ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.6sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 2.2s2026-09-08 UTC: p95 2.7s2026-09-09 UTC: p95 4.5s2026-09-10 UTC: p95 3.6s2026-09-11 UTC: p95 4.5s2026-09-12 UTC: p95 5.0s2026-09-13 UTC: p95 4.4s2026-09-14 UTC: p95 5.0s2026-09-15 UTC: p95 2.6s2026-09-16 UTC: p95 2.2s2026-09-17 UTC: p95 2.6s2026-09-18 UTC: p95 5.6s2026-09-19 UTC: p95 4.1s2026-09-20 UTC: p95 3.2s2026-09-21 UTC: p95 5.2s2026-09-22 UTC: p95 3.8s2026-09-23 UTC: p95 3.9s2026-09-24 UTC: p95 5.3s2026-09-25 UTC: p95 3.7s2026-09-26 UTC: p95 2.4s2026-09-27 UTC: p95 4.7s2026-09-28 UTC: p95 5.3s2026-09-29 UTC: p95 5.3s2026-09-30 UTC: p95 5.8s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.6s
Sep 6Sep 20Oct 5
US-Central
431msp95 · latest
10s5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 881ms2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 2.3s2026-09-09 UTC: p95 5.1s2026-09-10 UTC: p95 2.3s2026-09-11 UTC: p95 4.9s2026-09-12 UTC: p95 3.4s2026-09-13 UTC: p95 3.1s2026-09-14 UTC: p95 4.2s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 2.8s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 4.4s2026-09-19 UTC: p95 3.9s2026-09-20 UTC: p95 3.9s2026-09-21 UTC: p95 4.0s2026-09-22 UTC: p95 3.6s2026-09-23 UTC: p95 3.3s2026-09-24 UTC: p95 4.4s2026-09-25 UTC: p95 2.7s2026-09-26 UTC: p95 722ms2026-09-27 UTC: p95 2.6s2026-09-28 UTC: p95 4.3s2026-09-29 UTC: p95 4.3s2026-09-30 UTC: p95 5.0s2026-10-01 UTC: p95 564ms2026-10-02 UTC: p95 350ms2026-10-03 UTC: p95 555ms2026-10-04 UTC: p95 487ms2026-10-05 UTC: p95 431ms
Sep 6Sep 20Oct 5
Canada
621msp95 · latest
10s5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 655ms2026-09-07 UTC: p95 655ms2026-09-08 UTC: p95 4.3s2026-09-09 UTC: p95 3.5s2026-09-10 UTC: p95 4.2s2026-09-11 UTC: p95 3.8s2026-09-12 UTC: p95 3.0s2026-09-13 UTC: p95 4.2s2026-09-14 UTC: p95 4.6s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 2.1s2026-09-17 UTC: p95 2.1s2026-09-18 UTC: p95 4.5s2026-09-19 UTC: p95 3.5s2026-09-20 UTC: p95 2.0s2026-09-21 UTC: p95 5.0s2026-09-22 UTC: p95 3.7s2026-09-23 UTC: p95 4.0s2026-09-24 UTC: p95 4.5s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 2.3s2026-09-27 UTC: p95 4.1s2026-09-28 UTC: p95 3.9s2026-09-29 UTC: p95 4.9s2026-09-30 UTC: p95 4.7s2026-10-01 UTC: p95 665ms2026-10-02 UTC: p95 611ms2026-10-03 UTC: p95 459ms2026-10-04 UTC: p95 655ms2026-10-05 UTC: p95 621ms
Sep 6Sep 20Oct 5
UK
725msp95 · latest
10s5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 518ms2026-09-07 UTC: p95 379ms2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 3.4s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 3.9s2026-09-12 UTC: p95 3.4s2026-09-13 UTC: p95 3.9s2026-09-14 UTC: p95 3.0s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.9s2026-09-17 UTC: p95 2.7s2026-09-18 UTC: p95 4.2s2026-09-19 UTC: p95 3.8s2026-09-20 UTC: p95 4.7s2026-09-21 UTC: p95 4.8s2026-09-22 UTC: p95 3.0s2026-09-23 UTC: p95 4.0s2026-09-24 UTC: p95 4.6s2026-09-25 UTC: p95 2.6s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 2.9s2026-09-28 UTC: p95 5.1s2026-09-29 UTC: p95 4.3s2026-09-30 UTC: p95 3.9s2026-10-01 UTC: p95 741ms2026-10-02 UTC: p95 684ms2026-10-03 UTC: p95 750ms2026-10-04 UTC: p95 723ms2026-10-05 UTC: p95 725ms
Sep 6Sep 20Oct 5
Southeast Asia
1.5sp95 · latest
10s5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 3.8s2026-09-08 UTC: p95 2.8s2026-09-09 UTC: p95 4.8s2026-09-10 UTC: p95 2.2s2026-09-11 UTC: p95 4.8s2026-09-12 UTC: p95 5.0s2026-09-13 UTC: p95 5.7s2026-09-14 UTC: p95 4.0s2026-09-15 UTC: p95 3.5s2026-09-16 UTC: p95 2.6s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 5.5s2026-09-19 UTC: p95 2.6s2026-09-20 UTC: p95 4.5s2026-09-21 UTC: p95 4.9s2026-09-22 UTC: p95 3.9s2026-09-23 UTC: p95 5.7s2026-09-24 UTC: p95 6.3s2026-09-25 UTC: p95 2.2s2026-09-26 UTC: p95 3.3s2026-09-27 UTC: p95 5.1s2026-09-28 UTC: p95 5.7s2026-09-29 UTC: p95 5.7s2026-09-30 UTC: p95 5.5s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 2.3s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
Australia
1.3sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 2.7s2026-09-08 UTC: p95 2.5s2026-09-09 UTC: p95 4.2s2026-09-10 UTC: p95 3.7s2026-09-11 UTC: p95 5s2026-09-12 UTC: p95 4.6s2026-09-13 UTC: p95 4.6s2026-09-14 UTC: p95 5.1s2026-09-15 UTC: p95 3.0s2026-09-16 UTC: p95 3.3s2026-09-17 UTC: p95 2.1s2026-09-18 UTC: p95 5.5s2026-09-19 UTC: p95 3.6s2026-09-20 UTC: p95 4.2s2026-09-21 UTC: p95 6.3s2026-09-22 UTC: p95 5.8s2026-09-23 UTC: p95 3.5s2026-09-24 UTC: p95 4.1s2026-09-25 UTC: p95 4.2s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 3.9s2026-09-28 UTC: p95 5.1s2026-09-29 UTC: p95 5.4s2026-09-30 UTC: p95 4.4s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
South America
1.9sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 2.1s2026-09-09 UTC: p95 4.3s2026-09-10 UTC: p95 2.4s2026-09-11 UTC: p95 3.7s2026-09-12 UTC: p95 4.3s2026-09-13 UTC: p95 3.9s2026-09-14 UTC: p95 4.7s2026-09-15 UTC: p95 2.5s2026-09-16 UTC: p95 2.9s2026-09-17 UTC: p95 3.2s2026-09-18 UTC: p95 4.8s2026-09-19 UTC: p95 3.6s2026-09-20 UTC: p95 4.7s2026-09-21 UTC: p95 4.7s2026-09-22 UTC: p95 3.5s2026-09-23 UTC: p95 4.0s2026-09-24 UTC: p95 4.9s2026-09-25 UTC: p95 4.5s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 3.2s2026-09-28 UTC: p95 6.7s2026-09-29 UTC: p95 5.2s2026-09-30 UTC: p95 5.7s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.9s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.9s
Sep 6Sep 20Oct 5

Is it Mailchimp, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Mailchimp -- it cannot diagnose Mailchimp's own systems.

What we measured, function by function

Mailchimp answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Mailchimp go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Mailchimp, and again when they can reach it again. That is our own measurement from ten regions, not Mailchimp's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 386msstatus code: 401checked: Oct 5, 2026, 7:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Mailchimp normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 652msstatus code: 401checked: Oct 5, 2026, 7:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Mailchimp normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 145msstatus code: 401checked: Oct 5, 2026, 7:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Mailchimp normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 586msstatus code: 401checked: Oct 5, 2026, 7:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Mailchimp normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1592msstatus code: 401checked: Oct 5, 2026, 7:57 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Mailchimp normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 723msstatus code: 401checked: Oct 5, 2026, 7:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Mailchimp normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 309msstatus code: 401checked: Oct 5, 2026, 7:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Mailchimp normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 956msstatus code: 401checked: Oct 5, 2026, 7:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Mailchimp normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 789msstatus code: 401checked: Oct 5, 2026, 7:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Mailchimp normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 880msstatus code: 401checked: Oct 5, 2026, 8:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Mailchimp normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Mailchimp, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Mailchimp yet, which is not evidence that nothing is wrong.

Recent outages

Partial outage, 32mmeasured by our probes · US-Central2026-10-04

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Mailchimp since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Mailchimp covering any window you pick, with our measurements and Mailchimp's own claim at the time, side by side.

Full availability history for Mailchimp: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Mailchimp uptime measured by RealUptimeLive, from this page's own readings.
[![Mailchimp uptime measured by RealUptime](https://realuptime.io/outages/mailchimp/badge.svg?days=30)](https://realuptime.io/outages/mailchimp)
<a href="https://realuptime.io/outages/mailchimp"><img src="https://realuptime.io/outages/mailchimp/badge.svg?days=30" alt="Mailchimp uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Mailchimp's SLA implies, from our measurement

At or above your target

We measured none of downtime for Mailchimp over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

Separately, we measured 31 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Mailchimp's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.mailchimp.com/3.0/
secondary
https://status.mailchimp.com/
RealUptime is not affiliated with Mailchimp; the name identifies what we measured, and nothing here speaks for Mailchimp's own team. We send a single web request to Mailchimp from 10 regions on our own schedule and time the response. We do not see inside Mailchimp's systems, do not use an account or real transaction, and are not the same signal Mailchimp's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Mailchimp is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.