Skip to main content
Ashby

Delays in Workday HRIS Sync

Degraded Lasted 47m · started · Ashby's page

Level
confirmed
Worst impact
Degraded
Components
HRIS Integration
Down Index
18of 100

What to do

  • Check whether you use Ashby HRIS Integration. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 47m it lasted.

    Anything that failed between 2026-02-20 18:59 UTC and 2026-02-20 19:45 UTC may need a replay.
  • Subscribe to Ashby's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=ashby works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Ashby 4

  1. investigating

    We are currently investigating this issue.

    provider

  2. identified

    We have identified an issue with an upstream provider that is causing delays in Workday sync.

    provider

  3. monitoring

    We're seeing signs of recovery with the upstream provider and Workday HRIS syncs are now catching up.

    provider

  4. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5941665699

Is Ashby still down?

No, this incident was resolved 2026-02-20 19:45 UTC. For Ashby's live state, see https://down.guide/ashby.

How long did it last?

47m, from 2026-02-20 18:59 UTC to 2026-02-20 19:45 UTC, by the times Ashby posted.

What was affected?

Ashby named HRIS Integration.

What caused it?

Ashby hasn't published a root cause. If it does, it shows here.

Where does this come from?

Ashby's official status page, https://status.ashbyhq.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.