Skip to content

Outage tracker / Mailchimp

Is Mailchimp down?

I'm having a problem

Partially degradedchecked 2 minutes ago

Mailchimp is answering our probes, but its web surface is running at least 0.6x its 7-day median from UK, Asia-Pacific, US-Central, Southeast Asia, US-West and Australia. Everything else we check answered at its usual speed.

As of Oct 19, 2026, 8:53 PM UTC, RealUptime's checks of Mailchimp passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Mailchimp did not fail from two or more distant regions in the 60 days we have checked it (since Aug 20, 2026). This does not show Mailchimp works for users.

our check readinglive · checked Oct 19, 2026, 8:53 PM UTC
US-East789 msChecks passing
US-West1155 msPartially degraded
Europe955 msChecks passing
Asia-Pacific1728 msPartially degraded
US-Central1151 msPartially degraded
Canada266 msChecks passing
UK638 msPartially degraded
Southeast Asia2273 msPartially degraded
Australia1301 msPartially degraded
South America1732 msChecks passing
their status pagetheir claim, not our reading

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

Mailchimp response time, by region

US-East
1.1sp95 · 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-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 529ms2026-10-06 UTC: p95 598ms2026-10-07 UTC: p95 523ms2026-10-08 UTC: p95 465ms2026-10-09 UTC: p95 450ms2026-10-10 UTC: p95 444ms2026-10-11 UTC: p95 433ms2026-10-12 UTC: p95 424ms2026-10-13 UTC: p95 485ms2026-10-14 UTC: p95 538ms2026-10-15 UTC: p95 566ms2026-10-16 UTC: p95 571ms2026-10-17 UTC: p95 904ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
US-West
1.4sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 841ms2026-10-06 UTC: p95 679ms2026-10-07 UTC: p95 681ms2026-10-08 UTC: p95 684ms2026-10-09 UTC: p95 603ms2026-10-10 UTC: p95 575ms2026-10-11 UTC: p95 687ms2026-10-12 UTC: p95 707ms2026-10-13 UTC: p95 676ms2026-10-14 UTC: p95 717ms2026-10-15 UTC: p95 711ms2026-10-16 UTC: p95 797ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19
Europe
1.2sp95 · 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-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 789ms2026-10-06 UTC: p95 885ms2026-10-07 UTC: p95 729ms2026-10-08 UTC: p95 821ms2026-10-09 UTC: p95 856ms2026-10-10 UTC: p95 822ms2026-10-11 UTC: p95 822ms2026-10-12 UTC: p95 904ms2026-10-13 UTC: p95 876ms2026-10-14 UTC: p95 846ms2026-10-15 UTC: p95 826ms2026-10-16 UTC: p95 742ms2026-10-17 UTC: p95 954ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
Asia-Pacific
2.2sp95 · 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-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.5s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 902ms2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.9s2026-10-16 UTC: p95 928ms2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.2s
Sep 20Oct 4Oct 19
US-Central
1.3sp95 · 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-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 426ms2026-10-06 UTC: p95 573ms2026-10-07 UTC: p95 288ms2026-10-08 UTC: p95 335ms2026-10-09 UTC: p95 417ms2026-10-10 UTC: p95 582ms2026-10-11 UTC: p95 411ms2026-10-12 UTC: p95 438ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 382ms2026-10-15 UTC: p95 496ms2026-10-16 UTC: p95 610ms2026-10-17 UTC: p95 975ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
Canada
310msp95 · 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-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 611ms2026-10-06 UTC: p95 933ms2026-10-07 UTC: p95 681ms2026-10-08 UTC: p95 475ms2026-10-09 UTC: p95 562ms2026-10-10 UTC: p95 450ms2026-10-11 UTC: p95 481ms2026-10-12 UTC: p95 607ms2026-10-13 UTC: p95 355ms2026-10-14 UTC: p95 461ms2026-10-15 UTC: p95 421ms2026-10-16 UTC: p95 417ms2026-10-17 UTC: p95 295ms2026-10-18 UTC: p95 823ms2026-10-19 UTC: p95 310ms
Sep 20Oct 4Oct 19
UK
881msp95 · 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-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 723ms2026-10-06 UTC: p95 707ms2026-10-07 UTC: p95 618ms2026-10-08 UTC: p95 759ms2026-10-09 UTC: p95 630ms2026-10-10 UTC: p95 722ms2026-10-11 UTC: p95 622ms2026-10-12 UTC: p95 720ms2026-10-13 UTC: p95 611ms2026-10-14 UTC: p95 551ms2026-10-15 UTC: p95 524ms2026-10-16 UTC: p95 502ms2026-10-17 UTC: p95 814ms2026-10-18 UTC: p95 918ms2026-10-19 UTC: p95 881ms
Sep 20Oct 4Oct 19
Southeast Asia
2.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-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.6s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.5s
Sep 20Oct 4Oct 19
Australia
1.4sp95 · 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-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.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s
Sep 20Oct 4Oct 19
South America
1.8sp95 · 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-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.6s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 4.3s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.8s
Sep 20Oct 4Oct 19

Check your own site while you wait on Mailchimp

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: Checks passingUS-West: Degraded Answering, but 3.4x slower than its 7-day median.Europe: Checks passingAsia-Pacific: Degraded Answering, but 1.4x slower than its 7-day median.US-Central: Degraded Answering, but 4.8x slower than its 7-day median.Canada: Checks passingUK: Degraded Answering, but 7.1x slower than its 7-day median.Southeast Asia: Degraded Answering, but 0.6x slower than its 7-day median.Australia: Degraded Answering, but 3.7x slower than its 7-day median.South America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Mailchimp fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Mailchimp fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Mailchimp's official status.

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 our checks show, and what people reported

  • North America
    Partially degradedUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 789msstatus code: 401checked: Oct 19, 2026, 8:43 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
      Partially degradedlatency: 1155msstatus code: 401checked: Oct 19, 2026, 8:52 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
      Partially degradedlatency: 1151msstatus code: 401checked: Oct 19, 2026, 8:51 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
      Checks passinglatency: 266msstatus code: 401checked: Oct 19, 2026, 8:41 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
    Checks passinglatency: 1732msstatus code: 401checked: Oct 19, 2026, 8:08 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
    Partially degradedEurope, UK
    • Europe
      Checks passinglatency: 955msstatus code: 401checked: Oct 19, 2026, 8:53 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
      Partially degradedlatency: 638msstatus code: 401checked: Oct 19, 2026, 8:01 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
    Partially degradedAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Partially degradedlatency: 1728msstatus code: 401checked: Oct 19, 2026, 8:50 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
      Partially degradedlatency: 2273msstatus code: 401checked: Oct 19, 2026, 8:38 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
      Partially degradedlatency: 1301msstatus code: 401checked: Oct 19, 2026, 8:12 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 probe events

No probe events on record yet for Mailchimp.

check 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 check readings and Mailchimp's own claim at the time, side by side.

Full check history for Mailchimp: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Mailchimp uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Mailchimp down?", https://realuptime.io/outages/mailchimp. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Mailchimp's stated SLA

At or above your target

Our checks of Mailchimp failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.mailchimp.com

RealUptime is not affiliated with Mailchimp; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.