Protime Outage History

We are currently experiencing an issue affecting the availability and performance of most Protime applications. You may notice that some services are not reachable or are responding slowly. Our technical team is actively working on resolving the issue with the highest priority. At this time, we are scaling up our infrastructure capacity to help restore normal service levels as quickly as possible. We sincerely apologize for the inconvenience and appreciate your patience and understanding. Next update will be provided around 9:00

Response times across all applications have been normalized. Root cause analysis is being performed, but all services should be back up and running at normal operating capacity.

We are investigating an issue that in rare cases our hardware is not getting the latest update, which should happen automatically. We have a manual workaround in place when issues are being reported, so don't hesitate to reach out. We are working hard on fixing the automatic update process.

Customers on Database 20 may experience performance issues, including slowness with refreshing the day program in ProTeam/myProtime. Calculations are currently in the backlog and will be processed as soon as possible. Our team is currently investigating the root cause.

myProtime files is down due to a technical issue on one of our servers. We are working hard to get this back online asap.

myProtime and Protime Premium show performance issues on June 02, 2025 for about 1.5 hours. This was caused by a high load of usage of our services, and has been solved by splitting traffic between our datacenters.

Multiple customers are encountering errors when making bookings on their terminals. We're actively investigating the issue and will provide a solution asap.

myProtime mail server seems to be down starting 2025-05-11 14:57:00 No notification or invitation emails are being sent. We are actively working on solving this issue.

During planned network maintenance we stumbled upon unforeseen downtime for myProtime. The issue was solved swiftly.

We are currently experiencing an issue where ProVisit Access is down. Our team is actively working to resolve the issue as quickly as possible.

We are currently experiencing an issue where terminal clockings are not being processed in real-time. Please be assured that all bookings are being securely stored and no data has been lost. Our team is actively working to resolve the issue as quickly as possible.

You might experience a 404 error when trying to reach our Premium modules (Protime, Import, Export, Proteam, etc…). This issue can usually be resolved by refreshing your page, sometimes multiple times. We understand that this may be inconvenient, but we already have a solution ready to be deployed. Tonight (10/03/2025 – 8pm CET), we will upgrade our servers to fix this bug. Everything should be resolved by tomorrow.

Our myProtime Visitors app is currently down due to a 502 server error, which is affecting visitor registrations and pre-registrations. Our technical team is working on a fix and we’ll update you once it's resolved. We apologize for the inconvenience and appreciate your patience.

Hi, we are currently experiencing issues with myProtime Files. Our technical team is investigating the issue and working on a solution

It is possible that some clockings from the time and access terminals are delayed. However, rest assure that none of the clockings will be lost. These clockings remain saved in the terminals themselves until they're sent. We apologize for any inconvenience this may cause and appreciate your patience and understanding. If you have any questions or require further assistance, please do not hesitate to contact our support team.

We have identified an issue with some hardware terminals that experience timeout issues while using Online Access. Please note that this does not affect the recording of clocking data; all clockings are saved correctly in Protime. We are actively investigating and working to resolve this. Thank you for your patience and understanding.

We are currently experiencing an issue where clockings might not immediately synchronize into ProTime. All clockings are safely stored within the terminal and will synchronize as soon as the connection is restored. Our team is actively working to resolve this as quickly as possible.

Multiple servers from the same host rebooted unexpectedly. The issue was quickly resolved, and all systems are operational again. We are monitoring the system closely and investigating the root cause to prevent recurrence.

Clockings might not synchronise into ProTime. Clockings will be stored within the terminal until connection is restored. We are working on it.

We are currently experiencing synchronization issues between myProtime and Protime Premium, resulting in data/alerts in myProtime appearing outdated. Our development teams are actively investigating the issue. Next update: 11AM CET