Skip to main content
Zapier

Upstream errors with the BambooHR integration

Degraded Lasted 6h 12m · started · Zapier's page

Level
confirmed
Worst impact
Degraded
Down Index
21of 100

What to do

  • Check whether your product depends on Zapier. 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 6h 12m it lasted.

    Anything that failed between 2026-10-21 14:10 UTC and 2026-10-21 20:22 UTC may need a replay.
  • Subscribe to Zapier's feed to hear about the next one first. RSS feed

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

Updates from Zapier 3

  1. identified

    Zaps using BambooHR may encounter errors or fail to retrieve data due to a service disruption at BambooHR. We have identified the issue as an outage affecting BambooHR and are monitoring their service for recovery. The full scope of affected Zaps is still being assessed.

    provider

  2. monitoring

    We are monitoring the BambooHR integration following the service disruption at BambooHR. Zaps using BambooHR may still encounter errors or fail to retrieve data while we assess recovery. We have not yet confirmed that service is fully restored.

    provider

  3. resolved

    Our Engineering team has confirmed the service disruption at BambooHR has been resolved and the normal service has been restored. Affected Zap runs have been replayed, and no additional action is necessary. If you still have errors or have questions, please feel free to open a ticket with our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

    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-edfb460726

Is Zapier still down?

No, this incident was resolved 2026-10-21 20:22 UTC. For Zapier's live state, see https://down.guide/zapier.

How long did it last?

6h 12m, from 2026-10-21 14:10 UTC to 2026-10-21 20:22 UTC, by the times Zapier posted.

What caused it?

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

Where does this come from?

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