Service Disruption Impacting Chase connections
Plaid reported a service disruption that affected Chase connections, including item adds and API calls. Plaid later said that Chase fixed the intermittent errors. The incident is resolved for Plaid and lasted about 9 hours and 23 minutes.
State
Resolved
Started
Lasted
9 h 23 min
Worst impact
Partial outage
Timeline
4 updatesInvestigating
9 h 23 min 100%
Updates
Times in UTCAs posted by Plaid
The intermittent errors on Chase's side have been resolved. This is resolved now for Plaid.
We are seeing intermittent errors for a small percentage of users due to issues on Chase's side.
Chase is currently experiencing downtime impacting all channels and data recipients for a small percentage of users.
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.
Plaid in the last 90 days
Full historyIncidents in 90 days
15
Days with an incident
17
Median duration
1 h 34 min
This incident
6.0× the median
Other Plaid incidents
All incidentsPlaid·Elevated /signal/evaluate errors
Plaid reported elevated errors on the /signal/evaluate endpoint. Plaid identified the cause and applied a mitigation. The incident is resolved and lasted 39 minutes.
Plaid·Transfer RTP Requests are Temporarily Disabled for Some Customers
Plaid disabled Transfer RTP requests for some customers. Other payment rail types worked. Plaid reports that the incident is resolved, and it lasted 69 minutes.
Plaid·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.
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.live/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.live/feed.xml?providers=plaid/feed subscribe https://outages.live/feed.xml?providers=plaidFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane