Plaid Outage History

Plaid is up right now

Plaid had 14 outages in the last 90 days totaling 25h 36m of downtime — averaging 4.7 incidents per month.

There were 14 Plaid outages since February 11, 2026 totaling 25h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.plaid.com

Notice April 30, 2026

Dashboard widgets appearing as dark variants

Detected by Pingoru
Apr 30, 2026, 07:53 PM UTC
Resolved
Apr 30, 2026, 08:55 PM UTC
Duration
1h 1m
Timeline · 3 updates
  1. investigating Apr 30, 2026, 07:53 PM UTC

    Dashboard widgets are appearing as dark theme variants for some users.

  2. identified Apr 30, 2026, 08:09 PM UTC

    We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

  3. resolved Apr 30, 2026, 08:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2026

Elevated API errors

Detected by Pingoru
Apr 29, 2026, 03:07 AM UTC
Resolved
Apr 29, 2026, 03:25 AM UTC
Duration
17m
Timeline · 3 updates
  1. monitoring Apr 29, 2026, 03:07 AM UTC

    A fix has been implemented and we are monitoring the results.

  2. identified Apr 29, 2026, 03:07 AM UTC

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

  3. resolved Apr 29, 2026, 04:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 23, 2026

IDV Downtime

Detected by Pingoru
Apr 23, 2026, 05:33 PM UTC
Resolved
Apr 23, 2026, 05:58 PM UTC
Duration
25m
Timeline · 2 updates
  1. monitoring Apr 23, 2026, 05:33 PM UTC

    Identity Verification experienced downtime between 17:02 to 17:07 UTC. The problem has since been identified and fixed.

  2. resolved Apr 23, 2026, 05:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 23, 2026

Transaction Updates Delayed

Detected by Pingoru
Apr 23, 2026, 02:57 PM UTC
Resolved
Apr 23, 2026, 10:23 PM UTC
Duration
7h 25m
Timeline · 5 updates
  1. identified Apr 23, 2026, 02:57 PM UTC

    We are currently experiencing elevated latency for the INITIAL_UPDATE and HISTORICAL_UPDATE Transactions webhooks. We are actively investigating and working to mitigate this issue.

  2. identified Apr 23, 2026, 03:04 PM UTC

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

  3. monitoring Apr 23, 2026, 04:34 PM UTC

    We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

  4. monitoring Apr 23, 2026, 06:06 PM UTC

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

  5. resolved Apr 23, 2026, 10:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 22, 2026

Service Disruption Impacting Wells Fargo connections

Detected by Pingoru
Apr 22, 2026, 04:08 AM UTC
Resolved
Apr 22, 2026, 03:57 AM UTC
Duration
Timeline · 2 updates
  1. resolved Apr 22, 2026, 04:08 AM UTC

    This incident has been resolved.

  2. investigating Apr 22, 2026, 04:08 AM 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.

Read the full incident report →

Minor April 18, 2026

Elevated Link errors

Detected by Pingoru
Apr 18, 2026, 03:45 AM UTC
Resolved
Apr 18, 2026, 07:47 AM UTC
Duration
4h 2m
Timeline · 2 updates
  1. investigating Apr 18, 2026, 03:45 AM UTC

    We are currently experiencing elevated error rates for Link due to AT&T messaging issues. We are actively investigating and working to mitigate this issue.

  2. resolved Apr 18, 2026, 07:47 AM UTC

    We experienced degraded performance with Link. Some Link users missed their text messages. The issue has been mitigated.

Read the full incident report →

Notice April 1, 2026

Increased Transactions webhook latency

Detected by Pingoru
Apr 01, 2026, 09:02 PM UTC
Resolved
Apr 01, 2026, 09:07 PM UTC
Duration
5m
Timeline · 2 updates
  1. monitoring Apr 01, 2026, 09:02 PM UTC

    We are currently experiencing elevated latency for the INITIAL_UPDATE and HISTORICAL_UPDATE Transactions webhooks. We are actively investigating and working to mitigate this issue.

  2. resolved Apr 01, 2026, 09:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 27, 2026

Elevated dashboard error rates

Detected by Pingoru
Mar 27, 2026, 05:06 PM UTC
Resolved
Mar 27, 2026, 09:26 PM UTC
Duration
4h 20m
Timeline · 3 updates
  1. investigating Mar 27, 2026, 05:06 PM UTC

    We are experiencing elevated error rates in the Dashboard. We are actively investigating this issue.

  2. monitoring Mar 27, 2026, 05:19 PM UTC

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

  3. resolved Mar 27, 2026, 09:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 13, 2026

Service Disruption Impacting Fidelity and Fidelity NetBenefit connections

Detected by Pingoru
Mar 13, 2026, 04:28 PM UTC
Resolved
Mar 13, 2026, 05:37 PM UTC
Duration
1h 9m
Timeline · 2 updates
  1. investigating Mar 13, 2026, 04:28 PM UTC

    We are currently investigating an issue affecting connections to Fidelity and Fidelity NetBenefits. As a result, item adds and API requests for these institutions through Plaid may be impacted. Our team is actively working to resolve the issue and will share updates as they become available.

  2. resolved Mar 13, 2026, 06:05 PM UTC

    The issue affecting connections to Fidelity and Fidelity NetBenefits has been resolved. Item adds and API requests through Plaid have returned to normal operation. We will continue to monitor to ensure stability.

Read the full incident report →

Critical March 9, 2026

API downtime

Detected by Pingoru
Mar 09, 2026, 09:44 PM UTC
Resolved
Mar 09, 2026, 11:14 PM UTC
Duration
1h 30m
Timeline · 2 updates
  1. investigating Mar 09, 2026, 09:44 PM UTC

    We experienced elevated error rates for API calls and item adds on Monday, March 09, 2026 from 21:25 UTC - 21:30 UTC. This issue has been mitigated. We are closely monitoring our systems as we recover.

  2. resolved Mar 10, 2026, 12:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026

Transfer API degradation

Detected by Pingoru
Mar 03, 2026, 11:15 PM UTC
Resolved
Mar 04, 2026, 04:11 AM UTC
Duration
4h 55m
Timeline · 2 updates
  1. monitoring Mar 03, 2026, 11:15 PM UTC

    FedACH continues to report delays in ACH file delivery and settlement. This may result in ACH Transfer delays. We are continuing to monitor the situation to limit client impact.

  2. resolved Mar 04, 2026, 04:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 24, 2026

Instant Payment Transfer Rails Unavailable And Delayed ACH Processing

Detected by Pingoru
Feb 24, 2026, 02:54 AM UTC
Resolved
Feb 24, 2026, 03:14 AM UTC
Duration
19m
Affected: API - Production
Timeline · 2 updates
  1. investigating Feb 24, 2026, 02:54 AM UTC

    Instant Payment Transfer rails are temporarily delayed. This applies to Instant Payouts (RTP and FedNow) and RfP (Request for Payments). ACH Transfers are unaffected for now. We are actively monitoring and will update this incident as it is resolved.

  2. resolved Feb 24, 2026, 03:14 AM UTC

    We think the impact from the issue is over.

Read the full incident report →

Notice February 11, 2026

Service Disruption Impact Chase Customers

Detected by Pingoru
Feb 11, 2026, 06:32 PM UTC
Resolved
Feb 10, 2026, 07:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 11, 2026, 06:32 PM 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.

Read the full incident report →