VTS incident

HID readers not recognizing Bluetooth Low Energy (BLE) credentials

Minor Resolved View vendor source →

VTS experienced a minor incident on April 11, 2025 affecting Integrations, lasting 177d 21h. The incident has been resolved; the full update timeline is below.

Started
Apr 11, 2025, 03:20 PM UTC
Resolved
Oct 06, 2025, 01:17 PM UTC
Duration
177d 21h
Detected by Pingoru
Apr 11, 2025, 03:20 PM UTC

Affected components

Integrations

Update timeline

  1. investigating Apr 11, 2025, 03:20 PM UTC

    We are currently investigating an issue causing some of the BLE credentials to not work with the readers

  2. investigating Apr 23, 2025, 07:23 PM UTC

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

  3. investigating Apr 24, 2025, 02:09 PM UTC

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

  4. investigating Apr 24, 2025, 04:53 PM UTC

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

  5. investigating Apr 24, 2025, 10:36 PM UTC

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

  6. investigating Apr 25, 2025, 01:48 PM UTC

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

  7. investigating Apr 25, 2025, 06:45 PM UTC

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

  8. investigating Apr 25, 2025, 09:37 PM UTC

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

  9. investigating Apr 28, 2025, 01:45 AM UTC

    We continue to investigate the root cause of this issue. We will have an update on Monday.

  10. investigating Apr 28, 2025, 02:15 PM UTC

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

  11. investigating Apr 28, 2025, 07:21 PM UTC

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

  12. investigating Apr 28, 2025, 08:32 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  13. investigating Apr 29, 2025, 01:54 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  14. investigating Apr 29, 2025, 06:10 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  15. investigating Apr 30, 2025, 02:14 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  16. investigating Apr 30, 2025, 07:22 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  17. investigating May 01, 2025, 02:30 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  18. investigating May 01, 2025, 10:37 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  19. investigating May 02, 2025, 01:48 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  20. investigating May 05, 2025, 02:02 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  21. investigating May 05, 2025, 08:17 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  22. investigating May 06, 2025, 02:11 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID

  23. investigating May 06, 2025, 09:52 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  24. investigating May 07, 2025, 02:19 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  25. investigating May 07, 2025, 09:41 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  26. investigating May 08, 2025, 02:33 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  27. investigating May 09, 2025, 01:44 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  28. investigating May 12, 2025, 03:55 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  29. investigating May 12, 2025, 09:11 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  30. investigating May 13, 2025, 04:08 PM UTC

    We continue to investigate the root cause of this issue in collaboration with HID.

  31. investigating May 13, 2025, 09:23 PM UTC

    We have identified the root cause of this issue. We are evaluating full and partial resolution measures.

  32. investigating May 14, 2025, 03:25 PM UTC

    We have identified the root cause of this issue. We are evaluating full and partial resolution measures.

  33. investigating May 14, 2025, 08:50 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  34. investigating May 15, 2025, 01:49 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  35. investigating May 16, 2025, 09:18 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  36. investigating May 20, 2025, 04:27 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  37. investigating May 20, 2025, 09:39 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  38. investigating May 21, 2025, 11:30 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  39. investigating May 22, 2025, 02:36 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact

  40. investigating May 22, 2025, 08:44 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact

  41. investigating May 26, 2025, 02:21 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact

  42. investigating May 27, 2025, 01:31 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact

  43. investigating May 27, 2025, 01:32 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  44. investigating May 28, 2025, 01:55 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  45. investigating May 29, 2025, 02:54 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact.

  46. investigating Jun 02, 2025, 06:44 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact

  47. investigating Jun 05, 2025, 09:02 PM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact

  48. investigating Jun 09, 2025, 11:58 AM UTC

    We have identified the root cause of this issue. During this time, we have implemented temporary measures to mitigate the impact

  49. investigating Sep 18, 2025, 05:19 PM UTC

    We have identified the root cause and have implemented a permanent resolution, but are monitoring for a while, just in case.

  50. resolved Oct 06, 2025, 01:17 PM UTC

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