Workday outage: disaster-recovery services connect to live databases and take HR and payroll offline
Workday put its WD1 production customers into maintenance on November 13 after disaster-recovery services unexpectedly connected to production databases, leaving employees unable to clock in, see pay or request time off until the next day.
- Root cause:
- Preliminary
- Security:
- No evidence reported
- Started
- Nov 13, 2026, 22:00 UTC
- Service restored (Workday spokesperson, as reported)
- Nov 14, 2026, 16:00 UTC
- Duration
- 18 h 0 min
- Full recovery
- Not documented
- Geographic scope
- United States (affected customers; Workday has not said where its WD1 environment is)
- Last verified
- 3 sources
What happened
- Systems and services affected
- Workday WD1 production tenantsTime tracking (clock in and out)Pay informationTime-off requestsBenefits enrollmentCustomer integrations and jobs
- Kind of failure
- Unknown
- Sector
- HR, payroll and finance software
- Provider report
- None found
- Status and recovery
- Resolved. A Workday spokesperson said service was restored by 11 a.m. EST on November 14. At Washington University, delayed updates between systems and backlogged processes were cleared that evening. Workday has not said when all customers fully recovered.[2][1]
Workday has not given a start time. The start used here is when outage reports rose, about 22:00 UTC (5 p.m. Eastern) on November 13, according to UC Today citing Downdetector and Emerson College. Unverified posts suggest the problem began earlier in the day. The end is the restoration time a Workday spokesperson gave to the press.
What caused it?
Root cause: PreliminaryWorkday's status notice says that while validating the weekly maintenance window for disaster-recovery tenants, "tenanted services within the DR Site unexpectedly connected to Production databases," leaving "data in an inconsistent state." Workday has not said why this happened or published a full report.[1]
Provider report: None found. Workday has not published an incident report that we have found. Its status notices are posted on a Community Status Page that requires a customer login.[1]
Was it malicious?
No evidence reportedA Workday spokesperson told ABC10 the disruption was not related to a cybersecurity incident, as reported by UC Today.[2]
How the failure happened
- 1TriggerWeekly disaster-recovery validation
- 2FailureDR services connected to live databases
- 3SpreadData left inconsistent
- 4ResponseAll WD1 production tenants put into maintenance
- Affected6 services and systems
Evidence for each step
- 1Weekly disaster-recovery validation. Workday was validating the maintenance window for its disaster-recovery tenants[1]Starting point.
- 2DR services connected to live databases. Tenanted services at the DR site unexpectedly connected to production databases[1]Led from step 1: Preliminary: stated officially, may change.
- 3Data left inconsistent. Errors accessing tenants; jobs, integrations and tasks failing with missing-transaction errors[1]Led from step 2: Preliminary: stated officially, may change.
- 4All WD1 production tenants put into maintenance. Workday took affected customers offline while it worked out a recovery path[1]Led from step 3: Preliminary: stated officially, may change.
Only steps the sources state are drawn. Affected services are listed under What happened.
Explanation
Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.
Plain language: what happened and why people were affected.
On Friday afternoon, November 13, many employers that use Workday found their staff could not log in to clock in, check pay, request time off or enroll in benefits.
Workday says a routine check of its backup (disaster-recovery) systems went wrong: the backup systems connected to the live databases, which left some data out of step. Workday took its affected customers offline while it repaired the data. Service came back the next morning.
Confirmed and unknown
Confirmed
- ConfirmedWorkday placed all WD1 production tenants into maintenance while it investigated a recovery path.[1]Said by: Workday (status notice) · Evidence: Official (copy)
Stated or reported, not confirmed
- PreliminaryWhile validating the weekly maintenance window for disaster-recovery tenants, tenanted services at the DR site unexpectedly connected to production databases, leaving data in an inconsistent state.[1]Said by: Workday (status notice) · Evidence: Official (copy)
- Reported
- ReportedService was restored by 11 a.m. EST on November 14.[2]Said by: Workday spokesperson, to ABC10 · Evidence: News
- ReportedThe disruption affected two data centers.[2]Said by: Workday spokesperson, to ABC10 · Evidence: News
- ReportedMore than 11,500 organizations use Workday; it is not known how many were affected.[3]Evidence: News
Denied
- DeniedIt was a cybersecurity incident.[2]Said by: Workday spokesperson, to ABC10 · Evidence: News
Still unknown
- Why the disaster-recovery services connected to production databases.
- How many customers and employees were affected; Workday has said only "some of our customers."
- Whether any data was lost or had to be corrected.
- Whether Workday will publish an incident report.
Timeline
Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.
- First observedNov 13, 2026, 22:00 UTC
- AcknowledgedNot documented
- MitigationNot documented
- RecoveryNov 14, 2026, 16:00 UTC
- ResolvedNov 15, 2026, 00:49 UTC
- Incident reportNone found
- First observedOutage reports rise sharply; Downdetector logs nearly 3,000 reports and Emerson College reports Workday offline.[2]
- Washington University IT posts Workday's status notice: DR services connected to production databases and all WD1 production tenants are being placed into maintenance. Workday's own posting time is not shown.[1]
- Washington University IT: Workday has taken the service offline temporarily to address data management issues.[1]
- Washington University IT: Workday continues to test and validate system health for all customers; no estimated time for restoration.[1]
- RecoveryService restored by 11 a.m. EST, according to a Workday spokesperson.[2]
- After the incident endedWashington University IT: the outage is resolved, but updates between systems may be delayed.[1]
- ResolvedWashington University IT marks the incident resolved after clearing backlogged processes.[1]
- Start to: Service restored (Workday spokesperson, as reported)18 h 0 min
Evidence and sources
Grouped by type of evidence. Numbers match the citations above.
Copies of official records
Third-party copies of an official record that we cannot read directly, such as a provider's admin-only status page.
- 1.Service Outage (Vendor) - Workday (opens in a new tab)Washington University IT · Copy of official record · Published · AccessedReproduces Workday's Community Status Page notice word for word; Workday's page requires a customer login. Later updates are Washington University's own.
Independent reporting
News organizations reporting statements, impact and their own findings.
- 2.Workday's Backup Test Took Payroll and Timekeeping Offline (opens in a new tab)UC Today · News · Published · AccessedQuotes statements a Workday spokesperson gave to ABC10, KRON4 and LiveNOW from FOX.
- 3.Outage at HR platform Workday locks millions of employees out of their account (opens in a new tab)Engadget · News · Published · Accessed
Last verified against these sources on Nov 15, 2026.