Proposify Outage History

10 incidents recorded over the last 365 days, 10 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 Proposify status100.00% uptime history

Every Recorded Proposify Incident

Proposify incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 29, 2026Email System DownThis incident has been resolved.2h 24mResolved
Aug 26, 2026Document Sending IssuesThis incident has been resolved11h 30mResolved
Aug 15, 2026New Proposify documents list service degradationThe incident has been resolved2h 33mResolved
Jul 24, 2026Login IssuesThis incident has been resolved.2h 26mResolved
Jul 20, 2026Application outageThe incident has been resolved.8 minResolved
May 8, 2026Custom Domains IssuesThis incident has been resolved.1h 14mResolved
Feb 10, 2026Service degradationWe have confirmation from our provider that the incident has been resolved.1h 33mResolved
Jan 21, 2026Document sending errorsThis incident has been resolved.3h 50mResolved
Dec 9, 2025Performance degradation affecting document editor and previewThis incident has been resolved.56 minResolved
Nov 26, 2025New Signup Users Redirected Back to Signup Page After Template SelectionThis incident has been resolved.1h 29mResolved

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 Proposify 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 Proposify 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 Proposify 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 Proposify outage in this window ran 11h 30m, against a mean recovery of 2h 48m. If you depend on Proposify 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.