Protime incident

Possible issue with clocking registration from terminals

Minor Resolved View vendor source →

Protime experienced a minor incident on March 17, 2026 affecting Time Terminals, lasting 10h 3m. The incident has been resolved; the full update timeline is below.

Started
Mar 17, 2026, 12:45 AM UTC
Resolved
Mar 17, 2026, 10:49 AM UTC
Duration
10h 3m
Detected by Pingoru
Mar 17, 2026, 12:45 AM UTC

Affected components

Time Terminals

Update timeline

  1. investigating Mar 17, 2026, 07:48 AM UTC

    We are currently investigating an issue where clockings from terminals are not being registered. Our teams are actively working on this. We apologize for the inconvenience.

  2. investigating Mar 17, 2026, 08:47 AM UTC

    We are working with our partner to identify the root cause. Based on our initial investigation, we do not expect any data loss. This will be fully confirmed once the issue has been identified and resolved.

  3. monitoring Mar 17, 2026, 10:27 AM UTC

    We have received confirmation from our partner that the issue has been resolved. All clockings will be automatically forwarded to Protime Premium; however, this process may take some time to fully complete. We kindly ask for your patience and apologize for the inconvenience. We will continue to closely monitor the situation.

  4. resolved Mar 17, 2026, 10:49 AM UTC

    All clockings should now be visible in Protime Premium, and the service is fully operational again. We would like to thank you for your patience and apologize for the inconvenience caused.