# Is Constant Contact Down? The Status Page Is Readable, So We Counted All 50 Published Incidents

> How to tell whether Constant Contact is down: 24 named components, 50 published incidents over 28 months, a 2.1-hour median resolution, and four things that look like an outage and are not.

_Source: https://professionalstoolkit.com/articles/is-constant-contact-down — The Professional's Toolkit · updated 2026-10-08_

---


At the time of writing, no. The vendor's own status page reports "All Systems Operational" across
24 named components, with no open incidents and no scheduled maintenance [19].

That is the ten-second answer, and it is worth more than it sounds, because this is one of the
few products in this category whose status page can actually be read. We measured Klaviyo's
equivalent at zero characters of readable text; this one publishes a component list, a live
indicator and a dated incident history anyone can count. So rather than guess, this article
counts it.

## How to check in ten seconds, and what to look at

The page is at status.constantcontact.com, and it serves a readable indicator rather than an
application you have to wait for. Three things on it are worth knowing how to read.

The headline indicator is a single phrase. "All Systems Operational" is the clear state [19];
anything else names the affected component.

The component list is the useful part, because *down* is almost never all-or-nothing here. The
24 components are granular enough to tell you whether your actual problem is covered: Email
Campaigns, Contact Management, SMS Management, Event Campaigns, Email Automation, Segments, SMS
Sending, Login, Survey Creation, Landing Pages, Social Media, Action Blocks, Reporting, API's and
Integrations, My Account & Billing, Image Library, ConstantContact.com and Contact Center
[19]. If your campaign will not send, Email Campaigns and Email Automation are the two rows
to read; if you cannot get in at all, it is Login.

And the dated history below the indicator tells you whether today is unusual. On a quiet day the
page simply repeats "No incidents reported." under each date [19], which is itself the
answer most of the time.

If the page says everything is operational and your problem persists, skip ahead to the section
on the four things that look like an outage and are not. That is the likelier explanation, and
each has a different fix.



> 💡 **undefined:** Read the component, not just the indicator. Email Campaigns and Email Automation are the rows that matter if a send has stalled; Login is the row that matters if you cannot get in.

## What the published record actually shows

The status page exposes its history, so we counted all of it. Fifty incidents are published,
spanning 13 June 2024 to 1 October 2026. Twenty-eight months [19].

By the vendor's own impact labels: 26 minor, 12 major, 4 critical, and 8 recorded with no impact
rating. That averages a little under two published incidents a month, and the distribution is
lumpy rather than steady. The busiest months in the record are October 2024, October 2025 and
July 2026, each with five, while several months carry none at all.

Two things follow that are worth stating plainly. First, a published incident rate of under two a
month, with only four critical events in twenty-eight months, is not the profile of an unreliable
product. Second, the record exists at all, dated and labelled, which is a stronger position than
most of this category offers, a vendor that publishes four critical incidents is telling you
something a vendor with an unreadable status page is not.

The caveat is the one that applies to every status page: it records what the vendor chose to post.
A published history is evidence of transparency and of incidents, not proof of their completeness.
We report it as the vendor's record rather than as an independent measurement, and we can say
that because we could read it.



> ⚠ **undefined:** Exceeding your send allowance does not stop sending — it charges $0.002 per send over — so an allowance problem looks like a bill, not an outage.

## The largest category is delay, not outage

Sorting those fifty incidents by what their titles describe changes the picture, and it explains
the search volume better than any uptime figure.

Seventeen of the fifty mention delay or slowness. Eleven concern sending or delivery. Eight
concern login. Six name campaigns, five name contacts or segments, four name reporting, and one
names the API [19]. The modal incident on this platform is not the site being unavailable; it
is the site being available and your campaign arriving late.

That matters for how you should read your own experience. If you scheduled a send and nothing
appears to have happened, the product is very probably not down. It is very probably running
behind, which is a different problem with a different correct response.

The vendor's own incident text for the most recent entry, on 1 October 2026, tells you what that
response is, and it is counter-intuitive enough to be worth quoting in full: "We are experiencing delays in email campaign sending at this time. We recommend leaving your campaign scheduled, as unscheduling and rescheduling may result in further delays. Our engineers are aware of this issue and are working to resolve the delays." [19]

Leave it alone. The instinct when a send stalls is to cancel and resend, and the vendor states
that this makes it worse. That single sentence is the most practically useful thing on the status
page, and it is the reason to check the page before touching the campaign rather than after.



> 💡 **undefined:** Subscribe to the status page's email or text notifications. It is the only way to learn about a delay before your recipients do.

## How long incidents last

We computed resolution times from the published created and resolved timestamps across all fifty
incidents [19].

The median is 2.1 hours. The mean is 4.0 hours, pulled up by a tail. The longest single incident
in the record ran 44.7 hours.

The gap between a 2.1-hour median and a 4.0-hour mean is the shape worth internalising: most
incidents are over inside an afternoon, and a small number run into a second day. For planning
purposes that means a same-day send has a reasonable chance of going out late rather than not at
all, while a date-critical send, an event reminder, a deadline notice, a sale that ends, should
not be scheduled with two hours of margin.

The most recent incident illustrates the median rather than the tail. The vendor's own log shows
the first notice at 12:03, an update at 12:05, and the resolution at 12:59, with the closing line
"The issue has been resolved, and mail is sending normally." [19] Under an hour, start to
finish, publicly logged with timestamps.

That level of logging is also what makes the subscription options on the page worth using. The
status page offers email and SMS notification for incidents, which is the only way to learn about
a delay before your recipients do.

## Why 720 people a month search this

Here is the number that reframes the whole article. *is constant contact down* draws 720 searches
a month in the United States. The published incident rate is under two a month. People are
searching roughly one order of magnitude more often than the vendor records something happening.

That gap is not evidence of hidden outages. It is evidence of what the search actually means.
Someone types *is constant contact down* when their send has not arrived, when a page is slow,
when they cannot log in on the first attempt, or when a recipient says they got nothing, and in
most of those cases the platform is operational and something else is wrong.

The review corpus contains the version of this that is a real complaint rather than a
misdiagnosis, and it is specific: "The site keeps crashing. I have had to call customer service 3 times to have them send my email for me." [10] Note the remedy in that sentence. Live phone
support is on every tier of this product including the cheapest [2], and in this corpus
support appears in 27 of 100 reviews and splits 18 positive to 8 negative, so the realistic path
when something is broken is a person, and that path is unusually short here.

The practical ordering, then: check the status page first because it takes ten seconds and is
readable, then check the four things below, then call, because calling works on this product.



> 💡 **undefined:** Do not unschedule a stalled campaign. The vendor states that unscheduling and rescheduling may result in further delays.

## Four things that look like an outage and are not

Each of these produces the experience of *nothing is sending* while every component shows
operational, and each has a different fix.

A delay, not a failure. Seventeen of fifty published incidents are delays [19], and a delay
with no incident posted yet looks identical to one with an incident posted. Leave the campaign
scheduled, per the vendor's own advice [19].

Your send allowance, not the platform. Plans carry a monthly send allowance of "10, 12, or 24 times the highest number of contacts in your contact pricing tier" [4]. Exceeding it does not
stop your sending, it charges "$0.002 for every send over the maximum send allowance" [4], so
this is a cause of a surprising bill rather than a stoppage. Worth checking in the same session,
since the billing tab is where the real send count lives.

Deliverability, not availability. If some recipients received the campaign and others did not,
the platform sent it and something between you and the inbox did not accept it. The vendor claims
a "98% inbox rate" [2] with no stated window or method, so treat it as a claim; the useful
action is checking authentication on your sending domain and the bounce report. Remember that
"Even if an email bounces, it still counts as a send" [4], so a deliverability problem is
also a billing one.

Reporting, not sending. Four published incidents concern reporting specifically [19], and the
vendor documents a permanent discrepancy that looks like one: "Resends are not included in the stats on the Reporting tab, so you should always refer to your account page to see your most accurate send count for the billing period." [4] If your numbers look wrong rather than
absent, this is the likeliest reason and nothing is broken.

## What an incident looks like from the inside

Worth walking through one, because knowing the shape tells you how long to wait before acting.

The most recent entry in the record is 1 October 2026, titled "Delays in email campaign sending",
and the vendor logs it in three timestamped stages [19]. At 12:03 the first notice goes up as
Investigating, carrying the diagnosis and the instruction: "We are experiencing delays in email campaign sending at this time. We recommend leaving your campaign scheduled, as unscheduling and rescheduling may result in further delays. Our engineers are aware of this issue and are working to resolve the delays." At 12:05 an Update confirms the investigation continues. At 12:59 the
entry closes as Resolved, with "The issue has been resolved, and mail is sending normally."

