Workday production service outage

Access interruptions delayed routine HR, benefits, time reporting, and expense workflows.

Last modified

Summary

  • Environment: Workday production tenants used for human resources and finance
  • Operational impact: Access interruptions delayed routine HR, benefits, time reporting, and expense workflows
  • Financial impact: Financial impact remains unquantified in public reports
  • Record status: Developing record. Reviewed November 17, 2026; updated as evidence emerges.

What happened

On November 13, 2026, a Workday outage took production services offline for multiple customers. Brown University reported problems signing in that evening. [2]

Saint Joseph’s University reported that Workday took its tenant offline for emergency maintenance. [1]

Impact

  • At Brown, the outage interrupted time reporting, open enrollment, expense reports, hiring, and time-off management. [2]
  • Saint Joseph’s reported just under 16 hours of unavailable service in its own environment. [1]

Timeline

  1. Brown reports Workday sign-in problems

    Brown opened its Workday status incident.

    [2]
  2. Saint Joseph’s reports emergency maintenance

    The university reported its Workday tenant unavailable while Workday investigated.

    [1]
  3. Saint Joseph’s confirms restoration

    Workday re-indexed the tenant’s query service and restored access.

    [1]
  4. Brown confirms restoration

    Brown reported that its automated processes had resumed and were working through the backlog.

    [2]
  5. Briefing updated

    This briefing was last reviewed and updated on November 17, 2026.

Threat Group & Attack Vector

Brown attributed the outage to a configuration error when the vendor reconnected systems during routine maintenance. [2]

Response

Brown asked people who enter their hours directly to track them separately until access returned. Staff who used time clocks could keep doing so and synchronize their time records once service returned. [2]

Saint Joseph’s said Workday checked against data consistency issues by re-indexing its query service before re-enabling access. [1]