Mailchimp service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for mailchimp.com. Compare the regional responses with the problem you see in Mailchimp.
Find Mailchimp help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Mailchimp sign-in, audience imports, campaign scheduling and delivery are different stages.
The checker above requests mailchimp.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Mailchimp action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse work app checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Select campaign, import or account help and preserve job state before retrying.
Open the website in your browser and compare it with the result above.
Open Mailchimp help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Account/campaign/job identifier, scheduled time, failed stage and error; keep subscriber data private.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Mailchimp.
These are troubleshooting comparisons, not claims that Mailchimp is currently experiencing a particular incident.
Check the campaign or import job state before submitting another send or import.
Compare the corresponding status information and inspect any validation or bounce report; a content/recipient error is not proof of platform downtime.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Mailchimp seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open mailchimp.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Mailchimp issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Mailchimp support.
Run the mailchimp.com check and compare its original timestamps and responses with your actual error. Mailchimp sign-in, audience imports, campaign scheduling and delivery are different stages.
Use the community buttons on this page to share whether the service works for you. For help from Mailchimp, use the official help/reporting resource linked above. Select campaign, import or account help and preserve job state before retrying.
Check the campaign or import job state before submitting another send or import. Compare the corresponding status information and inspect any validation or bounce report; a content/recipient error is not proof of platform downtime.
Account/campaign/job identifier, scheduled time, failed stage and error; keep subscriber data private.