Yesware Outage History
5 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 Yesware Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Yesware Platform MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 0m | Scheduled |
| Oct 20, 2026 | Yesware Campaigns MaintenanceScheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 30m | Scheduled |
| Jul 24, 2026 | Authentication Issues with Yesware's Salesforce IntegrationThis incident has been resolved. | 1246h 5m | Resolved |
| Mar 10, 2026 | Custom Availability for Meeting Scheduler Not LoadingThis incident has been resolved. | 12h 46m | Resolved |
| Nov 20, 2025 | Mac Users Experiencing Issues with Desktop Outlook Add-inOur engineers have successfully deployed a fix, which should eliminate any previously encountered issues tracking emails sent through the desktop version of Outlook while on Mac computers. Users may need to close out… | 88h 59m | Resolved |
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 Yesware 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 Yesware 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 Yesware 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 Yesware outage in this window ran 51d 22h, against a mean recovery of 11d 6h. If you depend on Yesware 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.