- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Plaid. 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 0m it lasted.
Anything that failed between 2026-10-13 20:55 UTC and 2026-10-13 08:50 UTC may need a replay.Subscribe to Plaid's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=plaid works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Plaid 2
- identified
We identified an issue causing delays in Transactions update processing. During this time, some customers may have received fewer `SYNC_UPDATES_AVAILABLE` webhooks than expected. We applied mitigation and transaction updates began processing normally, including delivery of the accumulated backlog.
provider
- resolved
This incident has been resolved and the backlog of delayed transaction updates has cleared. Some customers may have observed elevated `SYNC_UPDATES_AVAILABLE` webhook volume while processing caught up. We did not observe an abnormal increase in webhook delivery failures, and no customer action is required.
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-bac3897ac3
Is Plaid still down?
No, this incident was resolved 2026-10-13 08:50 UTC. For Plaid's live state, see https://down.guide/plaid.
How long did it last?
0m, from 2026-10-13 20:55 UTC to 2026-10-13 08:50 UTC, by the times Plaid posted.
What caused it?
Plaid hasn't published a root cause. If it does, it shows here.
Where does this come from?
Plaid's official status page, https://status.plaid.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.