Dev APIs / Banking API / Plaid

Plaid

OPERATIONAL

Since Jul 2026 · 25 incidents · status.plaid.com · checked just now

User reportsVisitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.
…
CompareAdd to stackStatus page
GradeDLast 90 days
DPRODA+SHIP

Overview

30d90d1y
Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
98.132%Grade D
IncidentsEverything posted on the status page except scheduled maintenance.
180 Sev 1
Fully downMost customers down, by the provider's own account.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
3h 38m
LongestLongest Sev 1–2 incident, start to resolved.
5d 16h
Since lastTime since the last counted incident was resolved.
3d 3h

By area

DProduction
18INCIDENTS
9d 11hAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Sep 15, 2026 · 6h 28mTransaction Updates Delayed
SEV 2Sep 11, 2026 · 5h 19mStatements API downtime
SEV 2Sep 15, 2026 · 2h 13mElevated Item add errors
24 in the last 6 months.
A+Shipping
0INCIDENTS
0mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90dNothing.
3 in the last 6 months.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

25 in the last 6 months.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down18
Sev 3 · Can't shipCan't deploy, build or manage it0
Sev 4 · PapercutDocs, status page, slow dashboard0

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Where it breaks

Last 12 monthsPlaces named on the status page: cloud regions, cities, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.
1 place · 24 not pinned
United Kingdom (UK): 1 incident · Plaid
Sev 1–2 time by place, 12 monthsTime with a Sev 1 or 2 open that names the place, any provider. Overlaps count once.
United Kingdom16h 06m

Communication

Updates eachStatus page updates per incident, on average.
3.1Last 12 months
Update gapMedian time between status page updates during an incident.
1h 25mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 24Sev 1–2

Incident history

Oct 22, 202618mSEV 2
Service Disruption Impacting Chase connectionsChase was down on all channels, so Plaid item adds for Chase connections failed for about 18 minutes; other institutions were not reported affected.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Chase was down on all channels, so Plaid item adds for Chase connections failed for about 18 minutes; other institutions were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 03:34 UTC · investigating
    Chase is currently experiencing downtime impacting all channels and data recipients. Item adds through Plaid are impacted. We will provide an update when Chase has resolved the issue.
  2. 03:52 UTC · resolved
    This incident has been resolved.
Source
Oct 21, 20261h 19mSEV 2
Service Disruption Impacting Chase connectionsChase connections failed through Plaid for about 80 minutes because Chase itself was down; other institutions were not described as affected.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Chase connections failed through Plaid for about 80 minutes because Chase itself was down; other institutions were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 03:18 UTC · investigating
    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. 04:37 UTC · resolved
    This incident has been resolved.
Source
Oct 15, 20269mSEV 2
Link performance degradationLink, Plaid's customer sign-in flow, had degraded performance for about 9 minutes; the text gives no scope.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Link, Plaid's customer sign-in flow, had degraded performance for about 9 minutes; the text gives no scope.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 14:39 UTC · investigating
    We are experiencing degraded performance with Link. We are actively investigating and working to mitigate this issue.
  2. 14:47 UTC · resolved
    This incident has been resolved.
Source
Oct 14, 202632mSEV 2
Elevated API errorsElevated API errors hit transactions/enrich and other transactions endpoints and webhooks for about 30 minutes; the text gives no breadth.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Elevated API errors hit transactions/enrich and other transactions endpoints and webhooks for about 30 minutes; the text gives no breadth.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 21:10 UTC · identified
    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. 21:50 UTC · monitoring
    This issue has been mitigated. We are closely monitoring our systems as we recover.
  3. 21:59 UTC · resolved
    This incident has been resolved.
Source
Oct 13, 20260mSEV 2
Delayed Transactions Update WebhooksTransactions update processing was delayed, so some customers received fewer SYNC_UPDATES_AVAILABLE webhooks than expected. Plaid applied mitigation and the backlog of delayed updates cleared, with no customer action required. Duration and number of customers affected were not stated.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER -725M
    Transaction update processing was delayed, so some customers received fewer SYNC_UPDATES_AVAILABLE webhooks than expected until a backlog cleared.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 07:40 UTC · 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.
  2. 08:50 UTC · 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.
Source
Oct 11, 202644mSEV 2
Service Disruption Impacting Chase connectionsChase bank connections failed through Plaid for about 45 minutes; other institutions were not described as affected.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Chase bank connections failed through Plaid for about 45 minutes; other institutions were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 08:25 UTC · investigating
    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. 09:09 UTC · resolved
    This incident has been resolved.
