Timeclock Plus 中断历史

1. 2026年8月26日 UTC 16:11investigating

   客户在使用"期间导出"功能时出现错误. 我们目前正在调查根源,并将在获得新信息后提供最新情况.

2. 2026年8月26日 UTC 16:30identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年8月26日 UTC 17:02monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年8月26日 UTC 21:01resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月22日 UTC 14:24investigating

   We're experiencing issues with our TimeClock Plus Time and Attendance application affecting a subset of users. The disruption is related to our network infrastructure layer and is not isolated to TCP's systems. Our team is actively working with our providers to resolve this. We will provide more details as soon as more information becomes available.

2. 2026年6月22日 UTC 14:29identified

   The issue has been identified and a fix is being implemented.

3. 2026年6月22日 UTC 17:00monitoring

   A fix has been implemented and we are monitoring the results.

4. 2026年6月23日 UTC 15:07resolved

   This incident has been resolved.

1. 2026年5月26日 UTC 18:48investigating

   We’re experiencing issues with our TimeClock Plus Time and Attendance application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2026年5月26日 UTC 19:18monitoring

   A fix has been implemented and we are monitoring the results.

3. 2026年5月26日 UTC 19:18resolved

   This incident has been resolved.

1. 2026年5月18日 UTC 13:05investigating

   We’re experiencing issues with our TimeClock Plus Time and Attendance application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2026年5月18日 UTC 14:17investigating

   We are continuing to investigate this issue.

3. 2026年5月18日 UTC 14:55investigating

   We will be performing urgent maintenance between 10:15AM CDT and 10:45AM CDT. During this time, customers will experience a brief period of downtime.

4. 2026年5月18日 UTC 15:35investigating

   Maintenance has been completed. We are verifying application performance.

5. 2026年5月18日 UTC 15:41identified

   The issue has been identified and a fix is being implemented.

6. 2026年5月18日 UTC 15:58monitoring

   A fix has been implemented and we are monitoring the results.

7. 2026年5月18日 UTC 17:58resolved

   This incident has been resolved.

1. 2026年5月8日 UTC 00:47investigating

   We are aware of reports of elevated response times and intermittent errors affecting some users. We have identified the issue as stemming from our infrastructure provider and are actively monitoring while they work toward resolution. Updates to follow.

2. 2026年5月8日 UTC 01:52investigating

   We are continuing to investigate this issue.

3. 2026年5月8日 UTC 13:55identified

   We are continuing to work through our restore processes following an outage declared by AWS which they are still working to address. The issue was caused by a cooling system failure in one of their Availability Zones, which has impacted our infrastructure. Our team is actively working through restoration efforts to bring our services back. We sincerely apologize for the disruption and thank you for your continued patience.

4. 2026年5月8日 UTC 17:08identified

   We are continuing to work through our restore processes following an outage declared by AWS which they are still working to address. The issue was caused by a cooling system failure in one of their Availability Zones, which has impacted our infrastructure. Our team is actively working through restoration efforts to bring our services back.

5. 2026年5月8日 UTC 19:01identified

   Access has been restored for customers on Prod60. Some customers may experience 1-3 hours of data loss depending on working hours. If you have experienced data loss, please reach out to our support team at 325-223-9300 or [email protected] for assistance.

6. 2026年5月8日 UTC 20:54identified

   Access has been restored for most customers on Prod25. We are still working to restore access for a subset of customers. Some customers will be subject to data loss due to the outage. If you have experienced data loss, please reach out to our support team at 325-223-9300 or [email protected] for assistance.

7. 2026年5月8日 UTC 22:58monitoring

   All systems are working normally. We will continue to monitor performance over the weekend. Additional information will posted as it becomes available.

8. 2026年5月9日 UTC 21:18monitoring

   We will be performing additional maintenance on Prod25 that will result in a short period of downtime (10-15 minutes). This will be completed in the next 1-2 hours. A follow-up message will be posted when the maintenance begins and when the maintenance is completed.

9. 2026年5月11日 UTC 13:33resolved

   This incident has been resolved.

1. 2026年2月23日 UTC 23:05investigating

   We’re experiencing issues with our TimeClock Plus Time and Attendance application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2026年2月24日 UTC 03:10identified

   The issue has been identified and a fix is being implemented.

3. 2026年2月24日 UTC 03:46monitoring

   A fix has been implemented and we are monitoring the results.

4. 2026年2月24日 UTC 14:48resolved

   This incident has been resolved.

1. 2026年2月17日 UTC 12:39investigating

   We’re experiencing issues with our TimeClock Plus Time and Attendance application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2026年2月17日 UTC 13:58investigating

   We are continuing to investigate this issue.

3. 2026年2月17日 UTC 14:41investigating

   The TimeClock Plus application performance has stabilized. We are continuing to investigate the root cause and will provide further updates as information becomes available.

4. 2026年2月17日 UTC 23:08investigating

   The TimeClock Plus application performance remains stable. We are continuing to investigate the root cause and will provide further updates as information becomes available.

5. 2026年2月18日 UTC 14:32identified

   The issue has been identified and a fix is being implemented.

6. 2026年2月19日 UTC 14:19monitoring

   A fix has been implemented and we are monitoring the results.

7. 2026年2月21日 UTC 19:14resolved

   This incident has been resolved.

1. 2026年2月3日 UTC 15:42investigating

   We’re experiencing issues with our TimeClock Plus Time and Attendance application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2026年2月3日 UTC 15:42identified

   The issue has been identified and a fix is being implemented.

3. 2026年2月3日 UTC 16:01monitoring

   A fix has been implemented and we are monitoring the results.

4. 2026年2月3日 UTC 16:41monitoring

   We are continuing to monitor for any further issues.

5. 2026年2月3日 UTC 19:05resolved

   This incident has been resolved.

1. 2025年12月21日 UTC 19:19investigating

   We are experiencing issues with our Aladtec Scheduling application. A subset of users is impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2025年12月21日 UTC 19:43identified

   The issue has been identified and a fix is being implemented.

3. 2025年12月21日 UTC 20:39identified

   We are continuing to work on a fix for this issue.

4. 2025年12月21日 UTC 20:48monitoring

   A fix has been implemented and we are monitoring the results.

5. 2025年12月21日 UTC 20:56resolved

   This incident has been resolved.

1. 2025年10月8日 UTC 16:32identified

   The issue has been identified and a fix is being implemented.

2. 2025年10月8日 UTC 17:08monitoring

   A fix has been implemented and we are monitoring the results.

3. 2025年10月8日 UTC 17:13resolved

   This incident has been resolved.

1. 2025年10月2日 UTC 14:42investigating

   We are currently experiencing degraded performance. Our team is actively investigating the issue and working to restore normal service as quickly as possible.

2. 2025年10月2日 UTC 15:02monitoring

   A fix has been implemented and we are monitoring the results.

3. 2025年10月2日 UTC 16:39resolved

   This incident has been resolved. Degraded performance was due to an issue with our Web Application Firewall provider. More information can be found here: https://www.cloudflarestatus.com/incidents/nz9nlcyz4qy4

1. 2025年9月2日 UTC 00:08investigating

   We are experiencing issues with our Aladtec Scheduling application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2025年9月2日 UTC 00:32resolved

   This incident has been resolved.

1. 2025年8月22日 UTC 05:04investigating

   We are currently investigating this issue.

2. 2025年8月22日 UTC 05:10identified

   The issue has been identified and a fix is being implemented.

3. 2025年8月22日 UTC 05:16monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年8月22日 UTC 05:21resolved

   This incident has been resolved.

1. 2025年8月21日 UTC 18:07investigating

   We are currently experiencing service degradation and elevated error rates impacting multiple services. This is due to a reported issue with our web application firewall provider. We apologize for any disruption this may be causing to your workflow. We will provide our next update as new information becomes available.

2. 2025年8月21日 UTC 18:35identified

   Our Web Application Firewall provider has identified the issue and is working to implement a fix.

3. 2025年8月21日 UTC 19:46monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年8月21日 UTC 20:09resolved

   This incident has been resolved.

1. 2025年8月11日 UTC 22:07investigating

   We are investigating reports of customers experiencing automation service disruption. We are working to identify the issue and the impact across our server fleet.

2. 2025年8月11日 UTC 22:28identified

   The issue has been identified and a fix is being implemented.

3. 2025年8月11日 UTC 23:26monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年8月11日 UTC 23:31resolved

   This incident has been resolved.

1. 2025年8月1日 UTC 15:37investigating

   We are experiencing issues with our Aladtec Scheduling application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2025年8月1日 UTC 17:02identified

   The issue has been identified and a fix is being implemented.

3. 2025年8月1日 UTC 17:09monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年8月1日 UTC 19:00resolved

   This incident has been resolved.

1. 2025年7月29日 UTC 17:31investigating

   We’re experiencing issues with our TimeClock Plus Time and Attendance application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2025年7月29日 UTC 17:44identified

   The issue has been identified and a fix is being implemented.

3. 2025年7月29日 UTC 17:54monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年7月29日 UTC 18:27resolved

   This incident has been resolved.

1. 2025年6月24日 UTC 11:38investigating

   We are experiencing issues with our Aladtec Scheduling application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available. Components affected: secure15.aladtec.com

2. 2025年6月24日 UTC 12:10identified

   The issue has been identified and a fix is being implemented.

3. 2025年6月24日 UTC 12:12monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年6月24日 UTC 13:00resolved

   This incident has been resolved.

1. 2025年6月18日 UTC 16:40investigating

   We’re experiencing issues with our TimeClock Plus Time and Attendance application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2025年6月18日 UTC 16:55identified

   The issue has been identified and a fix is being implemented.

3. 2025年6月18日 UTC 17:39monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年6月18日 UTC 20:24resolved

   This incident has been resolved.

1. 2025年6月13日 UTC 14:01investigating

   We’re experiencing issues with our Aladtec Scheduling application. A subset of users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.

2. 2025年6月13日 UTC 14:10identified

   The issue has been identified and a fix is being implemented.

3. 2025年6月13日 UTC 14:22monitoring

   A fix has been implemented and we are monitoring the results.

4. 2025年6月13日 UTC 14:24monitoring

   We are continuing to monitor for any further issues.

5. 2025年6月13日 UTC 14:32resolved

   This incident has been resolved.