Funraise Outage History

4 incidents recorded over the last 365 days, 3 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.

Every Recorded Funraise Incident

Funraise incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Platform OutageThis incident has been resolved.3h 8mResolved
Sep 28, 2026Funraise Scheduled MaintenanceThe scheduled maintenance has been completed.30 minScheduled
Aug 7, 2026Platform Latency and Intermittent Payment ErrorsThis incident has been resolved.3h 7mResolved
Jan 9, 2026Intercom Outage Impacting Live ChatIntercom has implemented a fix for the earlier outage affecting Inbox, Messenger, Fin, and related features in the US region. Live chat and in-app messaging should now be functioning normally. We are continuing to…38 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 Funraise 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 Funraise 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 Funraise 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 Funraise outage in this window ran 3h 8m, against a mean recovery of 1h 51m. If you depend on Funraise 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.