Source
Sep 26, 20261h 34mSEV 2
Service Disruption Impacting Bank of America connectionsPlaid API calls to Bank of America accounts failed for about 95 minutes because the bank was down; other institutions were not reported affected.AI-graded · some customers
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Plaid API calls to Bank of America accounts failed for about 95 minutes because the bank was down; other institutions were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 03:40 UTC · investigating
    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. 05:15 UTC · resolved
    This incident has been resolved.
Source
Sep 17, 20266h 02mSEV 2
Service Disruption Impacting Chime connectionsPlaid connections to Chime were down for about six hours, delaying transaction data updates for developers using Chime.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Plaid connections to Chime were down for about six hours, delaying transaction data updates for developers using Chime.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 20:22 UTC · investigating
    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. 02:23 UTC · resolved
    This incident has been resolved.
Source
Sep 15, 20266h 28mSEV 2
Transaction Updates DelayedTransactions updates were delayed for an unspecified set of customers for about six hours; the provider says recovery was underway with delays lingering.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Transactions updates were delayed for an unspecified set of customers for about six hours; the provider says recovery was underway with delays lingering.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 17:56 UTC · investigating
    We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue.
  2. 19:12 UTC · investigating
    We have resolved the underlying issue and the system is now recovering. Transactions updates will be delayed for the next few hours.
  3. 00:24 UTC · resolved
    This incident has been resolved.
Source
Sep 15, 20262h 13mSEV 2
Elevated Item add errorsPlaid saw elevated error rates on Item add requests starting 16:31 UTC on September 15, 2026. The root cause was identified and mitigated by 18:36, and the incident was resolved at 18:45. The text does not give the specific cause or the full scope.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Item add requests showed elevated errors for about two hours; the text does not say which customers or regions were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 16:31 UTC · investigating
    We are currently experiencing elevated error rates for Item adds. We are actively investigating and working to mitigate this issue.
  2. 18:26 UTC · identified
    We have identified the root cause of the issue and are actively working to mitigate the impact.
  3. 18:36 UTC · monitoring
    This issue has been mitigated. We are closely monitoring our systems as we recover.
  4. 18:45 UTC · resolved
    This incident has been resolved.
Source
Sep 11, 20265h 19mSEV 2
Statements API downtimePlaid's Statements API download endpoint was down for about five and a half hours; the scope of affected customers is not stated.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Plaid's Statements API download endpoint was down for about five and a half hours; the scope of affected customers is not stated.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 16:56 UTC · investigating
    Our Statements API, /statements/download, is currently experiencing unexpected downtime. We are actively investigating and working to mitigate this issue.
  2. 22:15 UTC · resolved
    This incident has been resolved.
Source
Aug 24, 202615h 37mSEV 2
Elevated API errorsElevated errors on Plaid's API, with no components or affected share named; mitigated, then resolved about 15 hours after it started.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Elevated errors on Plaid's API, with no components or affected share named; mitigated, then resolved about 15 hours after it started.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 05:36 UTC · monitoring
    This issue has been mitigated. We are closely monitoring our systems as we recover.
  2. 21:13 UTC · resolved
    This incident has been resolved.
Source
Aug 16, 20263h 38mSEV 2
Service Disruption Impacting Navy Federal Credit Union connectionsNavy Federal Credit Union had downtime affecting all channels and data recipients, so Plaid item adds and API calls for its connections failed. Plaid said it was recovering by 16:29 UTC and marked the issue resolved at 18:51 UTC on 2026-08-16.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Item adds and API calls for Navy Federal Credit Union connections failed for about 3.5 hours; other institutions were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 15:13 UTC · investigating
    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. 15:24 UTC · investigating
    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. 16:29 UTC · monitoring
    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. 18:51 UTC · resolved
    The health issue with Navy Federal Credit Union has been resolved
Source
Aug 12, 20268h 20mSEV 2
Service Disruption Impacting Navy Federal Credit Union connectionsPlaid API calls and item adds failed for Navy Federal Credit Union connections for about 8 hours; other institutions were not described as affected.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Plaid API calls and item adds failed for Navy Federal Credit Union connections for about 8 hours; other institutions were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 21:48 UTC · identified
    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. 06:08 UTC · resolved
    The Navy Federal Credit Union issue has been resolved