Fifty-six minutes, start to finish, with the actionable instruction in the first post rather than
the last. That is a well-run incident log, and it is the median case: 2.1 hours is the middle of
the distribution across all fifty [19].

The three stages are worth recognising because they tell you different things. Investigating means
the vendor has confirmed a real problem and usually names the affected behaviour. Update means
nothing has changed yet. Resolved is the only one that means your campaign will go.

What this implies for your own behaviour during a delay: the useful window is short. If an
incident is posted, the median says wait, and the vendor's instruction says do not touch the
campaign. If no incident is posted after twenty or thirty minutes and your send is still not
moving, the problem is more likely yours than theirs, which is the next section.



> 💡 **undefined:** If nothing is posted and the problem persists, call. Phone and chat are on every tier of this product, which is not true of its rivals at the entry price.

## How this compares with the rest of the category

The thing that makes this article possible is itself the finding, and it is worth stating because
a reader comparing products should weigh it.

We tried to do the same count for Klaviyo and could not. Its status page yielded zero characters
of readable text, the information exists and is assembled in the browser, so there is no component
list to read, no incident history to count and no resolution times to compute. Search demand for
*is klaviyo down* is 720 a month, exactly the same as for this product, and for that one there is
no public record a reader can check.

Constant Contact publishes 24 named components, a live indicator, a dated 28-month history with
impact labels, timestamped incident logs, and email and text notification [19]. On a
transparency axis that is not a close comparison.

It is also worth noting what the record costs the vendor to publish. Four critical incidents and
twelve major ones over twenty-eight months is not a flattering number in isolation, and a vendor
optimising appearances would make that page harder to read rather than easier. We have measured
three products in this category whose pricing pages serve prices to browsers only; this is the
same company choosing the opposite behaviour on the page where it would be most tempting to hide.

Set against that: nine of this vendor's own commercial pages returned nothing to us on a four-path
pass, and the site rate-limits automated readers. So the transparency is real and it is not
uniform — the status page is open and the marketing site is closed, which is an unusual way round.



> ⚠ **undefined:** If the vendor's commercial pages look down to a tool rather than a browser, that is the site returning 403 to automated readers, not an incident.

## What the status page does not cover

Three limits, stated so you know when the page stops being the right place to look.

It reports components rather than accounts. A page showing Login as operational does not tell you
that your login works; an account-level problem — a locked account, a failed payment, a
suspension — is invisible to it. The billing FAQ notes that the system draws on your account
balance before your card [3], so a payment problem can arrive without a card decline, and it
will not appear on the status page.

It covers the platform, not the separate products. Constant Contact also sells `Lead Gen & CRM`
as its own product with its own documentation [20], and the component list on the status page
does not name it. If that is the part not working, the status page is the wrong page.

And it says nothing about the vendor's commercial site. Nine of those pages returned nothing to
every reader we tried, from two networks and with a browser user-agent, though four of them came
through later in a single window. That is not an outage and it is not on the status page; it is
how the site treats automated readers. If you are trying to read the pricing page with a tool
rather than a browser, that is why it looks down.



> ⚠ **undefined:** The status page reports components, not accounts. A locked account, a failed payment or a suspension is invisible to it.



## FAQ

**How do I check if Constant Contact is down?**

Open status.constantcontact.com. Unlike several products in this category, it serves readable text rather than an application you have to wait for: a single headline indicator, 24 named components each with its own state, and a dated incident history. Read the component rather than just the indicator, because outages here are rarely all-or-nothing — if a campaign has stalled, Email Campaigns and Email Automation are the rows that matter.

**How often does Constant Contact actually go down?**

The vendor has published 50 incidents between 13 June 2024 and 1 October 2026, which is a little under two a month across twenty-eight months. By its own impact labels those break down as 26 minor, 12 major, 4 critical and 8 with no rating. Four critical events in twenty-eight months is not the profile of an unreliable product, and the fact that the record is published, dated and countable is itself worth something.

**My campaign has not sent. Is it an outage?**

Probably not. Seventeen of the fifty published incidents describe delay or slowness rather than unavailability, so a late send is the most common failure mode here. The vendor's advice during a delay is counter-intuitive and worth following: leave the campaign scheduled, because unscheduling and rescheduling may result in further delays. If the status page shows everything operational, check your send allowance, your domain authentication and your bounce report before assuming the platform.

**How long do incidents usually last?**

The median across all fifty published incidents is 2.1 hours and the mean is 4.0, with the longest running 44.7 hours. Most are over inside an afternoon and a small number run into a second day. The practical consequence is for date-critical sends: an event reminder or a deadline notice should not be scheduled with two hours of margin.

## If it is genuinely down, the order of operations

Check the status page and read the component, not just the indicator [19]. The component tells
you whether to wait or to act.

If an incident is posted and it is a delay, leave your campaign scheduled. The vendor states that
unscheduling and rescheduling may make it worse [19].

Subscribe to the status page's notifications while you are there, by email or text. It is the only
mechanism that tells you before your recipients do.

If nothing is posted and the problem is yours, work the four causes above in order: allowance,
authentication, reporting discrepancy, account state. Three of the four are visible on your own
billing and reporting tabs.

Then call. Phone and chat with a human are on every tier of this product [2], which is not
true of its main rivals at the entry price, and the review corpus says that route works more often
than it fails. For a date-critical send, calling at the thirty-minute mark costs you nothing and
is faster than any other diagnosis you can run.




## Sources

[1] Constant Contact vendor pricing page — https://www.constantcontact.com/pricing (2026-10)
[2] Constant Contact vendor billing FAQ — https://community.constantcontact.com/t5/FAQs/Billing-FAQ/ta-p/386088 (2026-10)
[3] Constant Contact vendor documentation on the email send allowance and overage fee — https://knowledgebase.constantcontact.com/email-digital-marketing/articles/KnowledgeBase/46046-Constant-Contact-s-email-send-limit-and-overage-fee?lang=en_US (2026-10)
[4] Constant Contact vendor documentation on the SMS marketing add-on — https://knowledgebase.constantcontact.com/email-digital-marketing/articles/KnowledgeBase/46517-Add-SMS-to-your-Constant-Contact-email-plan?lang=en_US (2026-10)
[5] Constant Contact vendor documentation on trying SMS features — https://knowledgebase.constantcontact.com/email-digital-marketing/articles/KnowledgeBase/54070-Try-Before-You-Buy-SMS-Features?lang=en_US (2026-10)
[6] Constant Contact vendor documentation on payment options — https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5775-payment-options-for-your-account?lang=en_US (2026-10)
[7] Constant Contact vendor documentation on lists, tags and segments — https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5963-difference-between-tags-and-lists?lang=en_US (2026-10)
[8] Constant Contact vendor documentation on exporting contacts — https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5295-exporting-a-contact-list-from-constant-contact (2026-10)
[9] Trustpilot aggregate score and review corpus for Constant Contact — https://www.trustpilot.com/review/constantcontact.com (2026-10)
[10] Google Play listing for the Constant Contact Marketing App — https://play.google.com/store/apps/details?id=com.constantcontact.toolkit (2026-10)
[11] WordPress.org plugin directory listing for Constant Contact Forms — https://wordpress.org/plugins/constant-contact-forms/ (2026-10)
[12] Mailchimp vendor pricing page — https://mailchimp.com/pricing/ (2026-09)
[13] Mailchimp vendor documentation on pricing plans — https://mailchimp.com/en/help/about-mailchimp-pricing-plans/ (2026-09)
[14] Mailchimp vendor plan comparison page — https://mailchimp.com/en/pricing/marketing/compare-plans/ (2026-09)
[15] Trustpilot aggregate score for Mailchimp — https://www.trustpilot.com/review/mailchimp.com (2026-09)
[16] Mailchimp vendor documentation on changing or pausing a plan — https://mailchimp.com/en/help/change-or-pause-your-pricing-plan/ (2026-09)
[17] Mailchimp vendor documentation on contacts — https://mailchimp.com/en/help/about-your-contacts/ (2026-09)
[18] Constant Contact public status page and its incident history — https://status.constantcontact.com/ (2026-10)
[19] Constant Contact vendor documentation for Lead Gen & CRM, a separate product — https://knowledgebase.constantcontact.com/lead-gen-crm/articles/KnowledgeBase/51158-Account-Import-History-Overview?lang=en_US (2026-10)
[20] Constant Contact's own Shopify App Store listing, which publishes the month-to-month prices its pricing page does not — https://apps.shopify.com/constant-contact-2 (2026-10)