Historial de interrupciones de Timeclock Plus

1. August 26, 2026 at 4:11 PM UTCinvestigating

   Los clientes están experimentando errores al utilizar la función Period Export. Actualmente estamos investigando la causa raíz y proporcionaremos actualizaciones a medida que se disponga de nueva información.

2. August 26, 2026 at 4:30 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. August 26, 2026 at 5:02 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. August 26, 2026 at 9:01 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 22, 2026 at 2:24 PM 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. June 22, 2026 at 2:29 PM UTCidentified

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

3. June 22, 2026 at 5:00 PM UTCmonitoring

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

4. June 23, 2026 at 3:07 PM UTCresolved

   This incident has been resolved.

1. May 26, 2026 at 6:48 PM 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. May 26, 2026 at 7:18 PM UTCmonitoring

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

3. May 26, 2026 at 7:18 PM UTCresolved

   This incident has been resolved.

1. May 18, 2026 at 1:05 PM 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. May 18, 2026 at 2:17 PM UTCinvestigating

   We are continuing to investigate this issue.

3. May 18, 2026 at 2:55 PM 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. May 18, 2026 at 3:35 PM UTCinvestigating

   Maintenance has been completed. We are verifying application performance.

5. May 18, 2026 at 3:41 PM UTCidentified

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

6. May 18, 2026 at 3:58 PM UTCmonitoring

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

7. May 18, 2026 at 5:58 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 12:47 AM 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. May 8, 2026 at 1:52 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 8, 2026 at 1:55 PM 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. May 8, 2026 at 5:08 PM 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. May 8, 2026 at 7:01 PM 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. May 8, 2026 at 8:54 PM 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. May 8, 2026 at 10:58 PM UTCmonitoring

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

8. May 9, 2026 at 9:18 PM 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. May 11, 2026 at 1:33 PM UTCresolved

   This incident has been resolved.

1. February 23, 2026 at 11:05 PM 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. February 24, 2026 at 3:10 AM UTCidentified

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

3. February 24, 2026 at 3:46 AM UTCmonitoring

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

4. February 24, 2026 at 2:48 PM UTCresolved

   This incident has been resolved.

1. February 17, 2026 at 12:39 PM 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. February 17, 2026 at 1:58 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 17, 2026 at 2:41 PM 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. February 17, 2026 at 11:08 PM 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. February 18, 2026 at 2:32 PM UTCidentified

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

6. February 19, 2026 at 2:19 PM UTCmonitoring

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

7. February 21, 2026 at 7:14 PM UTCresolved

   This incident has been resolved.

1. February 3, 2026 at 3:42 PM 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. February 3, 2026 at 3:42 PM UTCidentified

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

3. February 3, 2026 at 4:01 PM UTCmonitoring

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

4. February 3, 2026 at 4:41 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. February 3, 2026 at 7:05 PM UTCresolved

   This incident has been resolved.

1. December 21, 2025 at 7:19 PM 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. December 21, 2025 at 7:43 PM UTCidentified

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

3. December 21, 2025 at 8:39 PM UTCidentified

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

4. December 21, 2025 at 8:48 PM UTCmonitoring

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

5. December 21, 2025 at 8:56 PM UTCresolved

   This incident has been resolved.

1. October 8, 2025 at 4:32 PM UTCidentified

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

2. October 8, 2025 at 5:08 PM UTCmonitoring

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

3. October 8, 2025 at 5:13 PM UTCresolved

   This incident has been resolved.

1. October 2, 2025 at 2:42 PM 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. October 2, 2025 at 3:02 PM UTCmonitoring

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

3. October 2, 2025 at 4:39 PM 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. September 2, 2025 at 12:08 AM 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. September 2, 2025 at 12:32 AM UTCresolved

   This incident has been resolved.

1. August 22, 2025 at 5:04 AM UTCinvestigating

   We are currently investigating this issue.

2. August 22, 2025 at 5:10 AM UTCidentified

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

3. August 22, 2025 at 5:16 AM UTCmonitoring

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

4. August 22, 2025 at 5:21 AM UTCresolved

   This incident has been resolved.

1. August 21, 2025 at 6:07 PM 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. August 21, 2025 at 6:35 PM UTCidentified

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

3. August 21, 2025 at 7:46 PM UTCmonitoring

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

4. August 21, 2025 at 8:09 PM UTCresolved

   This incident has been resolved.

1. August 11, 2025 at 10:07 PM 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. August 11, 2025 at 10:28 PM UTCidentified

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

3. August 11, 2025 at 11:26 PM UTCmonitoring

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

4. August 11, 2025 at 11:31 PM UTCresolved

   This incident has been resolved.

1. August 1, 2025 at 3:37 PM 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. August 1, 2025 at 5:02 PM UTCidentified

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

3. August 1, 2025 at 5:09 PM UTCmonitoring

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

4. August 1, 2025 at 7:00 PM UTCresolved

   This incident has been resolved.

1. July 29, 2025 at 5:31 PM 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. July 29, 2025 at 5:44 PM UTCidentified

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

3. July 29, 2025 at 5:54 PM UTCmonitoring

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

4. July 29, 2025 at 6:27 PM UTCresolved

   This incident has been resolved.

1. June 24, 2025 at 11:38 AM 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. June 24, 2025 at 12:10 PM UTCidentified

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

3. June 24, 2025 at 12:12 PM UTCmonitoring

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

4. June 24, 2025 at 1:00 PM UTCresolved

   This incident has been resolved.

1. June 18, 2025 at 4:40 PM 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. June 18, 2025 at 4:55 PM UTCidentified

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

3. June 18, 2025 at 5:39 PM UTCmonitoring

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

4. June 18, 2025 at 8:24 PM UTCresolved

   This incident has been resolved.

1. June 13, 2025 at 2:01 PM 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. June 13, 2025 at 2:10 PM UTCidentified

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

3. June 13, 2025 at 2:22 PM UTCmonitoring

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

4. June 13, 2025 at 2:24 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. June 13, 2025 at 2:32 PM UTCresolved

   This incident has been resolved.