Is Plaid down?
For agents
proceed
Proceed.
GET upbutler.com/status/plaid/status.agent.json
MCP: upstream_status {"service":"plaid"}
Bank account linking and financial data APIs.
What Plaid reports
Operational
Taken as is from Plaid's own status page API. Incident titles and component names below are theirs.
Open status.plaid.comUpButler's independent probe
There is no keyless endpoint of Plaid that says anything useful, so UpButler does not probe it. To check your own Plaid account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Plaid components
4 operational
- API - ProductionOperational
- API - SandboxOperational
- DashboardOperational
- Plaid PortalOperational
Plaid incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Plaid.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Service Disruption Impacting Bank of America connections | major | 1 h 34 min |
Tell your outage from Plaid's
Declare that your project depends on Plaid. When one of your monitors fails while Plaid has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- plaidcurl -s https://upbutler.com/status/plaid/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "plaid",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Plaid down right now?
- No. As of 2026-10-10 05:09 UTC, Plaid is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Plaid's own status page API at https://status.plaid.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Plaid's words.
- How can my agent or app check Plaid status?
- Fetch https://upbutler.com/status/plaid/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"plaid"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Plaid's?
- Add "plaid" to the dependencies of your UpButler workspace. When one of your monitors fails while Plaid has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in payments and commerce
UpButler is not affiliated with Plaid. Status and incident text belong to Plaid and are read from their public status source; the probe result is UpButler's own measurement.