Plaid Status: How to Check If Plaid API Is Down Right Now (2026)
Updated June 2026 · 7 min read · API Status Check
Quick Answer
Check Plaid API status at status.plaid.com (official) for real-time platform and per-product status. For bank-specific issues, check your Plaid Dashboard for institution-level connectivity.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
The Official Plaid Status Page
Plaid maintains an official status page at status.plaid.com. It tracks status per product and service layer:
What Each Plaid Status Means
Monitor Plaid API health independently
Better Stack monitors Plaid API endpoints from multiple global locations — so you get alerted the moment Plaid degrades, before your users start reporting failed bank connections. Free tier included.
Try Better Stack Free →Institution-Level Issues: The Most Common Plaid Problem
The Plaid platform itself may be healthy while individual bank institutions experience connectivity issues. This is the most common source of Plaid errors for fintech developers:
Per-Institution Connectivity Is Tracked Separately
Plaid connects to thousands of financial institutions. Each bank has its own connection method (screen scraping, direct API, OAuth). When a bank has a maintenance window, updates its website, or experiences IT issues, Plaid's connection to that institution may fail — even though the Plaid platform itself is operational. Check your Plaid Dashboard → Institutions for per-bank connectivity status.
ITEM_LOGIN_REQUIRED Errors
The most common Plaid error is ITEM_LOGIN_REQUIRED — the user's bank credentials or OAuth session have expired and they need to re-authenticate. This is not a Plaid outage. Handle this by listening for the ITEM webhook with error.error_code = 'ITEM_LOGIN_REQUIRED' and prompting the user to re-link their account via Plaid Link update mode.
INSTITUTION_DOWN Errors
If Plaid returns an INSTITUTION_DOWN error code, the specific bank institution is unavailable through Plaid. This is institution-side, not Plaid platform. Users will need to retry once the institution recovers. Surface a clear user message: 'Your bank is temporarily unavailable. Please try again in a few hours.'
OAuth Bank Connections
Major banks (Chase, Bank of America, Wells Fargo, etc.) use OAuth with Plaid — users authenticate directly on their bank's website. OAuth sessions expire, and users periodically need to re-authorize. Additionally, when a bank updates their OAuth implementation, all existing items may be invalidated simultaneously, causing a spike in ITEM_LOGIN_REQUIRED errors that looks like a Plaid outage but is actually a bank-side session reset.
5 Ways to Check Plaid Status Right Now
Official Plaid Status Page
Visit status.plaid.com for real-time per-product status. Subscribe to email notifications for instant outage alerts.
status.plaid.com →Plaid Dashboard Institution Status
Log into your Plaid Dashboard and check the Institutions section. Per-institution connectivity issues are tracked separately from platform health and are the most common cause of bank connection failures.
Plaid Dashboard →Test the Plaid API Directly
Call a lightweight Plaid endpoint to verify API health:
# Test Plaid API health (requires sandbox credentials)
curl -s -o /dev/null -w "%{http_code} — %{time_total}s\n" \
-X POST https://sandbox.plaid.com/link/token/create \
-H "Content-Type: application/json" \
-d '{"client_id":"CLIENT_ID","secret":"SECRET","client_name":"Test","user":{"client_user_id":"test"},"products":["auth"],"country_codes":["US"],"language":"en"}'
# 200 = healthy APISearch X/Twitter
Search 'Plaid down' or 'Plaid not working' on X. Fintech developers report Plaid issues immediately on social media, often before status page updates.
Search X for 'plaid down' →Monitor Your Own Error Rates
Track your Plaid API error rates in your application metrics. A spike in PLAID_ERROR or INSTITUTION_DOWN errors in your logs is often the earliest signal of a Plaid incident — faster than the public status page update.
Common Plaid Errors During Outages
These are the errors and symptoms you'll encounter when Plaid or connected institutions are experiencing issues:
"INSTITUTION_DOWN / institution unavailable"The specific bank institution is temporarily unavailable through Plaid. Not a Plaid platform issue. Surface a user-friendly message and prompt the user to retry in a few hours. Monitor institution status in your Plaid Dashboard."ITEM_LOGIN_REQUIRED / credentials expired"The user's bank credentials or OAuth authorization has expired. Trigger Plaid Link in update mode to prompt re-authentication. This is expected behavior, not an outage — handle it proactively with webhook listeners."PLAID_ERROR / API request failed"Generic Plaid API error during a platform incident. Check status.plaid.com for active incidents. Implement exponential backoff and retry for read operations. For write operations (payment initiation), verify idempotency before retrying."Plaid Link not loading / blank modal"Plaid Link is served via a JavaScript CDN. If your CSP blocks Plaid domains, Link will fail silently. Check browser console for blocked resource errors. Also check status.plaid.com for Link service degradation."Webhook not received / delayed webhook delivery"Plaid webhook delivery may be delayed during incidents. Check status.plaid.com for webhook service issues. Implement a polling fallback using /transactions/sync for critical financial data rather than depending solely on webhooks."PRODUCTS_NOT_SUPPORTED for a specific institution"The requested Plaid product (e.g., Investments or Liabilities) is not supported for the user's specific bank. Not an outage — this is a permanent limitation. Check Plaid's institution coverage data to verify which products work with which banks.What to Do When Plaid Is Down
Immediate Response
- Check status.plaid.com and your Plaid Dashboard institution status
- Distinguish platform outage from institution-specific issue — handle them differently
- Surface a clear user-facing error: "Bank connection temporarily unavailable, please try again later"
- Pause any automated payment initiations that depend on real-time Plaid data
- Document the incident timeline for any regulatory reporting requirements
Long-Term Resilience
- Monitor Plaid API error rates in your own application metrics
- Implement polling fallback alongside webhooks for critical data
- Cache the last-known-good transaction data to serve during outages
- Handle ITEM_LOGIN_REQUIRED proactively — don't wait for users to complain
- Consider a secondary data provider for critical institution coverage
Frequently Asked Questions
Where is the official Plaid status page?
Plaid's official status page is at status.plaid.com. It tracks real-time health per product: Plaid Link, Transactions, Auth, Identity Verification, Income, Investments, Liabilities, and Webhooks. For bank-level issues, check your Plaid Dashboard's institution connectivity page.
Is Plaid down or is it just my bank?
If a single bank is affected but others work, it is a bank-level institution issue — not a Plaid outage. If multiple banks fail simultaneously in your app, or if you get PLAID_ERROR responses unrelated to specific institutions, it is likely a Plaid platform issue. Check status.plaid.com and your institution dashboard to distinguish the two.
How long do Plaid outages typically last?
Minor Plaid API degradations typically resolve within 15–30 minutes. Full platform outages are rare and typically resolve within 1–2 hours. Institution-specific connectivity issues vary widely — they depend on the bank's own recovery timeline, which can range from hours to days for major bank IT incidents.
Does Plaid retry failed webhook deliveries?
Yes — Plaid retries webhook deliveries with exponential backoff for delivery failures. However, during severe platform outages, webhook delivery may be paused entirely. After recovery, Plaid typically sends a catch-up batch of missed webhooks. Build your webhook handlers to be idempotent — the same event may be delivered more than once.
How do I handle Plaid downtime in my fintech app?
Best practices: (1) Show graceful user-facing errors rather than raw API errors. (2) Cache the last-known-good account balance and transaction data. (3) Implement retry logic with exponential backoff in your Plaid API client. (4) Monitor your own error rates — don't depend solely on status.plaid.com for awareness. (5) For payment-critical flows, implement manual fallback options (CSV upload, manual entry) as a backup during outages.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Plaid goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Plaid + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial