outages.live
Live
PlaidIncident · 2026-10-11 08:25 UTC

Service Disruption Impacting Chase connections

ResolvedOfficial update

This incident has been resolved.

The latest update from Plaid.

State

Resolved

Started

21 d ago

2026-10-11 08:25 UTC

Lasted

44 min

until 2026-10-11 09:09 UTC

Worst impact

Partial outage

Timeline

2 updates
08:2508:3608:4708:5809:09
Partial outageUpdate postedTimes in UTC

Investigating

44 min 100%

Updates

Times in UTC

As posted by Plaid

Resolved2026-10-11 09:09 UTC

This incident has been resolved.

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

Plaid in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

22

Median duration

4 h 29 min

This incident

83% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 4 h 29 min
90 days agoToday

Other Plaid incidents

All incidents

Plaid·Service Disruption Impacting Wells Fargo connections

This incident has been resolved.

Resolvedresolved 6 d ago

Plaid·Service Disruption Impacting Chase connections

This incident has been resolved.

Resolvedresolved 10 d ago

Plaid·Service Disruption Impacting Chase connections

This incident has been resolved.

Resolvedresolved 11 d ago

Plaid·Link performance degradation

This incident has been resolved.

Resolvedresolved 17 d ago

Plaid·Elevated API errors

This incident has been resolved.

Resolvedresolved 17 d ago

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.

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

RSS
https://outages.cc/feed.xml?providers=plaid
Slack
/feed subscribe https://outages.cc/feed.xml?providers=plaid

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane