Visier Outage History

Visier is up right now

Visier had 11 outages in the last 2 years totaling 92h 52m of downtime — averaging 0.5 incidents per month.

There were 11 Visier outages since October 20, 2025 totaling 92h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.visier.com

Major September 17, 2026

We are currently experiencing an issue with Vee 2 in our Asia Pacific ap00 deployment.

Detected by Pingoru
Sep 17, 2026, 12:20 AM UTC
Resolved
Sep 17, 2026, 12:43 AM UTC
Duration
22m
Affected: Asia-Pacific (ap)
Timeline · 2 updates
  1. identified Sep 17, 2026, 12:39 AM UTC

    Please note that some customers may currently be experiencing an issue with Vee2 answering questions in the Asia Pacific Region. We are actively working on resolving the issue. We apologize for any inconvenience this may have caused. We thank you for your patience.

  2. resolved Sep 17, 2026, 12:43 AM UTC

    The incident has been resolved. We apologize for any inconvenience this may have caused.

Read the full incident report →

Notice May 29, 2026

We are currently experiencing an issue with Vee AI in our Europe region.

Detected by Pingoru
May 29, 2026, 03:10 PM UTC
Resolved
May 29, 2026, 05:00 PM UTC
Duration
1h 50m
Timeline · 3 updates
  1. investigating May 29, 2026, 03:37 PM UTC

    Please note that some customers hosted in the Europe region (ae00) are currently experiencing issues with Vee in Visier People. We are actively working on resolving the issue. We apologize for any inconvenience this may have caused. We appreciate your patience.

  2. identified May 29, 2026, 03:59 PM UTC

    The issue has been identified, and a change is being rolled out to resolve it. Thank you for your understanding.

  3. resolved May 29, 2026, 05:25 PM UTC

    The issues with the AI Language Model have been resolved, Vee is back online.

Read the full incident report →

Minor May 17, 2026

We are currently experiencing an issue with Vee infrastructure in ap00

Detected by Pingoru
May 17, 2026, 03:30 AM UTC
Resolved
May 20, 2026, 01:23 AM UTC
Duration
2d 21h
Affected: Asia-Pacific (ap)
Timeline · 4 updates
  1. investigating May 17, 2026, 04:21 AM UTC

    Please note that some customers may currently be experiencing an issue with Vee performance in Visier People in ap00. We are actively working on resolving the issue. We apologize for any inconvenience this may be causing.

  2. identified May 17, 2026, 12:29 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 17, 2026, 01:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 20, 2026, 01:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

We are currently experiencing an issue with the API health-check endpoint

Detected by Pingoru
May 07, 2026, 11:44 PM UTC
Resolved
May 08, 2026, 04:50 AM UTC
Duration
5h 6m
Affected: US (au)
Timeline · 5 updates
  1. identified May 08, 2026, 12:04 AM UTC

    Please note that some customers hosted in the US (sites au00 and au03) may be experiencing API health-check endpoint errors, while the API is functional. The problem originates from one of our service providers. We are actively working on resolving the issue with them. We apologize for any inconvenience, and we thank you for your patience.

  2. monitoring May 08, 2026, 12:08 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified May 08, 2026, 12:13 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring May 08, 2026, 01:00 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved May 08, 2026, 04:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 27, 2026

We are currently experiencing an issue with Vee infrastructure.

Detected by Pingoru
Apr 27, 2026, 09:52 PM UTC
Resolved
Apr 27, 2026, 10:58 PM UTC
Duration
1h 5m
Affected: US (au)US (zu)Canada (ac)Canada (zc)Asia-Pacific (ap)
Timeline · 3 updates
  1. identified Apr 27, 2026, 10:18 PM UTC

    Please note that some customers may currently be experiencing an issue with Vee performance in Visier People. We are actively working on resolving the issue. We apologize for any inconvenience this may be causing.

  2. monitoring Apr 27, 2026, 10:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 27, 2026, 10:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 12, 2026

We are currently experiencing an issue with certain endpoints in the Compensation Benchmark API.

Detected by Pingoru
Apr 12, 2026, 03:35 PM UTC
Resolved
Apr 12, 2026, 06:19 PM UTC
Duration
2h 43m
Affected: US (au)US (au)
Timeline · 3 updates
  1. investigating Apr 12, 2026, 04:21 PM UTC

    Please note that some customers may currently be experiencing an issue with certain endpoints in the Compensation Benchmark API. We are actively working on resolving the issue. We apologize for any inconvenience this may cause. We thank you for your patience.

  2. identified Apr 12, 2026, 04:22 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 12, 2026, 06:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 28, 2026

