Skip to main content
Vanta

Policy and Documents cannot be synced from Confluence

Degraded Lasted 1h 6m · started · Vanta's page

Level
confirmed
Worst impact
Degraded
Components
3rd Party Integrations
Down Index
20of 100

What to do

  • Check whether you use Vanta 3rd Party Integrations. 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 1h 6m it lasted.

    Anything that failed between 2026-05-14 05:37 UTC and 2026-05-14 06:43 UTC may need a replay.
  • Subscribe to Vanta's feed to hear about the next one first. RSS feed

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

Updates from Vanta 2

  1. monitoring

    Outage in 3rd-Party Integration Confluence for syncing Policies and Documents. Atlassian is aware and actively working on mitigating the issue.

    provider

  2. resolved

    This incident has been resolved, and policy and document syncing should be functioning as expected.

    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-89a3653732

Is Vanta still down?

No, this incident was resolved 2026-05-14 06:43 UTC. For Vanta's live state, see https://down.guide/vanta.

How long did it last?

1h 6m, from 2026-05-14 05:37 UTC to 2026-05-14 06:43 UTC, by the times Vanta posted.

What was affected?

Vanta named 3rd Party Integrations.

What caused it?

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

Where does this come from?

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