TimeClock Plus status history
Current state: operational — “All Systems Operational” per https://status.tcpsoftware.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do TimeClock Plus incidents last?
From 14 incidents with a vendor-posted start and resolve time. Longest on record: TimeClock Plus Application Outage — 4.3 days (2026-02-17 12:39 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (15)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-26 16:11 UTC | TimeClock Plus Application Disruption | resolved | none | 4 h 50 min |
| 2026-06-22 14:24 UTC | TimeClock Plus Application Performance Degradation | resolved | none | 24 h 42 min |
| 2026-05-26 18:48 UTC | TimeClock Plus Application Performance Degradation | resolved | major | 30 min |
| 2026-05-18 13:05 UTC | TimeClock Plus Application Performance Degradation | resolved | minor | 4 h 52 min |
| 2026-05-08 00:47 UTC | Application Performance Degradation/Outage | resolved | major | 3 d 12 h |
| 2026-02-23 23:05 UTC | TimeClock Plus Application Performance Degradation | resolved | minor | 15 h 43 min |
| 2026-02-17 12:39 UTC | TimeClock Plus Application Outage | resolved | critical | 4 d 6 h |
| 2026-02-03 15:42 UTC | TimeClock Plus Application Outage | resolved | major | 3 h 22 min |
| 2025-12-21 19:19 UTC | Aladtec Application Outage | resolved | major | 1 h 36 min |
| 2025-10-08 16:32 UTC | TimeClock Plus PrismHR2 Application Disruption | resolved | major | 41 min |
| 2025-10-02 14:42 UTC | Degraded Application Performance | resolved | minor | 1 h 57 min |
| 2025-09-27 09:32 UTC | Aladtec Outage | resolved | maintenance | 1 h 44 min |
| 2025-09-02 00:08 UTC | Aladtec Outage | resolved | none | 24 min |
| 2025-08-22 05:04 UTC | TimeClock Plus Group10-2 Application Disruption | resolved | major | 17 min |
| 2025-08-21 18:07 UTC | Service Provider Degradation | resolved | minor | 2 h 02 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch TimeClock Plus with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"timeclock-plus"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}