Source
Aug 5, 20265d 16hSEV 2
Delayed Capital One Transactions UpdatesTransaction data updates were delayed for a subset of Capital One Items starting August 5. Plaid found the root cause and addressed it on August 5, then monitored. All delayed transactions were fully processed by August 10.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Transaction data refreshes were delayed for a subset of Capital One Items for about 9 days; Items stayed healthy.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 01:01 UTC · investigating
    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. 02:26 UTC · investigating
    We have identified the root cause of the issue and are actively working to mitigate the impact.
  3. 02:40 UTC · identified
    We have identified the root cause of the issue and are actively working to mitigate the impact.
  4. 19:52 UTC · monitoring
    We've addressed the underlying cause and are currently monitoring for the resolution.
  5. 17:39 UTC · resolved
    All Delayed Transactions have now been fully processed.
Source
Aug 2, 202622h 01mSEV 2
Service Disruption Impacting Bank of America connectionsIssues with new connections to Bank of America were reported for about 22 hours; other institutions were not described as affected.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Issues with new connections to Bank of America were reported for about 22 hours; other institutions were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 14:51 UTC · investigating
    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. 12:53 UTC · resolved
    This incident has been resolved.
Source
Aug 1, 20261h 22mSEV 2
python SDK degraded on Identity Verification APIsPython SDK v33.0.0 and later had degraded performance retrieving Identity Verification results; other SDK versions and API paths were not described as affected.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Python SDK v33.0.0 and later had degraded performance retrieving Identity Verification results; other SDK versions and API paths were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 01:34 UTC · identified
    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. 02:56 UTC · resolved
    A fix is deployed. This incident has been resolved.
Source
Jul 27, 202616h 06mSEV 2
Virtual Account perfomance degradation (UK and Europe)Elevated error rates hit Payouts and Refunds API calls in UK and Europe, and settlement webhooks for pay-ins were also impacted. The provider worked with a partner to restore service. Monitoring began at 22:09 on 27 July, and the incident was resolved at 08:40 on 28 July.AI-graded · regional
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Payouts and Refunds API calls failed at elevated rates and pay-in settlement webhooks were delayed in UK and Europe for about 16 hours.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
5 updates
  1. 16:34 UTC · investigating
    We are currently experiencing elevated error rates for Payouts/Refunds API calls. We are actively investigating and working to mitigate this issue.
  2. 17:55 UTC · identified
    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. 20:35 UTC · identified
    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. 22:09 UTC · monitoring
    We are observing improved performance and services are returning to normal operations. We are closely monitoring our systems as we recover.
  5. 08:40 UTC · resolved
    This incident has been resolved. Our services have returned to normal operations.
Source
Jul 23, 202610h 18mSEV 2
Payouts/Refunds API degraded2 incidents
  1. Thu, Jul 23 11:41 UTC2h 52mSEV 2
    Payouts/Refunds API degradedPlaid saw elevated error rates on Payouts/Refunds API calls from 11:41 to about 14:33 UTC on July 23. The root cause was identified and mitigated by 12:25, with monitoring until resolution. The text gives no count of affected customers and no detailed cause.AI-graded
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
      Payouts and Refunds API calls returned elevated errors for about three hours; no regions or customer share were named.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    5 updates
    1. 11:41 UTC · investigating
      We are currently experiencing elevated error rates for Payouts/Refunds API calls. We are actively investigating and working to mitigate this issue.
    2. 11:51 UTC · identified
      We have identified the root cause of the issue and are actively working to mitigate the impact.
    3. 12:25 UTC · monitoring
      This issue has been mitigated. We are closely monitoring our systems as we recover.
    4. 14:28 UTC · monitoring
      This incident has been resolved.
    5. 14:33 UTC · resolved
      This incident has been resolved.
    Source
  2. Thu, Jul 23 20:36 UTC1h 22mSEV 2
    Transfer Status Upates DelaysStatus updates for some Standard and Same-Day ACH transfers were delayed; the transfers themselves settled and new payments worked.AI-graded · some customers
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
      Status updates for some Standard and Same-Day ACH transfers were delayed; the transfers themselves settled and new payments worked.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    2 updates
    1. 20:36 UTC · investigating
      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 root cause and are actively addressing it and will update this incident as it is resolved.
    2. 21:59 UTC · resolved
      All impacted ACH and Same-day ACH transfers's status have been updated to posted. They will be marked as settled later today.
    Source
