SendPulse Outage History

14 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 SendPulse status99.94% uptime history

Every Recorded SendPulse Incident

SendPulse incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 5, 2026Authorisation Service is down11 minResolved
Oct 30, 2026Scheduled maintenance for Email VerifierScheduled Maintenance1h 0mScheduled
Oct 23, 2026Scheduled maintenance for AutomationScheduled Maintenance1h 0mScheduled
Oct 22, 2026Member Area is down9 minResolved
Oct 21, 2026REST API is down22 minResolved
Oct 21, 2026Authorisation Service is down20 minResolved
Oct 21, 2026Member Area is down33 minResolved
Oct 21, 2026Possible disruptions for users in some regions2h 55mResolved
Oct 2, 2026Slow loading of Instagram bots and chats50 minResolved
Sep 28, 2026Google Sheets authorization issues11 minResolved
Sep 11, 2026Authorisation Service is down10 minResolved
Sep 11, 2026Member Area is down12 minResolved
Sep 4, 2026Increased message delivery errors on Facebook Messenger9h 58mResolved
Aug 28, 2026Delays in chatbot message delivery7 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 SendPulse 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 SendPulse 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 SendPulse 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 SendPulse outage in this window ran 9h 58m, against a mean recovery of 1h 17m. If you depend on SendPulse 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.