Constant Contact status history
Current state: operational — “All Systems Operational” per https://status.constantcontact.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Constant Contact incidents last?
From 25 incidents with a vendor-posted start and resolve time. Longest on record: Delays with Segments and Automation Path Starts — 44.6 h (2026-07-23 23:50 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (25)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-14 19:09 UTC | Unable to view partner organization reporting | resolved | minor | 3 h 32 min |
| 2026-09-02 17:40 UTC | Login Issues | resolved | major | 1 h 45 min |
| 2026-07-23 23:50 UTC | Delays with Segments and Automation Path Starts | resolved | minor | 44 h 39 min |
| 2026-07-18 01:17 UTC | Login Issues | resolved | minor | 48 min |
| 2026-07-15 10:27 UTC | Login Issues | resolved | minor | 42 min |
| 2026-07-07 15:23 UTC | Delays in sending email | resolved | minor | 5 h 09 min |
| 2026-07-01 20:30 UTC | Error when creating new campaigns | resolved | critical | 43 min |
| 2026-06-23 18:37 UTC | Slowness when logging in and navigating within the account (6/23/2026) | resolved | minor | 47 min |
| 2026-04-21 20:49 UTC | Delay in Email Delivery | resolved | minor | 30 min |
| 2026-04-20 13:07 UTC | Delay in Email Delivery | resolved | minor | 1 h 39 min |
| 2026-04-06 18:52 UTC | Login Issues | resolved | none | 0 min |
| 2026-03-26 16:18 UTC | Slow navigation loading times | resolved | none | 3 h 38 min |
| 2026-03-12 01:00 UTC | Link Tracking and Reporting issue | resolved | none | 11 h 37 min |
| 2026-02-25 19:51 UTC | Email Delivery Delays | resolved | major | 31 min |
| 2026-02-06 18:39 UTC | Slow account navigation and sending campaigns | resolved | none | 1 h 07 min |
| 2026-01-22 19:30 UTC | Email Delivery Delays due to Microsoft Outage | resolved | minor | 13 h 00 min |
| 2025-11-19 18:49 UTC | Delays in test email delivery | resolved | minor | 3 h 16 min |
| 2025-11-18 12:35 UTC | Login Issues | resolved | minor | 2 h 03 min |
| 2025-11-12 19:45 UTC | SMS login issues | resolved | none | 1 h 32 min |
| 2025-10-27 20:05 UTC | Issues with our website | resolved | critical | 13 min |
| 2025-10-20 15:43 UTC | Product Navigation Issues | resolved | major | 1 h 04 min |
| 2025-10-16 18:15 UTC | Issues Loading Social Pages | resolved | minor | 1 h 48 min |
| 2025-10-02 13:30 UTC | Issues Viewing Reporting | resolved | minor | 1 h 30 min |
| 2025-10-01 12:14 UTC | Constant Contact Community | resolved | none | 21 min |
| 2025-09-24 17:15 UTC | Social post and landing page issues | resolved | none | 1 h 30 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Constant Contact with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"constant-contact"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}