Jul 22, 202643h 04mSEV 2
Transaction Updates DelayedTransaction update webhooks were delayed starting July 22 due to a third-party provider issue, and initial and historical webhooks were prioritized. A recurrence on July 24 was mitigated. Default update webhooks were delivered in backlog by the resolution at 10:02 UTC July 24.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Transaction update webhooks were delayed for days across customers, with default updates backlogged; the API itself kept responding.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
13 updates
  1. 14:58 UTC · investigating
    We are currently experiencing delays in Transactions updates. We are actively investigating and working to mitigate this issue.
  2. 16:43 UTC · 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
  3. 17:22 UTC · 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.
  4. 17:32 UTC · 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.
  5. 17:39 UTC · 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.
  6. 21:25 UTC · 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.
  7. 23:53 UTC · 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.
  8. 15:23 UTC · 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.
  9. 19:43 UTC · 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.
  10. 23:50 UTC · 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.
  11. 02:22 UTC · 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.
  12. 04:26 UTC · 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.
  13. 10:02 UTC · 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.
Source
Jul 17, 20261h 40mSEV 2
Link performance degradationSome users saw Plaid Link crash and restart after completing OAuth with their bank, prompting them to reconnect accounts. Plaid linked it to a recent WebKit bug and worked on mitigation. The incident was resolved about 1h40m after it started, with no fix detail beyond that.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Plaid Link crashed and restarted for some users after completing bank OAuth flows, forcing reconnection; other users unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 23:59 UTC · investigating
    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 WebKit bug: [https://bugs.webkit.org/show_bug.cgi?id=318772](https://bugs.webkit.org/show_bug.cgi?id=318772 "https://bugs.webkit.org/show_bug.cgi?id=318772") We are actively investigating and working to mitigate this issue.
  2. 01:39 UTC · resolved
    This incident has been resolved.
Source
Jul 16, 20261h 42mSEV 3
Elevated dashboard.plaid.com error ratesPlaid Dashboard logins via SSO and Google saw elevated error rates from 08:48 to 10:30 UTC on July 16, 2026. Latency lingered after the first mitigation. The cause was not described, and the resolution notice says logins are performing as normal.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Plaid Dashboard SSO and Google logins showed elevated errors and latency for about two hours; the text does not say how many users were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 08:48 UTC · investigating
    We are experiencing elevated error rates on the Plaid Dashboard during SSO and Google logins. We are actively investigating this issue.
  2. 09:22 UTC · identified
    We are experiencing elevated error rates on the Plaid Dashboard during SSO and Google logins. We are working on a resolution.
  3. 09:30 UTC · monitoring
    SSO and Google logins on the Plaid Dashboard are now working with increased latency. We'll continue to monitor until fully recovered.
  4. 10:30 UTC · resolved
    SSO and Google logins in the Plaid Dashboard are now performing as normal.
Source
Jul 12, 20262h 51mSEV 2
Elevated API errorsElevated error rates hit Document Income API calls for about three hours; the text does not say how many customers were affected.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Elevated error rates hit Document Income API calls for about three hours; the text does not say how many customers were affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 03:06 UTC · investigating
    We are currently experiencing elevated error rates for Document Income API calls. We are actively investigating and working to mitigate this issue.
  2. 05:57 UTC · resolved
    This incident has been resolved.
Source
Jul 12, 20263mSEV 2
Service Disruption Impacting Chase connectionsPlaid item adds and API calls for Chase connections failed across all channels and data recipients for about three minutes; other institutions were not described as affected.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Plaid item adds and API calls for Chase connections failed across all channels and data recipients for about three minutes; other institutions were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 00:43 UTC · investigating
    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. 00:45 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –MapboxGrade A+99.99% up2 incidentsMTTR 12h 38mPaddleGrade A+100.00% up3 incidentsMTTR 47mLoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mAblyGrade A99.98% up7 incidentsMTTR 7mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.97% up2 incidentsMTTR 3h 45mInngestGrade B99.63% up14 incidentsMTTR 43mClerkGrade C99.91% up10 incidentsMTTR 3h 26mResendGrade C99.85% up25 incidentsMTTR 24mStytchGrade C99.83% up6 incidentsMTTR 2h 29mWorkOSGrade C99.42% up21 incidentsMTTR 1h 05mTwilioGrade D99.10% up60 incidentsMTTR 6h 43mPlaidGrade D98.13% up18 incidentsMTTR 3h 38m

README badge

Plaid's live grade, for your README.

Plaid grade badge
[![plaid on downagain.dev](https://downagain.dev/badge/plaid.svg)](https://downagain.dev/p/plaid)