Vendor Status Watch

← all vendors

TimeClock Plus status history

Current state: operational — “All Systems Operational” per https://status.tcpsoftware.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
2incidents, last 90 days
15incidents on record
Incidents per week, last 12 weeks:

How long do TimeClock Plus incidents last?

2.7 hmedian incident duration14 measured
3.5 days90th percentile1 in 10 ran longer
96 minmedian, major/critical only7 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-26 16:11 UTCTimeClock Plus Application Disruptionresolvednone4 h 50 min
2026-06-22 14:24 UTCTimeClock Plus Application Performance Degradationresolvednone24 h 42 min
2026-05-26 18:48 UTCTimeClock Plus Application Performance Degradationresolvedmajor30 min
2026-05-18 13:05 UTCTimeClock Plus Application Performance Degradationresolvedminor4 h 52 min
2026-05-08 00:47 UTCApplication Performance Degradation/Outageresolvedmajor3 d 12 h
2026-02-23 23:05 UTCTimeClock Plus Application Performance Degradationresolvedminor15 h 43 min
2026-02-17 12:39 UTCTimeClock Plus Application Outageresolvedcritical4 d 6 h
2026-02-03 15:42 UTCTimeClock Plus Application Outageresolvedmajor3 h 22 min
2025-12-21 19:19 UTCAladtec Application Outageresolvedmajor1 h 36 min
2025-10-08 16:32 UTCTimeClock Plus PrismHR2 Application Disruptionresolvedmajor41 min
2025-10-02 14:42 UTCDegraded Application Performanceresolvedminor1 h 57 min
2025-09-27 09:32 UTCAladtec Outageresolvedmaintenance1 h 44 min
2025-09-02 00:08 UTCAladtec Outageresolvednone24 min
2025-08-22 05:04 UTCTimeClock Plus Group10-2 Application Disruptionresolvedmajor17 min
2025-08-21 18:07 UTCService Provider Degradationresolvedminor2 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
}