Loading status…
Plaid status · Payments & Finance · checked (3s ago)
No — Plaid is not down. All Plaid systems are reported operational.
According to Plaid's official status page, Plaid was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Plaid's feed reported no outage in 100.00% of our checks.
Everything above is read from Plaid's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Plaid in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Plaid connects applications to bank accounts — authentication, balances, transactions and payment initiation — and is the layer behind most fintech products that ask you to link a bank. It sits between the app and thousands of financial institutions.
The status page covers Plaid's own APIs and Link. What it cannot cover is the more common failure: individual bank integrations break constantly, because banks change their login flows, add authentication steps and go down themselves. Plaid publishes institution-level health separately, and an outage at one bank is invisible on this page.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Plaid's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Plaid was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 3s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Plaid's status endpoint.
Plaid has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Plaid posted itself — not every problem users hit.
resolved · Sep 17, 08:22 PM (2d ago)
resolved · Sep 15, 05:56 PM (4d ago)
resolved · Sep 15, 04:31 PM (4d ago)
resolved · Sep 11, 04:56 PM (8d ago)
resolved · Aug 24, 05:36 AM (27d ago)
resolved · Aug 16, 03:13 PM (34d ago)
resolved · Aug 12, 09:48 PM (38d ago)
resolved · Aug 5, 01:01 AM (46d ago)
resolved · Aug 2, 02:51 PM (48d ago)
resolved · Aug 1, 01:34 AM (50d ago)
resolved · Jul 27, 04:34 PM (54d ago)
resolved · Jul 23, 08:36 PM (58d ago)
resolved · Jul 23, 11:41 AM (58d ago)
resolved · Jul 22, 02:58 PM (59d ago)
resolved · Jul 17, 11:59 PM (64d ago)
resolved · Jul 16, 08:48 AM (65d ago)
resolved · Jul 12, 03:06 AM (70d ago)
resolved · Jul 12, 12:43 AM (70d ago)
resolved · Jul 11, 01:56 AM (71d ago)
resolved · Jul 10, 06:46 PM (71d ago)
Check the specific institution rather than Plaid — a link failing for one bank while others work is the bank, and that is the usual case. Items requiring re-authentication after a password or MFA change surface as errors that look like outages. Sandbox and development environments have different behaviour and limits from production, which catches integration work regularly.
