Delayed Capital One Transactions Updates
All Delayed Transactions have now been fully processed.
The latest update from Plaid.
State
Resolved
Started
88 d ago
2026-08-05 01:01 UTC
Lasted
6 days
until 2026-08-10 17:39 UTC
Worst impact
Notice
Timeline
5 updatesInvestigating
1 h 39 min 1%
Identified
17 h 12 min 13%
Monitoring
5 days 86%
Updates
Times in UTCAs posted by Plaid
All Delayed Transactions have now been fully processed.
We've addressed the underlying cause and are currently monitoring for the resolution.
We have identified the root cause of the issue and are actively working to mitigate the impact.
We have identified the root cause of the issue and are actively working to mitigate the impact.
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.
Plaid in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
22
Median duration
4 h 29 min
This incident
31× the median
Other Plaid incidents
All incidentsPlaid·Service Disruption Impacting Wells Fargo connections
This incident has been resolved.
Plaid·Service Disruption Impacting Chase connections
This incident has been resolved.
Plaid·Service Disruption Impacting Chase connections
This incident has been resolved.
Plaid·Link performance degradation
This incident has been resolved.
Plaid·Elevated API errors
This incident has been resolved.
Follow Plaid
Your coding agent knows when Plaid is down, and tells you when a failure is theirs, not yours. You can also get Plaid incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "plaid" and tell me if Plaid has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=plaid/feed subscribe https://outages.cc/feed.xml?providers=plaidFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane