Is TimeClock Plus down?
Last checked 10m agoNo incidents right now.
TimeClock Plus is operational right now. Last checked 10m ago; the most recent incident resolved 2d ago.
Real-time TimeClock Plus status, recent outages, and incident history — pulled directly from TimeClock Plus's official status page at https://status.tcpsoftware.com every 5 minutes. Pingoru tracks 67 TimeClock Plus services and has captured 18 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment TimeClock Plus reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Group1.tcplusondemand.comGroup2.tcplusondemand.comGroup3.tcplusondemand.comGroup4.tcplusondemand.comGroup5.tcplusondemand.comGroup10.tcplusondemand.comGroup10-2.tcplusondemand.comGroup12.tcplusondemand.comProd01.tcplusondemand.comProd02.tcplusondemand.com
Timeline · 4 updates
- investigating · Aug 26, 2026, 04:11 PM UTC
Customers are experiencing errors when using the Period Export feature. We are currently investigating the root cause and will provide updates as new information becomes available.
- identified · Aug 26, 2026, 04:30 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Aug 26, 2026, 05:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Aug 26, 2026, 09:01 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Group1.tcplusondemand.comGroup2.tcplusondemand.comGroup3.tcplusondemand.comHumanity SchedulingGroup4.tcplusondemand.comAladtec SchedulingGroup5.tcplusondemand.comScheduleAnywhere SchedulingGroup10.tcplusondemand.comInstaSub Substitute Management
Timeline · 4 updates
- investigating · Jun 22, 2026, 02:24 PM UTC
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.
- identified · Jun 22, 2026, 02:29 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jun 22, 2026, 05:00 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 23, 2026, 03:07 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started Aug 26, 2026, 04:11 PM UTC · Resolved Aug 26, 2026, 09:01 PM UTC · 4h 50m
- Started Jun 22, 2026, 02:24 PM UTC · Resolved Jun 23, 2026, 03:07 PM UTC · 1d