- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 1d 19h it lasted.
Anything that failed between 2026-07-22 14:58 UTC and 2026-07-24 10:02 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 13
- investigating
We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue.
provider
- investigating
We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue. 12:41pm EST - We're currently monitoring initial/full pull recovery over the next five to eight hours, will provide more information soon
provider
- investigating
We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue. 12:41pm EST - We're currently monitoring initial/full pull recovery over the next five to eight hours, will provide more information soon 1:21pm EST - To clarify, we are prioritizing initial and full pull recovery. We will work on recovering default pulls next. We don't yet have an estimate to when these delays will be fully resolved.
provider
- investigating
We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue. 1:21pm EST - We are prioritizing initial and full pull recovery. We will work on recovering default pulls next. We don't yet have an estimate to when these delays will be fully resolved.
provider
- investigating
We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue. We are prioritizing recovery of initial and historical Transaction webhooks and then will work through the Default webhook queue. We expect the first group to complete in the next 2-3 hours. Webhooks are being sent on a FIFO basis.
provider
- investigating
The underlying issue is resolved and the system continues to recover. Initial and Historical webhook queues are processing and Default webhooks will process when that completes.
provider
- monitoring
The underlying issue has been resolved, and recovery is progressing. Initial and historical transaction webhooks are now caught up, and new webhooks, including default webhooks, are being processed normally. We are continuing to work through the remaining backlog of older default webhook updates and are monitoring recovery closely.
provider
- monitoring
The underlying issue has been resolved, and recovery is progressing. Initial and historical transaction webhooks are now caught up, and new webhooks, including default webhooks, are being processed normally. We are continuing to work through the remaining backlog of older default update webhooks and expect all missing webhooks to be processed by the end of the day.
provider
- monitoring
The underlying issue has been resolved, and recovery is progressing. Initial and historical transaction webhooks are now caught up, and new webhooks, including default webhooks, are being processed normally. We are continuing to work through the remaining backlog of older default update webhooks and expect all missing webhooks to be processed by the end of the day.
provider
- monitoring
The underlying issue has been resolved, and recovery is progressing. Initial and historical transaction webhooks are now caught up, and new webhooks, including default webhooks, are being processed normally. We are continuing to work through the remaining backlog of older default update webhooks and expect all missing webhooks to be processed by the end of the day Pacific Time.
provider
- investigating
We are again experiencing delays in Transactions update webhooks due to a recurrence of the third-party service provider issue that caused the earlier degradation. We are working closely with the provider to mitigate the issue and restore normal processing as quickly as possible.
provider
- monitoring
The third-party provider issue has been mitigated and recovery is progressing. New item connections and their initial and historical transaction webhooks are healthy and firing normally again, and new transaction updates, including default update webhooks, are being processed normally. We have resumed working through the remaining backlog of older default update webhooks and will continue to monitor closely as it clears.
provider
- resolved
This incident is now resolved. The underlying issue has been fully mitigated, and all delayed default update webhooks have now been delivered. New item connections and their initial and historical transaction webhooks are firing normally, and new transaction updates, including default update webhooks, are being processed normally.
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-09ae3a6eae
Is Plaid still down?
No, this incident was resolved 2026-07-24 10:02 UTC. For Plaid's live state, see https://down.guide/plaid.
How long did it last?
1d 19h, from 2026-07-22 14:58 UTC to 2026-07-24 10:02 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.