Updated: 06:40 GMT, Saturday, November 14, 2026.
I spent Thursday and Friday watching Microsoft 365 stumble. Then, late Friday, another piece of workplace infrastructure went down, and this one sits closer to the paycheck.
Workday, used by more than 11,500 organizations worldwide, placed customer systems into maintenance after a problem turned up while it was testing its disaster-recovery environment. By early Saturday, affected staff still couldn't log in, clock in, check pay, request time off or finish benefits enrollment.
That's not a nuisance outage. That's the operating system of work.
What Workday Says Went Wrong
The San Francisco Chronicle reported that a problem found while testing backup systems left some information in an inconsistent state. A notice posted on Workday's Community Status Page, quoted by Washington University IT at 01:05 GMT on Saturday, is blunter.
While validating the weekly Maintenance Window for Disaster Recovery tenants, we have identified that tenanted services within the DR Site unexpectedly connected to Production databases. As a result, this has left data in an inconsistent state that can cause errors accessing tenants or jobs/integrations/tasks to fail with missing transaction error messages.
Workday said it was placing all WD1 production tenants into maintenance and would provide updates every 30 minutes. The test meant to prove you can survive a failure helped create one.
A Workday spokesperson told KRON4 and LiveNOW from FOX:
Some of our customers are experiencing a service disruption and we're working urgently to investigate and resolve the issue. We sincerely apologize for the challenges this is causing impacted customers.
Workday's X account had not posted about the incident as of Saturday morning. Its maintenance page still said, "Workday is currently unavailable."
Who Felt It, and What Stopped Working
Emerson College said Workday took the system offline at about 22:15 GMT on Friday for unplanned maintenance affecting multiple customers, and extended open enrollment to 17:00 GMT on Monday, November 16. LiveNOW from FOX reported that Downdetector logged nearly 3,000 outage reports shortly after 22:00 GMT.
Washington University was still listing a major outage at 04:44 GMT, saying Workday was not expected back until after an overnight maintenance window. Saint Joseph's University said at 02:53 GMT that a potential solution was still being tested.
Viral posts treated Workday's 11,500-plus customer base, including Walmart and Target, as the number affected. That is the customer count, not a confirmed impact total. Workday has only said "some of our customers." As of 06:35 GMT there was no restoration announcement, and StatusGator was still logging reports from the US and India.
On r/sysadmin and r/workday, commenters pasted the same Workday notice quoted by Washington University IT. An email shared by u/Bagellord added: "We currently do not have any ETA for service restoration and so we are recommending that customers with critical business deadlines today execute their business continuity plans."
According to u/VicomteValmont, who said they had just left a Workday webinar, the first DR-to-production connection was at 8:50 a.m. Pacific (16:50 GMT), and Workday believed the impact was limited to WD5. u/audreyality claimed Workday escalated an internal incident at 9:00 a.m. Pacific (17:00 GMT), but that the first customer alert did not go out until 2:12 p.m. Pacific (22:12 GMT). I have not verified those times.
"We were finalizing open enrollment. Sounds about right," wrote u/kahlyse. u/Academic_Bid9410, who said they work for Workday, wrote: "Down in CA and I work for workday. We didn’t even get a notification 🤦🏼♀️"
HR Systems Are Now as Critical as Communications
We treat email and meetings as the systems you cannot afford to lose. This week already made that point, in the Microsoft 365 outage that left Outlook and Exchange uneven while Teams mostly held.
Payroll and timekeeping belong in the same category. If people cannot clock in, you have a labor-compliance problem before breakfast. If open enrollment sits on a single vendor login, a Friday night outage becomes an HR crisis by Monday.
When one SaaS platform sits under thousands of employers, a disaster-recovery fault is a workforce story. We made that case after last year's AWS outage, and in asking whether adding backup systems actually reduces risk. I don't need a lecture about never using the cloud. I need evidence that the backup is isolated, and that the customer can still operate when the tenant goes dark.
What I'd Do This Morning
If you run IT or HR on Workday, don't wait for a polished vendor update. Stand up a manual timekeeping fallback, check payroll and benefits deadlines, and tell staff what's down and that nobody will be penalized for a login they couldn't complete.
Then ask the contract questions. When do you get a post-incident report? What does the SLA actually credit? Why did a disaster-recovery test have a path into production data?
Cloud HR is convenient until it isn't. This week, two platforms the modern workplace leans on hardest had a very public reminder of that.
