Visier Analytics Outage History
9 incidents recorded over the last 365 days, 9 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 Visier Analytics Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 17, 2026 | We are currently experiencing an issue with Vee 2 in our Asia Pacific ap00 deployment.The incident has been resolved. We apologize for any inconvenience this may have caused. | 3 min | Resolved |
| May 29, 2026 | We are currently experiencing an issue with Vee AI in our Europe region.The issues with the AI Language Model have been resolved, Vee is back online. | 1h 50m | Resolved |
| May 17, 2026 | We are currently experiencing an issue with Vee infrastructure in ap00This incident has been resolved. | 69h 52m | Resolved |
| May 7, 2026 | We are currently experiencing an issue with the API health-check endpointThis incident has been resolved. | 5h 6m | Resolved |
| Apr 27, 2026 | We are currently experiencing an issue with Vee infrastructure.This incident has been resolved. | 1h 5m | Resolved |
| Apr 12, 2026 | We are currently experiencing an issue with certain endpoints in the Compensation Benchmark API.This incident has been resolved. | 2h 43m | Resolved |
| Jan 28, 2026 | We are currently experiencing an performance issue with Visier PeopleThe incident has been resolved. We apologize for the disruptions to your workflows. | 53 min | Resolved |
| Dec 5, 2025 | We are currently experiencing an issue with the connectivity to our services.This incident has been resolved. | 35 min | Resolved |
| Nov 18, 2025 | We are currently experiencing an issue with the connectivity to our servicesThis incident has been resolved. | 2h 57m | 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 Visier Analytics 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 Visier Analytics 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 Visier Analytics 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 Visier Analytics outage in this window ran 2d 21h, against a mean recovery of 9h 27m. If you depend on Visier Analytics 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.