Protime incident

Possible issue with time clockings being denied

Minor Resolved View vendor source →

Protime experienced a minor incident on September 3, 2026 affecting ProTime and Time Terminals, lasting 22h 34m. The incident has been resolved; the full update timeline is below.

Started
Sep 03, 2026, 12:47 PM UTC
Resolved
Sep 04, 2026, 11:22 AM UTC
Duration
22h 34m
Detected by Pingoru
Sep 03, 2026, 12:47 PM UTC

Affected components

ProTimeTime Terminals

Update timeline

  1. investigating Sep 03, 2026, 12:47 PM UTC

    We are currently investigating an issue where time clockings are being denied when no terminal group is linked. we apologize for the inconvenience.

  2. investigating Sep 03, 2026, 02:10 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 03, 2026, 03:22 PM UTC

    We have identified an issue in the new terminal application version(IT11 and IT51) that may cause employees without a configured terminal group in Protime Premium to receive denied time registrations. The impact is currently assessed as very limited. Our teams will now remotely revert the affected terminals to a previous application version. No action is needed from the customer side. We will provide a further update on 04/09/2026. We sincerely apologize for any inconvenience this may cause and appreciate your patience while we work to resolve the issue.

  4. identified Sep 03, 2026, 03:28 PM UTC

    Our teams will now remotely revert the affected terminals to a previous application version. No action is needed from the customer side.

  5. identified Sep 04, 2026, 06:34 AM UTC

    Our teams are currently working closely with our partners to determine the best possible solution. We sincerely apologize for any inconvenience this may cause and appreciate your patience and understanding as we work to resolve the issue.

  6. monitoring Sep 04, 2026, 11:20 AM UTC

    A fix has been implemented on the affected terminals. Regarding the denied clockings, we will contact the impacted customers and provide guidance on how to correct these entries. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding.

  7. resolved Sep 04, 2026, 11:22 AM UTC

    This incident has been resolved.