impact.com Outage History

28 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live impact.com status100.00% uptime history

Every Recorded impact.com Incident

impact.com incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 21, 2026General Reporting Delay - Actions only (Tracking Unaffected)This incident has been resolved.3h 28mResolved
Oct 20, 2026Cloud Infrastructure MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Oct 17, 2026Maintenance of Reporting InfrastructureThe scheduled maintenance has been completed.4h 0mScheduled
Oct 13, 2026Release 1.204The scheduled maintenance has been completed.2h 0mScheduled
Sep 17, 2026Release 1.203The scheduled maintenance has been completed.2h 0mScheduled
Aug 24, 2026Release 1.202The scheduled maintenance has been completed.2h 0mScheduled
Aug 20, 2026Newsletters, CRM, and Workflows Emails Not SendingThe incident has been resolved. In order to improve performance a change was made to outreach analytics backend system which prevented emails from being sent out and logged. The change was reverted and the system…9h 26mResolved
Jul 30, 2026Release 1.201The scheduled maintenance has been completed.2h 0mScheduled
Jul 29, 2026General Reporting Delay (Postback Actions ONLY)This incident has been resolved.3h 15mResolved
Jul 17, 2026Platform Services: Search & Indexing UpgradeThe scheduled maintenance has been completed.5h 0mScheduled
Jul 6, 2026Release 1.200The scheduled maintenance has been completed.2h 0mScheduled
Jun 29, 2026Elevated Report - API ErrorsThis incident has been resolved.4h 8mResolved
Jun 8, 2026Elevated Report - API ErrorsThis incident has been resolved.6h 15mResolved
Jun 6, 2026Maintenance of Reporting InfrastructureThe scheduled maintenance has been completed.3h 0mScheduled
Jun 4, 2026Release 1.199The scheduled maintenance has been completed.2h 0mScheduled
May 7, 2026General Reporting Delay (Tracking Unaffected)This incident has been resolved.6h 13mResolved
May 7, 2026Release 1.198The scheduled maintenance has been completed.2h 0mScheduled
Apr 14, 2026Platform Session PerformanceThis incident has been resolved.2h 12mResolved
Mar 24, 2026Release 1.196The scheduled maintenance has been completed.2h 0mScheduled
Mar 22, 2026Scheduled Maintenance: BigIP F5 appliance upgradeThe scheduled maintenance has been completed.2h 0mScheduled
Feb 24, 2026Release 1.195The scheduled maintenance has been completed.2h 0mScheduled
Jan 22, 2026Release 1.194The scheduled maintenance has been completed.2h 0mScheduled
Jan 22, 2026Click Reporting DelayThis incident has been resolved.3h 5mResolved
Jan 14, 2026Conversion Processing Delay (Tracking Unaffected)This incident has been resolved.7h 8mResolved
Jan 13, 2026General Reporting Delay (Tracking Unaffected)This incident has been resolved.3h 16mResolved
Dec 11, 2025General Platform Incident- Identified the IssueThe Advocate product navigation and access disruptions have been resolved. We apologize for any inconvenience. Should you continue to experience anything out of the ordinary, please try navigating to another page…2h 47mResolved
Dec 10, 2025Release 1.193The scheduled maintenance has been completed.2h 0mScheduled
Dec 5, 2025General Platform Incident- ResolvedThe platform disruptions have been resolved by the upstream provider. We apologize for any inconvenience. Should you continue to experience anything out of the ordinary please contact our Customer Solutions team (Need…47 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next impact.com incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This impact.com Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before impact.com acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single impact.com outage in this window ran 9h 26m, against a mean recovery of 3h 13m. If you depend on impact.com in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.