Protime incident
Possible issue with clocking registration from terminals
Resolved after 10 hours 3 minutes, affecting Time Terminals, on March 17, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
- 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.
- 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.
Your product runs on more than Protime
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services