История сбоев Timeclock Plus

1. 26 августа 2026 г. в 16:11 UTCinvestigating

   Клиенты испытывают ошибки при использовании функции «Период экспорта». В настоящее время мы изучаем первопричину и будем предоставлять обновления по мере поступления новой информации.

2. 26 августа 2026 г. в 16:30 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

3. 26 августа 2026 г. в 17:02 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

4. 26 августа 2026 г. в 21:01 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 22 июня 2026 г. в 14:24 UTCinvestigating

   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. 22 июня 2026 г. в 14:29 UTCidentified

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

3. 22 июня 2026 г. в 17:00 UTCmonitoring

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

4. 23 июня 2026 г. в 15:07 UTCresolved

   This incident has been resolved.

1. 26 мая 2026 г. в 18:48 UTCinvestigating

   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. 26 мая 2026 г. в 19:18 UTCmonitoring

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

3. 26 мая 2026 г. в 19:18 UTCresolved

   This incident has been resolved.

1. 18 мая 2026 г. в 13:05 UTCinvestigating

   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. 18 мая 2026 г. в 14:17 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 мая 2026 г. в 14:55 UTCinvestigating

   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. 18 мая 2026 г. в 15:35 UTCinvestigating

   Maintenance has been completed. We are verifying application performance.

5. 18 мая 2026 г. в 15:41 UTCidentified

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

6. 18 мая 2026 г. в 15:58 UTCmonitoring

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

7. 18 мая 2026 г. в 17:58 UTCresolved

   This incident has been resolved.

1. 8 мая 2026 г. в 00:47 UTCinvestigating

   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. 8 мая 2026 г. в 01:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 8 мая 2026 г. в 13:55 UTCidentified

   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. 8 мая 2026 г. в 17:08 UTCidentified

   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. 8 мая 2026 г. в 19:01 UTCidentified

   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. 8 мая 2026 г. в 20:54 UTCidentified

   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. 8 мая 2026 г. в 22:58 UTCmonitoring

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

8. 9 мая 2026 г. в 21:18 UTCmonitoring

   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. 11 мая 2026 г. в 13:33 UTCresolved

   This incident has been resolved.

1. 23 февраля 2026 г. в 23:05 UTCinvestigating

   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. 24 февраля 2026 г. в 03:10 UTCidentified

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

3. 24 февраля 2026 г. в 03:46 UTCmonitoring

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

4. 24 февраля 2026 г. в 14:48 UTCresolved

   This incident has been resolved.

1. 17 февраля 2026 г. в 12:39 UTCinvestigating

   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. 17 февраля 2026 г. в 13:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 февраля 2026 г. в 14:41 UTCinvestigating

   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. 17 февраля 2026 г. в 23:08 UTCinvestigating

   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. 18 февраля 2026 г. в 14:32 UTCidentified

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

6. 19 февраля 2026 г. в 14:19 UTCmonitoring

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

7. 21 февраля 2026 г. в 19:14 UTCresolved

   This incident has been resolved.

1. 3 февраля 2026 г. в 15:42 UTCinvestigating

   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. 3 февраля 2026 г. в 15:42 UTCidentified

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

3. 3 февраля 2026 г. в 16:01 UTCmonitoring

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

4. 3 февраля 2026 г. в 16:41 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 3 февраля 2026 г. в 19:05 UTCresolved

   This incident has been resolved.

1. 21 декабря 2025 г. в 19:19 UTCinvestigating

   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. 21 декабря 2025 г. в 19:43 UTCidentified

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

3. 21 декабря 2025 г. в 20:39 UTCidentified

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

4. 21 декабря 2025 г. в 20:48 UTCmonitoring

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

5. 21 декабря 2025 г. в 20:56 UTCresolved

   This incident has been resolved.

1. 8 октября 2025 г. в 16:32 UTCidentified

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

2. 8 октября 2025 г. в 17:08 UTCmonitoring

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

3. 8 октября 2025 г. в 17:13 UTCresolved

   This incident has been resolved.

1. 2 октября 2025 г. в 14:42 UTCinvestigating

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

2. 2 октября 2025 г. в 15:02 UTCmonitoring

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

3. 2 октября 2025 г. в 16:39 UTCresolved

   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. 2 сентября 2025 г. в 00:08 UTCinvestigating

   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. 2 сентября 2025 г. в 00:32 UTCresolved

   This incident has been resolved.

1. 22 августа 2025 г. в 05:04 UTCinvestigating

   We are currently investigating this issue.

2. 22 августа 2025 г. в 05:10 UTCidentified

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

3. 22 августа 2025 г. в 05:16 UTCmonitoring

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

4. 22 августа 2025 г. в 05:21 UTCresolved

   This incident has been resolved.

1. 21 августа 2025 г. в 18:07 UTCinvestigating

   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. 21 августа 2025 г. в 18:35 UTCidentified

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

3. 21 августа 2025 г. в 19:46 UTCmonitoring

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

4. 21 августа 2025 г. в 20:09 UTCresolved

   This incident has been resolved.

1. 11 августа 2025 г. в 22:07 UTCinvestigating

   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. 11 августа 2025 г. в 22:28 UTCidentified

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

3. 11 августа 2025 г. в 23:26 UTCmonitoring

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

4. 11 августа 2025 г. в 23:31 UTCresolved

   This incident has been resolved.

1. 1 августа 2025 г. в 15:37 UTCinvestigating

   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. 1 августа 2025 г. в 17:02 UTCidentified

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

3. 1 августа 2025 г. в 17:09 UTCmonitoring

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

4. 1 августа 2025 г. в 19:00 UTCresolved

   This incident has been resolved.

1. 29 июля 2025 г. в 17:31 UTCinvestigating

   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. 29 июля 2025 г. в 17:44 UTCidentified

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

3. 29 июля 2025 г. в 17:54 UTCmonitoring

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

4. 29 июля 2025 г. в 18:27 UTCresolved

   This incident has been resolved.

1. 24 июня 2025 г. в 11:38 UTCinvestigating

   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. 24 июня 2025 г. в 12:10 UTCidentified

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

3. 24 июня 2025 г. в 12:12 UTCmonitoring

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

4. 24 июня 2025 г. в 13:00 UTCresolved

   This incident has been resolved.

1. 18 июня 2025 г. в 16:40 UTCinvestigating

   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. 18 июня 2025 г. в 16:55 UTCidentified

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

3. 18 июня 2025 г. в 17:39 UTCmonitoring

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

4. 18 июня 2025 г. в 20:24 UTCresolved

   This incident has been resolved.

1. 13 июня 2025 г. в 14:01 UTCinvestigating

   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. 13 июня 2025 г. в 14:10 UTCidentified

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

3. 13 июня 2025 г. в 14:22 UTCmonitoring

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

4. 13 июня 2025 г. в 14:24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 13 июня 2025 г. в 14:32 UTCresolved

   This incident has been resolved.