Plaid

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-21 03:18 UTC

   Chase is currently experiencing downtime impacting all channels and data recipients. Item adds and API calls through Plaid are impacted. We will provide an update when Chase has resolved the issue.

2. resolved 2026-10-21 04:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 14:39 UTC

   We are experiencing degraded performance with Link. We are actively investigating and working to mitigate this issue.

2. resolved 2026-10-15 14:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-14 21:10 UTC

   We have identified the root cause of the issue and are actively working to mitigate the impact. The `transactions/enrich` and other `transactions` related endpoints and webhooks.

2. monitoring 2026-10-14 21:50 UTC

   This issue has been mitigated. We are closely monitoring our systems as we recover.

3. resolved 2026-10-14 21:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-13 07:40 UTC

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

2. resolved 2026-10-13 08:50 UTC

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

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-11 08:25 UTC

   Chase is currently experiencing downtime impacting all channels and data recipients. Item adds and API calls through Plaid are impacted. We will provide an update when Chase has resolved the issue.

2. resolved 2026-10-11 09:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-26 03:40 UTC

   Bank of America is currently experiencing downtime impacting all channels and data recipients. API calls through Plaid are impacted. We will provide an update when Bank of America has resolved the issue.

2. resolved 2026-09-26 05:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 20:22 UTC

   Chime is currently experiencing downtime impacting all channels and data recipients. Transactions Data updates might be delayed. We will provide an update when Chime has resolved the issue.

2. resolved 2026-09-18 02:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-15 17:56 UTC

   We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue.

2. investigating 2026-09-15 19:12 UTC

   We have resolved the underlying issue and the system is now recovering. Transactions updates will be delayed for the next few hours.

3. resolved 2026-09-16 00:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 16:31 UTC

   We are currently experiencing elevated error rates for Item adds. We are actively investigating and working to mitigate this issue.

2. identified 2026-09-15 18:26 UTC

   We have identified the root cause of the issue and are actively working to mitigate the impact.

3. monitoring 2026-09-15 18:36 UTC

   This issue has been mitigated. We are closely monitoring our systems as we recover.

4. resolved 2026-09-15 18:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-11 16:56 UTC

   Our Statements API, /statements/download, is currently experiencing unexpected downtime. We are actively investigating and working to mitigate this issue.

2. resolved 2026-09-11 22:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-08-24 05:36 UTC

   This issue has been mitigated. We are closely monitoring our systems as we recover.

2. resolved 2026-08-24 21:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-16 15:13 UTC

   Navy Federal Credit Union is currently experiencing downtime impacting all channels and data recipients. Item adds and API calls through Plaid are impacted. We will provide an update when Navy Federal Credit Union has resolved the issue.

2. investigating 2026-08-16 15:24 UTC

   Navy Federal Credit Union is currently experiencing downtime impacting all channels and data recipients. Item adds and API calls through Plaid are impacted. We will provide an update when Navy Federal Credit Union has resolved the issue.

3. monitoring 2026-08-16 16:29 UTC

   Navy Federal Credit Union connection health is recovering. We'll continue monitoring and provide and update when Navy Federal Credit Union has fully resolved the issue.

4. resolved 2026-08-16 18:51 UTC

   The health issue with Navy Federal Credit Union has been resolved

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-12 21:48 UTC

   Navy Federal Credit Union is currently experiencing downtime impacting all channels and data recipients. Item adds and API calls through Plaid are impacted. We will provide an update when Navy Federal Credit Union has resolved the issue.

2. resolved 2026-08-13 06:08 UTC

   The Navy Federal Credit Union issue has been resolved

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 01:01 UTC

   We are investigating delayed transaction updates affecting a subset of Capital One Items. Affected Items remain healthy; the impact is limited to delayed refresh of transaction data.

2. investigating 2026-08-05 02:26 UTC

   We have identified the root cause of the issue and are actively working to mitigate the impact.

3. identified 2026-08-05 02:40 UTC

   We have identified the root cause of the issue and are actively working to mitigate the impact.

4. monitoring 2026-08-05 19:52 UTC

   We've addressed the underlying cause and are currently monitoring for the resolution.

5. resolved 2026-08-10 17:39 UTC

   All Delayed Transactions have now been fully processed.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-02 14:51 UTC

   We are observing issues impacting new connections to Bank of America. We have notified Bank of America and are working to root cause and resolve this issue as quickly as possible.

