Paycor status history
Current state: operational — “All Systems Operational” per https://status.recruitingbypaycor.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Paycor incidents last?
From 7 incidents with a vendor-posted start and resolve time. Longest on record: Transfer Hires to Paycor — 21.5 h (2026-06-25 18:14 UTC). Excluded, never estimated: nothing. 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 (7)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-30 15:25 UTC | In-Development Updates Temporarily Enabled in Production | resolved | none | 1 h 26 min |
| 2026-06-25 18:14 UTC | Transfer Hires to Paycor | resolved | major | 21 h 28 min |
| 2026-05-15 16:13 UTC | Heavier than normal traffic load | resolved | minor | 7 h 05 min |
| 2026-03-02 15:19 UTC | Gravity App Outage | resolved | critical | 2 h 43 min |
| 2026-01-02 19:06 UTC | Slow Loading Candidate Profiles | resolved | minor | 4 h 38 min |
| 2025-12-03 14:46 UTC | Candidate Indexing Delays | resolved | minor | 16 h 16 min |
| 2025-10-09 19:56 UTC | Integrated Background Check Submissions | resolved | minor | 17 h 30 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 Paycor with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"paycor"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
