- Detected by Pingoru
- Aug 12, 2026, 01:13 PM UTC
- Resolved
- Aug 12, 2026, 05:20 PM UTC
- Duration
- 4h 6m
Affected: ProTimemyProtimeProTeamExportImportYeartoolProNetProMobileProVisitUserProvisioning
Timeline · 3 updates
-
investigating Aug 12, 2026, 01:13 PM UTC
We are currently investigating this issue.
-
investigating Aug 12, 2026, 01:17 PM UTC
We are continuing to investigate this issue.
-
resolved Aug 13, 2026, 06:54 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2026, 12:14 PM UTC
- Resolved
- Aug 04, 2026, 03:15 PM UTC
- Duration
- 3h 1m
Affected: ProTimeProTeamExportImportYeartoolUserProvisioning
Timeline · 5 updates
-
investigating Aug 04, 2026, 12:14 PM UTC
Our teams are actively working to resolve issue affecting Protime Premium, and restore normal service as quickly as possible. We will provide further updates as soon as additional information becomes available. Users may not be able to see or open the different Protime Premium modules.
-
investigating Aug 04, 2026, 12:15 PM UTC
We are continuing to investigate this issue.
-
identified Aug 04, 2026, 01:31 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 04, 2026, 02:24 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 04, 2026, 03:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 07:12 AM UTC
- Resolved
- Aug 03, 2026, 09:12 AM UTC
- Duration
- 1h 59m
Affected: ProTimeProTeamExportImportYeartool
Timeline · 4 updates
-
investigating Aug 03, 2026, 07:12 AM UTC
Our teams are actively working to resolve issue affecting Protime Premium, and restore normal service as quickly as possible. We will provide further updates as soon as additional information becomes available. Users may not b able to see see the different Premium modules once logged in in Premium.
-
identified Aug 03, 2026, 07:53 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 03, 2026, 08:24 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 03, 2026, 09:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 10:35 AM UTC
- Resolved
- Jul 31, 2026, 02:23 PM UTC
- Duration
- 3h 47m
Affected: myProtime
Timeline · 4 updates
-
investigating Jul 31, 2026, 10:35 AM UTC
Our teams are actively working to resolve issue affecting the request approval functionality on myProtime, and restore normal service as quickly as possible. We will provide further updates as soon as additional information becomes available. Users may experience errors when approving requests on myProtime.
-
identified Jul 31, 2026, 12:00 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 31, 2026, 01:48 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 31, 2026, 02:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2026, 09:58 AM UTC
- Resolved
- Jul 30, 2026, 01:57 PM UTC
- Duration
- 3h 59m
Affected: myProtime planning shift
Timeline · 4 updates
-
investigating Jul 30, 2026, 09:58 AM UTC
We are currently investigating a platform infrastructure issue that may cause intermittent delays in data synchronization and processing within myProtime Planning Shift. Our teams have identified the affected area and are actively working to determine the root cause and implement a permanent solution. In the meantime, we are closely monitoring the platform and taking mitigation measures to minimize the impact. Users may experience delays before recent changes are reflected in the application. We will provide another update as soon as more information becomes available.
-
monitoring Jul 30, 2026, 12:57 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 30, 2026, 01:12 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 30, 2026, 01:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 09:39 AM UTC
- Resolved
- Jul 20, 2026, 11:03 AM UTC
- Duration
- 1h 23m
Affected: ExportImport
Timeline · 3 updates
-
investigating Jul 20, 2026, 09:39 AM UTC
Our teams are actively working to resolve issue affecting the Import and Export modules and restore normal service as quickly as possible. We will provide further updates as soon as additional information becomes available. Users may experience error during the use of Import and Export
-
monitoring Jul 20, 2026, 10:04 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 20, 2026, 11:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 08:29 AM UTC
- Resolved
- Jul 10, 2026, 10:02 AM UTC
- Duration
- 1h 32m
Affected: ProTimemyProtimeExport
Timeline · 4 updates
-
investigating Jul 10, 2026, 08:29 AM UTC
We are currently investigating an issue affecting email-related functionality across several services. Users may experience: - Reports sent using the "Send via Mail" option not being delivered. - Deliveroot retrieval notifications not being received. - Support user notifications not being processed. - Missing email notifications following approval or rejection actions in myProtime. Our teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as soon as more information becomes available.
-
monitoring Jul 10, 2026, 09:10 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 10, 2026, 09:10 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 10, 2026, 10:02 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 05:38 AM UTC
- Resolved
- Jun 19, 2026, 11:13 AM UTC
- Duration
- 1d 5h
Affected: myProtime
Timeline · 4 updates
-
investigating Jun 18, 2026, 07:22 AM UTC
We are currently investigating this issue. We apologize for any inconvenience caused.
-
identified Jun 18, 2026, 08:12 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 18, 2026, 08:38 AM UTC
The issue has been resolved. The backlog is currently being processed, and pending alerts and absence requests will gradually recover over the next few hours.
-
resolved Jun 19, 2026, 11:13 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 09:15 AM UTC
- Resolved
- Jun 12, 2026, 12:10 PM UTC
- Duration
- 2h 55m
Affected: ProVisit Kiosk
Timeline · 2 updates
-
investigating Jun 12, 2026, 09:15 AM UTC
We are currently experiencing a general issue with the visitor access control system. QR codes and visitor PIN codes that are generated are not granting access on our access control systems as expected. Our team is actively investigating the problem and working to resolve it as quickly as possible.
-
resolved Jun 12, 2026, 12:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 03:30 PM UTC
- Resolved
- Jun 17, 2026, 05:59 AM UTC
- Duration
- 6d 14h
Timeline · 4 updates
-
monitoring Jun 10, 2026, 07:39 PM UTC
It's possible end-users may experience connection issues using Planning Shift.
-
investigating Jun 12, 2026, 07:00 AM UTC
Our teams have narrowed down the source of the issue and continue to work on a resolution with the highest priority. We understand the impact of this ongoing disruption and will provide further updates as soon as more information becomes available.
-
monitoring Jun 12, 2026, 08:52 AM UTC
The issue affecting the Planning solution has been resolved, and the service is operating normally again. We sincerely apologize for the disruption and appreciate your patience while our teams worked to restore service. We will continue to monitor the platform closely to ensure stability.
-
resolved Jun 17, 2026, 05:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 07:39 AM UTC
- Resolved
- May 18, 2026, 12:41 PM UTC
- Duration
- 5h 1m
Affected: ProTimemyProtime
Timeline · 5 updates
-
investigating May 18, 2026, 07:39 AM UTC
We are aware that some users are experiencing slowness or issues with clockings not being processed. This problem is currently affecting only a small portion of our users. Our teams are actively investigating the root cause. We sincerely apologize for the inconvenience.
-
investigating May 18, 2026, 08:02 AM UTC
We are continuing to investigate this issue.
-
identified May 18, 2026, 08:49 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 18, 2026, 08:58 AM UTC
A fix has been implemented. Our systems are now reprocessing the backlog of calculations, and any ongoing issues should be automatically resolved within the next hour. We apologize for the inconvenience.
-
resolved May 18, 2026, 12:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 07:29 AM UTC
- Resolved
- May 08, 2026, 10:48 AM UTC
- Duration
- 3h 18m
Affected: ProTime
Timeline · 4 updates
-
investigating May 08, 2026, 07:29 AM UTC
You may encounter an error when trying to access the password reset page. We are currently investigating the issue.
-
identified May 08, 2026, 07:37 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 08, 2026, 07:42 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 08, 2026, 10:48 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 08:53 AM UTC
- Resolved
- May 11, 2026, 06:12 AM UTC
- Duration
- 20d 21h
Timeline · 2 updates
-
investigating Apr 20, 2026, 08:53 AM UTC
Following a recent Windows update, we are aware of an issue in Microsoft Edge that may prevent Excel files from opening when downloaded from myProtime. This issue is caused by Microsoft Edge and is not related to Protime. However we are checking what we can do on our end to mitigate this. Workarounds: - Open the file using Google Chrome or Mozilla Firefox - Use an InPrivate (incognito) window in Microsoft Edge - Re-run the export after changing the file extension from .xlsm to .xls - If the issue persists, please contact your internal IT department to review local security settings (firewall, GPOs, etc.) We apologize for the inconvenience and will continue to monitor the situation. Thank you for your understanding.
-
resolved May 11, 2026, 06:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 08:58 AM UTC
- Resolved
- Apr 17, 2026, 10:59 AM UTC
- Duration
- 2h 1m
Affected: ProTime
Timeline · 2 updates
-
investigating Apr 17, 2026, 08:58 AM UTC
Our DEV teams are currently looking into the translation issue. We apologize for this inconvenience.
-
resolved Apr 17, 2026, 10:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 03:48 PM UTC
- Resolved
- Mar 18, 2026, 04:04 PM UTC
- Duration
- 15m
Affected: myProtime
Timeline · 4 updates
-
investigating Mar 18, 2026, 03:48 PM UTC
We are currently investigating this issue.
-
identified Mar 18, 2026, 03:55 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 18, 2026, 04:02 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 18, 2026, 04:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 01:54 PM UTC
- Resolved
- Mar 17, 2026, 07:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 18, 2026, 01:54 PM UTC
Connection issues affecting some customers on specific databases.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 12:45 AM UTC
- Resolved
- Mar 17, 2026, 10:49 AM UTC
- Duration
- 10h 3m
Affected: Time Terminals
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 07:45 AM UTC
- Resolved
- Mar 23, 2026, 01:22 PM UTC
- Duration
- 7d 5h
Affected: ProTime
Timeline · 4 updates
-
investigating Mar 18, 2026, 02:41 PM UTC
We are currently investigating this issue.
-
monitoring Mar 18, 2026, 02:54 PM UTC
Dear user, We are currently experiencing an issue with work calendars. To resolve this, Please restart the Protime application. Affected customers will receive communication via their Premium session.
-
monitoring Mar 18, 2026, 04:09 PM UTC
Work calendars are functioning normally again. For some customers, there may be missing data since the beginning of the incident. We are currently investigating this and working on a resolution. If any action is required from your side, you will receive direct communication from us. If you do not receive further communication, either you are not impacted or the issue will be resolved automatically. We apologize for the inconvenience this issue may have caused.
-
resolved Mar 23, 2026, 01:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 10:13 AM UTC
- Resolved
- Mar 06, 2026, 10:38 AM UTC
- Duration
- 24m
Affected: myProtime
Timeline · 5 updates
-
investigating Mar 06, 2026, 10:13 AM UTC
We are currently investigating the issue. Since the HUB is unavailable, options such as navigating to your calendar, team calendar, and others are currently not accessible.
-
identified Mar 06, 2026, 10:28 AM UTC
The Hub is available again, but performance is still slow. We are currently investigating/Monitoring the issue.
-
monitoring Mar 06, 2026, 10:35 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Mar 06, 2026, 10:36 AM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 06, 2026, 10:38 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 09:23 AM UTC
- Resolved
- Mar 05, 2026, 10:01 AM UTC
- Duration
- 37m
Affected: myProtime
Timeline · 3 updates
-
identified Mar 05, 2026, 09:23 AM UTC
We are currently experiencing issues with clocking in myProtime. The root cause has been identified, and we are already implementing the fix. We apologize for this.
-
monitoring Mar 05, 2026, 09:35 AM UTC
A fix has been implemented, we are currently monitoring the issue.
-
resolved Mar 05, 2026, 10:01 AM UTC
This incident has been resolved.
Read the full incident report →
Critical February 24, 2026 - Detected by Pingoru
- Feb 24, 2026, 01:35 PM UTC
- Resolved
- Feb 24, 2026, 04:18 PM UTC
- Duration
- 2h 43m
Affected: Import
Timeline · 7 updates
-
investigating Feb 24, 2026, 01:35 PM UTC
We are currently experiencing an issue with the import module where newly added employees are imported with missing data (e.g., personalia files) or are created multiple times instead of once. Our teams are investigating the root cause.
-
investigating Feb 24, 2026, 01:52 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 24, 2026, 02:26 PM UTC
We are receiving additional reports of issues with the import function. To avoid incorrect or incomplete data being created, we will temporarily disable imports until the issue is resolved. We apologize for the inconvenience.
-
investigating Feb 24, 2026, 02:30 PM UTC
We are continuing to investigate this issue.
-
identified Feb 24, 2026, 02:35 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Feb 24, 2026, 03:48 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Feb 24, 2026, 04:18 PM UTC
The issue has been resolved. Please log out, fully close your browser, and reopen your session to ensure the import function works as expected. We sincerely apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 09:36 AM UTC
- Resolved
- Feb 20, 2026, 02:31 PM UTC
- Duration
- 4h 55m
Affected: ExportImport
Timeline · 6 updates
-
investigating Feb 20, 2026, 09:36 AM UTC
We are currently investigating an error that some users are encountering when using the import/Export module.
-
investigating Feb 20, 2026, 09:42 AM UTC
We are continuing to investigate this issue.
-
investigating Feb 20, 2026, 09:42 AM UTC
We got confirmation that Export module is also impacted.
-
identified Feb 20, 2026, 10:24 AM UTC
We have identified the issue and are currently working on a hotfix.
-
identified Feb 20, 2026, 02:08 PM UTC
We have implemented the fix for the import module. The export module is still affected, but only for automatic exports.
-
resolved Feb 20, 2026, 02:31 PM UTC
We fixed the issue for the export.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 01:00 AM UTC
- Resolved
- Feb 10, 2026, 06:36 AM UTC
- Duration
- 5h 35m
Affected: myProtime
Timeline · 3 updates
-
investigating Feb 10, 2026, 06:24 AM UTC
We are currently investigating the issue. Since the HUB is unavailable, options such as navigating to your calendar, team calendar, and others are currently not accessible.
-
identified Feb 10, 2026, 06:29 AM UTC
The Hub is available again, but performing slowly. We are currently investigating.
-
resolved Feb 10, 2026, 06:36 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 07:00 AM UTC
- Resolved
- Dec 18, 2025, 02:43 PM UTC
- Duration
- 7h 43m
Affected: myProtime
Timeline · 2 updates
-
investigating Jan 30, 2026, 02:59 PM UTC
We have received reports of anomalies in MyProtime, including some incorrect alerts. For most customers there is no impact, but we do see an increase in customer reports. Our team is currently investigating the issue, and we sincerely apologize for the inconvenience.
-
resolved Jan 30, 2026, 02:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 07:00 AM UTC
- Resolved
- Dec 15, 2025, 11:48 AM UTC
- Duration
- 4h 48m
Affected: myProtimeProVisit
Timeline · 2 updates
-
investigating Jan 30, 2026, 02:58 PM UTC
We are currently experiencing issues affecting calculations, absence requests, Premium synchronization, and occasional “Access Denied” errors in ProVisit. Our team is actively working on a fix, and we sincerely apologize for the inconvenience.
-
resolved Jan 30, 2026, 02:58 PM UTC
This incident has been resolved.
Read the full incident report →