We are currently experiencing an performance issue with Visier People

Detected by Pingoru
Jan 28, 2026, 01:13 AM UTC
Resolved
Jan 28, 2026, 02:07 AM UTC
Duration
53m
Affected: US (au)US (au)
Timeline · 4 updates
  1. investigating Jan 28, 2026, 01:13 AM UTC

    Please note that some customers may currently be experiencing performance issues. We are actively working on resolving the issue. We apologize for any inconvenience this may be causing.

  2. identified Jan 28, 2026, 01:44 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 28, 2026, 01:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 28, 2026, 02:07 AM UTC

    The incident has been resolved. We apologize for the disruptions to your workflows.

Read the full incident report →

Critical December 5, 2025

We are currently experiencing an issue with the connectivity to our services.

Detected by Pingoru
Dec 05, 2025, 08:50 AM UTC
Resolved
Dec 05, 2025, 09:25 AM UTC
Duration
35m
Affected: US (au)US (au)US (au)US (au)Europe (ae)Europe (ae)Europe (ae)Canada (ac)Canada (ac)Canada (AC)Asia-Pacific (ap)Asia-Pacific (ap)
Timeline · 3 updates
  1. investigating Dec 05, 2025, 09:04 AM UTC

    Please note that some customers may be experiencing connectivity errors. The problem originates from one of our service providers. We are actively working with them on resolving the issue. We apologize for any inconvenience, and we thank you for your patience.

  2. monitoring Dec 05, 2025, 09:21 AM UTC

    Our provider has implemented a fix, and connectivity has been restored.

  3. resolved Dec 05, 2025, 09:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

We are currently experiencing an issue with the connectivity to our services

Detected by Pingoru
Nov 18, 2025, 12:05 PM UTC
Resolved
Nov 18, 2025, 03:02 PM UTC
Duration
2h 57m
Affected: US (au)US (au)US (au)US (au)Europe (ae)Europe (ae)Europe (ae)Canada (ac)Canada (ac)Canada (AC)Asia-Pacific (ap)Asia-Pacific (ap)
Timeline · 6 updates
  1. identified Nov 18, 2025, 12:05 PM UTC

    Please note that some customers may be experiencing connectivity errors. The problem originates from one of our service providers. We are actively working with them on resolving the issue. We apologize for any inconvenience, and we thank you for your patience.

  2. identified Nov 18, 2025, 12:12 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Nov 18, 2025, 12:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Nov 18, 2025, 12:31 PM UTC

    We are continuing to monitor for any further issues.

  5. identified Nov 18, 2025, 12:46 PM UTC

    The issues with our provider infrastructure haven't been solved; we are seeing an increase in error rates.

  6. resolved Nov 18, 2025, 03:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

We are currently experiencing an issue with Data Products Services.

Detected by Pingoru
Oct 20, 2025, 03:24 PM UTC
Resolved
Oct 20, 2025, 07:50 PM UTC
Duration
4h 25m
Affected: US (au)
Timeline · 4 updates
  1. identified Oct 20, 2025, 03:24 PM UTC

    Please note that some customers may currently be experiencing an issue with our Data Products services, such as Skills and Compensation Benchmarks. We are actively working with our infrastructure service provider on resolving the issue. We apologize for any inconvenience this may caused.

  2. identified Oct 20, 2025, 03:35 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Oct 20, 2025, 06:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 20, 2025, 07:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

We are currently experiencing interruptions to some Visier services.

Detected by Pingoru
Oct 20, 2025, 07:19 AM UTC
Resolved
Oct 20, 2025, 10:17 AM UTC
Duration
2h 58m
Affected: US (au)US (au)US (au)
Timeline · 5 updates
  1. investigating Oct 20, 2025, 07:19 AM UTC

    Please note that some customers may currently be experiencing an interruption to their Visier services. We are actively working on resuming all services to normal. We apologize for any inconvenience this may have caused. Thank you for your patience.

  2. identified Oct 20, 2025, 09:09 AM UTC

    The issue impacting one of our basic infrastructure providers has not been resolved. At this moment, more services in the US region are being impacted.

  3. monitoring Oct 20, 2025, 09:40 AM UTC

    The services from our infrastructure provider seem recovered, we are monitoring our system.

  4. monitoring Oct 20, 2025, 09:41 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 20, 2025, 10:17 AM UTC

    This incident has been resolved.

Read the full incident report →