Service Disruption Impacting Chase connections
OutageThis incident has been resolved.
Plaid is up and running. Plaid connects apps to users' bank accounts.
Worked out from the incidents Plaid reported, so it is an estimate and not a measurement.
Last incident: “Service Disruption Impacting Chase connections”, 2 days ago.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been 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.
Plaid’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Plaid reported was “Service Disruption Impacting Chase connections”, 2 days ago (2026-10-22 03:34 UTC). Its last full outage started 2 days ago.
Plaid reports 4 components on its status page, including API - Production, API - Sandbox, Dashboard, Plaid Portal. Each is checked again whenever this page refreshes.
Do not retry a payment that may have gone through; check the dashboard first, and keep orders pending until the provider confirms.
No — 'API - Sandbox' and 'API - Production' are separate components. Sandbox incidents don't touch production Link sessions.
The Link front-end and the core API can degrade separately; also check the 'Dashboard' and 'Portal' rows — console tools are tracked apart from the API.
If the status above is operational but Plaid still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.