CheckUpstream measured Plaid at 100.000% availability across 2823 independent checks (global · api). 25 incidents were recorded in the past 12 months; the most recent resolved 15 days ago after 4 hours. Status signals are polled from Plaid's official Atlassian Statuspage status page, alongside independent probes and community reports.
180 days measured availability how this is computed
100.000%
global · api · n=2823 · p95 775ms (30d)
Share of our own checks against Plaid endpoints that returned Plaid's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 16 incidents · 167 of 180 days with none posted · 1d 12h of declared impact
Fewer incidents in the last 30 days than 11% of 232 tracked services.
Share of each window with no impact declared by Plaid
7d
100.000%
30d
97.260%
90d
98.853%
180d
99.144%
1y
99.578%
Downtime like this can be refundable
If you're a paying Plaid customer, outages in these windows may count against Plaid's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Plaid entitlement →Does Plaid actually matter to you?
A Plaid outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 16 incidents Plaid published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Plaid takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 16, 15:13 UTC · resolved in 3h 46m · Resolved
Aug 14, 20:10 UTC · resolved in 29m · Resolved
Aug 12, 21:48 UTC · resolved in 21m · Resolved
Aug 7, 16:47 UTC · resolved in 28m · Resolved
Live Plaid status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/plaid)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Plaid is currently Operational. CheckUpstream tracks Plaid in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Plaid's last resolved incident started 15 days ago and lasted 3h 46m (a partial outage).
Looking for the live "is Plaid down" view? See the Plaid Live status page.
Aug 7, 14:50 UTC · resolved in 20m · Resolved
Aug 6, 20:30 UTC · resolved in 29m · Resolved
Aug 5, 01:01 UTC · resolved in 29m · Resolved
Aug 4, 22:31 UTC · resolved in 24m · Resolved
Aug 2, 14:51 UTC · resolved in 22h 8m · Resolved
Aug 1, 01:34 UTC · resolved in 1h 26m · Resolved
Jul 27, 16:34 UTC · resolved in 6h 36m · Resolved
Apr 29, 02:41 UTC · resolved in 48m · Resolved
Apr 23, 14:57 UTC · resolved in 7h 32m · Resolved
Apr 18, 03:45 UTC · resolved in 4h 4m · Resolved
Apr 1, 21:02 UTC · resolved in 11m · Resolved
Mar 27, 17:06 UTC · resolved in 4h 30m · Resolved
Plaid's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Plaid endpoints. It is the share of checks that returned the expected response, not a figure taken from Plaid's status page.
Sign up to CheckUpstream and add Plaid to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Plaid's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.