Skip to content
← Reading Room

The Friday the 13th Outage That Could Still Hit Your Paycheck

19 November 2026 · 6 min read

On Friday, November 13, 2026, as the FAA's nationwide ground stop dominated the news, a Workday outage left employees at some organizations unable to clock in, check their pay, request time off, or finish benefits enrollment. Writing as a human resource specialist and PhD student in ISEM, I look at what that disruption reveals about the HR systems behind our working lives, and why the effects of an outage can continue long after the technology comes back. Drawing on that week's outages and the 2021 Kronos attack, the article explains how missing time records can turn into payroll errors and legal claims, introduces "time to whole" as a way to measure recovery from the employee's side, and offers practical steps for workers and HR teams.

On Friday, November 13, the Federal Aviation Administration halted departures across the United States at 3:54 p.m. Eastern. The ground stop lasted more than four hours, and more than 9,000 flights were canceled that day.

Around 5 p.m., another system started having trouble, and this one didn't come with pictures of crowded terminals. Nearly 3,000 outage reports for Workday, the HR and payroll platform, appeared on Downdetector. UC Today reported that employees at affected organizations couldn't clock in, check their pay, request time off or finish benefits enrollment. Workday said service was restored by 11 a.m. Eastern on Saturday, although some customers came back later.

I work in human resources and I'm a PhD student in ISEM, so the Workday outage is the one I kept thinking about. A canceled flight can be rebooked. When an hourly employee's shift goes unrecorded, someone has to work out what happened and make sure the pay is right.

What an HRIS does#

A human resource information system, or HRIS, holds an employee's official work record, including job details, hours, pay, leave and benefits. It often sends information to payroll, benefits providers and other company systems. Many employees only open it when they need a pay stub or want to request time off, so it's easy to overlook until it stops working.

What happened that week#

So many systems had problems in such a short time that people wondered whether the failures were connected. Nothing reported so far shows that they were. Director of National Intelligence Jay Clayton dismissed suspicions of malicious activity, and the FAA, Workday and JPMorgan Chase have all pointed away from a cyberattack.

Several of the early explanations do involve work on a live system. Officials said the FAA problem began when a new router was turned on in El Dorado, Arkansas, during a switch from copper to fiber. Workday said services at its disaster recovery site unexpectedly connected to production databases while it was validating a maintenance window. Microsoft linked its November 12 outage to a problem from a network capacity upgrade that a later network change exposed. Chase blamed a software bug in on-premise hardware systems, and CNN reported that an update to those systems caused the trouble.

Google's site reliability engineers have written that roughly 70% of their outages came from changes to live systems, so this pattern has been seen before. The investigations are still going, and some of these explanations may change.

The people questions#

The FAA case shows why I think HR belongs in these conversations. Transportation Secretary Sean Duffy raised the possibility of contractor error or faulty equipment. The router's maker says its devices did not fail, and the contractor, L3Harris, says it is supporting the investigation. The union representing FAA technicians says its members were not involved in the upgrade and that FAA employees have traditionally handled risk assessment on this kind of work. That claim hasn't been independently confirmed.

I don't know which account will hold up. I do know what I would ask as an HR professional: who was qualified to do this work, who approved it, and who still understood the older equipment? The Government Accountability Office has named the retirement of knowledgeable technicians as a challenge for aging FAA systems, and it found 51 of the agency's 138 air traffic control systems unsustainable.

Most companies will never run anything as complicated as air traffic control, but many have a system that only one or two people really understand. A good HRIS can help identify those risks by tracking certifications, specialized skills and upcoming retirements. I'd like to see that information reach the people who plan technology changes.

Why payroll problems outlast the outage#

A paycheck depends on several handoffs. Hours go from timekeeping to payroll, payroll sends a file to the bank, and the bank delivers the deposit. If hours are missing at the start, restoring the software doesn't automatically fix what happened while it was down.

The 2021 Kronos ransomware attack is the example HR professionals remember. UMass Memorial Health had more than 16,000 employees and no hours data for one pay period. It copied its last completed payroll, adjusted for hires and departures, and asked employees to keep track of their time. That kept people getting paid, but overtime and shift pay were hard to calculate, some leave balances may have been wrong, and a union reported more than 11,000 paycheck errors. The first clean payroll came on February 3, 2022, 54 days after the incident was disclosed.

Legal problems followed for a number of employers. Workers at Honda, Cargill and New York's transit agency were among those who brought wage claims. In March 2026, more than four years after the attack, Honda's proposed $2.3 million settlement still needed court approval.

A different way to measure recovery#

Technology teams usually track how long it takes to restore a service. I've started thinking about a second number for HR, which I call "time to whole." It would run from the start of the failure until the last affected employee's hours, pay, leave and benefits are correct. Workday's service came back in less than a day. Its customers will need their own reviews to know how long the second number turns out to be.

If your employer was affected#

  • Write down the hours you worked during the outage.
  • Compare your next pay stub with your notes, especially overtime and shift pay.
  • Check your leave balance and any time-off requests.
  • Make sure your benefits choices were saved, and ask HR if the deadline changed.

If you think your pay is wrong, start with HR or payroll. Your state labor agency or an employment attorney can advise you if the problem isn't resolved.

What HR teams can do#

Start by deciding which HR processes can't wait and how long each one can safely stop. Keep a secure offline copy of the employee roster and recent payroll records, and practice manual timekeeping before you need it. It also helps to have a way to reach employees that doesn't rely on company email, since Microsoft 365 had its own outage the day before Workday's.

During an outage, name one person to lead the response and tell employees what to do in the meantime. Let them know they won't be penalized for a punch or form the outage blocked. Emerson College extended open enrollment after the Workday disruption, and other deadlines may need the same treatment.

Afterward, check the data before trusting it. Review hours, overtime, leave, benefits elections and system integrations, and correct underpayments quickly. Federal rules allow overtime to be delayed when the amount can't be determined by payday, but only for as long as is reasonably necessary, so bring in legal counsel early.

If your organization uses a cloud HR system, ask your team what would happen if it went down the day before payroll. It's much easier to answer that question now than during an outage.

Sources#