VTS Outage History

VTS is up right now

Pingoru has recorded 46 incidents for VTS: 9 in the last 12 months and 5 in the last 90 days.

Source: status.vts.com

46incidents recorded
9last 12 months
5last 90 days
12 hourstypical duration

Incidents, newest first

Major January 14, 2025 Issue with HID Access Integrations 1h 48m Activate, Rise

Started Jan 14, 2025, 02:39 PM UTC· resolved Jan 14, 2025, 04:28 PM UTC

  1. monitoring Jan 14, 2025, 02:39 PM UTC

    HID is currently experiencing an outage in their authentication service. As a result, VTS can’t create or update credentials.

  2. monitoring Jan 14, 2025, 02:40 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Jan 14, 2025, 02:49 PM UTC

    For further updates, please refer to HID's status page: https://status.origo.hidglobal.com/incident/120

  4. resolved Jan 14, 2025, 04:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 13, 2025 Lease export degradation 22h 12m Lease

Started Jan 13, 2025, 05:14 PM UTC· resolved Jan 14, 2025, 03:26 PM UTC

  1. investigating Jan 13, 2025, 05:14 PM UTC

    We are experiencing this degradation with some of our exports for the VTS Lease product.

  2. investigating Jan 13, 2025, 06:37 PM UTC

    We continue to investigate the root cause of this issue. We will have an update in 4 hours.

  3. monitoring Jan 13, 2025, 09:29 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact. We will have an update tomorrow morning, US East Coast time (GMT-5).

  4. resolved Jan 14, 2025, 03:26 PM UTC

    We have resolved this incident and are continuing to monitor for any service deviation.

Read the full incident report →

Minor December 10, 2024 Activate latency spikes 1d Activate

Started Dec 10, 2024, 03:32 PM UTC· resolved Dec 11, 2024, 04:23 PM UTC

  1. investigating Dec 10, 2024, 03:32 PM UTC

    We are currently investigating latency spikes in Activate.

  2. identified Dec 10, 2024, 07:02 PM UTC

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

  3. monitoring Dec 10, 2024, 08:48 PM UTC

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

  4. monitoring Dec 10, 2024, 09:12 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Dec 11, 2024, 04:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2024 Login issues 28m Activate

Started Dec 09, 2024, 05:39 PM UTC· resolved Dec 09, 2024, 06:07 PM UTC

  1. investigating Dec 09, 2024, 05:39 PM UTC

    We are currently investigating an issue where users are getting logged out of Activate

  2. resolved Dec 09, 2024, 06:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 12, 2024 Issue with VTS Rise Kastle-integrated properties. 153d 21h Rise

Started Nov 12, 2024, 04:23 PM UTC· resolved Apr 15, 2025, 01:28 PM UTC

  1. investigating Nov 12, 2024, 04:23 PM UTC

    We are investigating an issue with user logins affecting customers using a Kastle integration.

  2. monitoring Nov 12, 2024, 05:17 PM UTC

    We have made updates to some affected users for Kastle integrated properties. We are in communication with Kastle and continuing to investigate.

  3. monitoring Nov 12, 2024, 11:52 PM UTC

    We have deployed several fixes to mitigate the impact. We are continuing to monitor and work with Kastle to address the root cause of this issue.

  4. monitoring Jan 07, 2025, 04:17 PM UTC

    We have deployed several fixes to resolve the issue. We are continuing to monitor and work with Kastle to address the root cause.

  5. monitoring Feb 19, 2025, 05:36 PM UTC

    We have implemented a series of fixes to alleviate the impact. We are actively monitoring the situation and collaborating with Kastle to identify and rectify the root cause of this issue. We anticipate a resolution by the end of March.

  6. monitoring Apr 02, 2025, 06:32 PM UTC

    We are continuously monitoring the situation to ensure the fix functions as intended. Our aim is to resolve this incident by April 11th.

  7. resolved Apr 15, 2025, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →