Is Plaid Down? How to Check Plaid Status Right Now

Plaid is the infrastructure layer that connects your financial app to your users' bank accounts. When Plaid is working, account linking is seamless, transactions sync in seconds, and your identity and balance checks complete silently in the background. When Plaid goes down, onboarding stalls, payment flows break, and users see cryptic bank connection errors. The failure is immediate because it sits directly in the critical path of account creation and fund movement.

Here's how to determine whether Plaid is down, identify which component is failing, and protect your users when Plaid degrades.

Is Plaid Down Right Now?

Check these sources in order:

1. Statusfield — Plaid status — real-time monitoring across Plaid's Link, API, webhooks, and data enrichment services.
2. Twitter/X — search Plaid down or Plaid Link not working sorted by Latest. Fintech developers post about Plaid failures quickly, especially Link UI issues that affect onboarding.
3. Downdetector — useful for confirming consumer-facing impact, though it lacks the component-level granularity needed for API-layer debugging.

What Actually Breaks During a Plaid Outage

Plaid is composed of several independent subsystems, and degradation is often component-specific.

Component	What it does	Impact when down
Plaid Link	Browser/mobile OAuth UI for bank account selection and authentication	Account linking flows stall at the bank selection or authentication screen; onboarding drops
Auth	Returns account and routing numbers for ACH transfers	ACH payment initiation fails; direct deposit setup breaks
Transactions	Fetches transaction history from connected accounts	Transaction sync stalls; spending history shows stale or missing data
Balance	Real-time account balance checks	Pre-payment balance checks fail; apps block transfers that should proceed
Identity	Returns account holder name and address	KYC flows fail; identity verification returns errors
Income & Assets	Verifies income streams and asset balances	Underwriting flows break; loan or credit applications stall
Investments	Returns brokerage holdings and transaction history	Portfolio syncing fails; investment dashboards show stale data
Webhooks	Notifies your server when transactions update, items require re-auth, etc.	Your app stops receiving real-time updates; re-auth prompts aren't surfaced to users
Item management	Manages connected institution connections (Items)	Reconnection flows fail; expired tokens can't be refreshed

Common Plaid Error Symptoms

What you see	What it usually means
INSTITUTION_DOWN error in Link	The specific bank's connection to Plaid is degraded — not all of Plaid
INSTITUTION_NOT_RESPONDING	Bank API is timing out on Plaid's side
ITEM_LOGIN_REQUIRED on fresh connections	OAuth session or credential update required — usually account-level, not a Plaid outage
PRODUCT_NOT_READY on Transactions	Transaction data is still being fetched; not an outage — retry after the initial update completes
500 or 503 from Plaid API	Plaid's API layer is degraded
Link opens but bank search returns no results	Link's institution search service is degraded
Webhooks not arriving after confirmed transactions	Webhook dispatch is degraded; events are queued or dropped
access_token exchange failing after Link success	Token exchange endpoint is degraded post-Link-completion

Key distinction: INSTITUTION_DOWN and INSTITUTION_NOT_RESPONDING are bank-level errors, not Plaid outages. If you're seeing these for one institution (e.g., Chase, Wells Fargo) but others work, the issue is with that institution's connection, not Plaid's infrastructure. If multiple institutions fail simultaneously, it's more likely a Plaid platform issue.

How Plaid's Architecture Affects Outage Scope

Link is a separate UI service from the API. Plaid Link (the browser/mobile widget) is served from Plaid's CDN and runs independently of the API. A Link UI degradation can occur while the backend API is fully operational, and vice versa. If users can't open Link but your API calls are succeeding, the issue is in Link's asset delivery, not the data API.

Each product (Transactions, Auth, Balance) is an independent service. A Transactions outage does not imply Auth is down. Scope your debugging to the specific product that's failing. Plaid's status page typically reflects this granularity — check it against which endpoint you're actually calling.

Webhooks run asynchronously and are not delivery-guaranteed. Plaid's webhook system delivers events on a best-effort basis. During partial outages, webhooks may queue and deliver late, or drop silently. Do not rely on webhooks as the sole mechanism for detecting account updates; poll Plaid's API periodically as a fallback.

Institution connections vary by institution. Plaid connects to each bank differently — some via OAuth (screen scraping-free, more stable), others via credential-based scraping. Institution-specific failures are common and do not reflect Plaid's core infrastructure health. If one bank is failing, check whether that institution is on Plaid's OAuth integration list.

Is It Plaid or Your Configuration?

Before concluding it's a Plaid outage, rule out these configuration issues:

Your client_id or secret is wrong or belongs to the wrong environment. Sandbox credentials do not work against Production endpoints. A INVALID_API_KEYS or 401 response means credentials mismatch, not a Plaid outage.

Your Item is in an error state. Items can enter ITEM_LOGIN_REQUIRED or ITEM_ERROR states when the user's bank credentials change or MFA is required. These are account-level failures — use a webhook or poll /item/get to detect them. Fixing them requires the user to re-authenticate via Link.

Your webhook URL is unreachable from Plaid. If your webhook endpoint is behind a firewall or requires auth headers that Plaid doesn't send, Plaid cannot deliver events. Verify your endpoint accepts Plaid's POST requests and returns 200.

You're in Sandbox but testing with non-Sandbox test credentials. Plaid's Sandbox uses fixed test credentials (e.g., user_good / pass_good). Any other credentials fail in Sandbox — this is expected behavior, not an outage.

When these are ruled out and failures persist across products or institutions, check Statusfield to confirm whether it's a Plaid platform issue.

Hardening Your App Against Plaid Outages

Plaid sits in the critical path of onboarding and payments. These steps reduce user impact when it degrades.

1. Design Link to handle partial failure gracefully

When Link fails to open or exits with an error, surface a clear message to the user rather than a blank screen. Return users to a retry flow. For non-blocking use cases (e.g., optional account linking), allow users to continue without completing Link.

2. Don't block critical flows on Plaid responses

For balance checks used to gate payments, implement a fallback path when Plaid returns a timeout or error — either allow the payment with a risk check, or queue it for retry. Blocking a payment entirely on a Plaid API failure is worse than proceeding with elevated monitoring.

3. Store Plaid data locally and refresh on demand

Cache the last-known balance, transaction list, and identity data. Serve cached data when Plaid is unreachable, with a clear "as of [timestamp]" label. This keeps your app functional during short outages without exposing stale data as current.

4. Poll for transaction updates, don't depend only on webhooks

Implement a daily or hourly job that calls /transactions/sync for active Items, regardless of whether webhooks arrived. Treat webhooks as the fast path and polling as the reliable path.

5. Monitor Plaid like a critical infrastructure dependency

Plaid failures directly block onboarding and payments. Statusfield monitors Plaid's API, Link, and webhook systems continuously, alerting you the moment status changes — through Slack, Discord, email, or webhook.

How to Stay Ahead of Plaid Outages

The goal is to know Plaid is degraded before your users hit a broken onboarding flow or a failed payment.

Statusfield monitors Plaid continuously and delivers alerts the moment a degradation is detected. On the free plan you get 3 monitors and 10 alerts/month, no credit card required.

→ Monitor Plaid on Statusfield — free, no credit card required

FAQ

Why is Plaid Link not loading for my users?

Plaid Link is served as a browser widget from Plaid's CDN. If Link fails to load, check whether your Content Security Policy (CSP) is blocking Plaid's domains (cdn.plaid.com, production.plaid.com). Also check for browser extensions interfering with iframe loading. If CSP and extensions are ruled out, check Statusfield to see if Link is experiencing a platform-level degradation.

Is Plaid down or is it just one bank?

Check Statusfield. If the issue is isolated to one institution (e.g., Chase), you'll typically see INSTITUTION_DOWN or INSTITUTION_NOT_RESPONDING errors — these are bank-level, not Plaid platform failures. If multiple institutions are failing simultaneously or your API calls are returning 5xx errors regardless of institution, it's more likely a Plaid infrastructure issue.

Plaid webhooks stopped arriving. Is Plaid down?

Not necessarily. Webhook dispatch is asynchronous and can degrade independently of Plaid's API. Check Statusfield for webhook-specific status. Also verify your webhook endpoint is returning 200 responses — Plaid may stop delivering to endpoints that return errors consistently. As a fallback, poll /transactions/sync or /item/get directly to check for updates.

How do I tell if a Plaid error is my fault or Plaid's?

Plaid's error codes follow a consistent taxonomy. Errors in the INSTITUTION_* family are bank-side issues. INVALID_API_KEYS and INVALID_INPUT are configuration problems on your side. INTERNAL_SERVER_ERROR and API_ERROR codes are Plaid platform issues. If you see INTERNAL_SERVER_ERROR responses that are not isolated to one institution, confirm on Statusfield.

How long do Plaid outages typically last?

Component-specific degradations (e.g., Transactions lagging, webhook delays) typically resolve within 30–90 minutes. Full platform outages affecting Link and the core API are rare and typically resolve within 1–2 hours. Institution-specific issues can last longer depending on the bank's own infrastructure. Monitor Statusfield for live status during an incident.