2. resolved 2026-08-03 12:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-01 01:34 UTC

   We've identified and issue causing degraded performance for our Python SDK (v33.0.0 and later) when retrieving Identity Verification results. We are deploying a fix.

2. resolved 2026-08-01 02:56 UTC

   A fix is deployed. This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 16:34 UTC

   We are currently experiencing elevated error rates for Payouts/Refunds API calls. We are actively investigating and working to mitigate this issue.

2. identified 2026-07-27 17:55 UTC

   We have identified the root cause of the issue and are actively working to mitigate the impact. This is also impacting payments transitioning to SETTLED status.

3. identified 2026-07-27 20:35 UTC

   The incident is ongoing and we are working with our partner to restore service. You may continue to see issues with Refunds and Payouts. Settlement webhooks for pay-ins are also impacted.

4. monitoring 2026-07-27 22:09 UTC

   We are observing improved performance and services are returning to normal operations. We are closely monitoring our systems as we recover.

5. resolved 2026-07-28 08:40 UTC

   This incident has been resolved. Our services have returned to normal operations.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-23 20:36 UTC

   Transfer is experiencing delays affecting status updates for some Standard ACH and Same-Day ACH transfers created yesterday. Impacted Transfers were successfully settled on ACH network. Transfer creation and new payment processing are operating normally. We've identified the...

2. resolved 2026-07-23 21:59 UTC

   All impacted ACH and Same-day ACH transfers's status have been updated to posted. They will be marked as settled later today.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 11:41 UTC

   We are currently experiencing elevated error rates for Payouts/Refunds API calls. We are actively investigating and working to mitigate this issue.

2. identified 2026-07-23 11:51 UTC

   We have identified the root cause of the issue and are actively working to mitigate the impact.

3. monitoring 2026-07-23 12:25 UTC

   This issue has been mitigated. We are closely monitoring our systems as we recover.

4. monitoring 2026-07-23 14:28 UTC

   This incident has been resolved.

5. resolved 2026-07-23 14:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-22 14:58 UTC

   We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue.

2. investigating 2026-07-22 16:43 UTC

   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

3. investigating 2026-07-22 17:22 UTC

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

4. investigating 2026-07-22 17:32 UTC

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

5. investigating 2026-07-22 17:39 UTC

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

6. investigating 2026-07-22 21:25 UTC

   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.

7. monitoring 2026-07-22 23:53 UTC

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

8. monitoring 2026-07-23 15:23 UTC

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

9. monitoring 2026-07-23 19:43 UTC

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

10. monitoring 2026-07-23 23:50 UTC

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

11. investigating 2026-07-24 02:22 UTC

    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.

12. monitoring 2026-07-24 04:26 UTC

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

13. resolved 2026-07-24 10:02 UTC

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

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 23:59 UTC

   We are experiencing degraded performance with Link. Some users are seeing issues with Link, where when users completes an OAuth flow with a bank, Plaid Link may crash and restart, prompting users to connect their bank accounts again. We believe that this is related to a recent...

2. resolved 2026-07-18 01:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-16 08:48 UTC

   We are experiencing elevated error rates on the Plaid Dashboard during SSO and Google logins. We are actively investigating this issue.

2. identified 2026-07-16 09:22 UTC

   We are experiencing elevated error rates on the Plaid Dashboard during SSO and Google logins. We are working on a resolution.

3. monitoring 2026-07-16 09:30 UTC

   SSO and Google logins on the Plaid Dashboard are now working with increased latency. We'll continue to monitor until fully recovered.

4. resolved 2026-07-16 10:30 UTC

   SSO and Google logins in the Plaid Dashboard are now performing as normal.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-12 03:06 UTC

   We are currently experiencing elevated error rates for Document Income API calls. We are actively investigating and working to mitigate this issue.

2. resolved 2026-07-12 05:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-12 00:43 UTC

   Chase is currently experiencing downtime impacting all channels and data recipients. Item adds and API calls through Plaid are impacted. We will provide an update when Chase has resolved the issue.

2. resolved 2026-07-12 00:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-11 01:56 UTC

   Wells Fargo is currently experiencing downtime impacting all channels and data recipients. Item adds through Plaid are impacted. We will provide an update when Wells Fargo has resolved the issue.

2. resolved 2026-07-11 02:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Plaid's status page.