Workvivo Outage History
4 incidents recorded over the last 365 days, 3 of them resolved, 1 still open. 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 Workvivo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 1, 2026 | Workvivo Application - outage affecting users in EU2 RegionOn Tuesday, 1 September, between 05:02 and 05:27 (GMT+1), Workvivo experienced intermittent connectivity issues affecting some customers hosted in our EU2 region, impacting access to Workvivo across Web and Mobile. The… | 0 min | Resolved |
| Mar 3, 2026 | Service Disruption - Workvivo UAE (.me) AWS Region OnlyIn line with guidance from AWS UAE, we strongly recommend that customers currently running workloads in the Middle East region take immediate steps to migrate those workloads to alternative AWS Regions. For the latest… | — | Investigating |
| Mar 2, 2026 | Service Disruption - Workvivo UAE (.me) AWS Region OnlyIn line with guidance from AWS UAE, we strongly recommend that customers currently running workloads in the Middle East region take immediate steps to migrate those workloads to alternative AWS Regions. For the latest… | 11h 20m | Resolved |
| Jan 23, 2026 | Workvivo Application - activity feed issue affecting usersThe issue has been resolved. Impact was limited to a subset of clients. Root cause analysis is ongoing, and we will continue to monitor the situation closely. | 16 min | 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 Workvivo 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 Workvivo 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 Workvivo 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 Workvivo outage in this window ran 11h 20m, against a mean recovery of 3h 52m. If you depend on Workvivo 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.