Vendor Status Watch

← all vendors

Plaid status history

Current state: operational — “All Systems Operational” per https://status.plaid.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

4incidents, last 30 days
21incidents, last 90 days
28incidents on record
Incidents per week, last 12 weeks:
Get Plaid alerts in your Slack — free templateRSS for Plaid

How long do Plaid incidents last?

3.3 hmedian incident duration27 measured
16.1 h90th percentile1 in 10 ran longer
102 minmedian, major/critical only7 incidents

From 27 incidents with a vendor-posted start and resolve time. Longest on record: Delayed Capital One Transactions Updates — 5.7 days (2026-08-05 01:01 UTC). Excluded, never estimated: 1 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (28)

StartedIncidentStatusImpactDuration
2026-09-15 17:56 UTCTransaction Updates Delayedresolvednone6 h 27 min
2026-09-15 16:31 UTCElevated Item add errorsresolvedminor2 h 13 min
2026-09-11 16:56 UTCStatements API downtimeresolvednone5 h 19 min
2026-08-24 05:36 UTCElevated API errorsresolvedminor15 h 36 min
2026-08-16 15:13 UTCService Disruption Impacting Navy Federal Credit Union connectionsresolvedminor3 h 37 min
2026-08-12 21:48 UTCService Disruption Impacting Navy Federal Credit Union connectionsresolvednone8 h 19 min
2026-08-05 01:01 UTCDelayed Capital One Transactions Updatesresolvednone5 d 16 h
2026-08-02 14:51 UTCService Disruption Impacting Bank of America connectionsresolvedmajor22 h 01 min
2026-08-01 01:34 UTCpython SDK degraded on Identity Verification APIsresolvedminor1 h 22 min
2026-07-27 16:34 UTCVirtual Account perfomance degradation (UK and Europe)resolvednone16 h 06 min
2026-07-23 20:36 UTCTransfer Status Upates Delaysresolvednone1 h 22 min
2026-07-23 11:41 UTCPayouts/Refunds API degradedresolvednone2 h 52 min
2026-07-22 14:58 UTCTransaction Updates Delayedresolvedminor43 h 03 min
2026-07-17 23:59 UTCLink performance degradationresolvednone1 h 39 min
2026-07-16 08:48 UTCElevated dashboard.plaid.com error ratesresolvedmajor1 h 42 min
2026-07-12 03:06 UTCElevated API errorsresolvednone2 h 51 min
2026-07-12 00:43 UTCService Disruption Impacting Chase connectionsresolvedmajor2 min
2026-07-11 01:56 UTCService Disruption Impacting Wells Fargo connectionsresolvedmajor19 min
2026-07-10 18:46 UTCIDV Performance Degradationresolvednone2 h 53 min
2026-07-10 16:51 UTCElevated Item add errorsresolvedminor4 h 46 min
2026-07-10 16:04 UTCService Disruption Impacting Wells Fargo connectionsresolvedmajor3 h 18 min
2026-06-08 18:53 UTCElevated Item add errorsresolvedminor3 min
2026-06-05 02:24 UTCService Disruption Impacting Wells Fargo connectionsresolvedmajor3 h 57 min
2026-05-26 23:13 UTCIssues retrieving invoices on the Dashboard Billing pageresolvednone—
2026-05-26 22:42 UTCService Disruption Impacting Chase connectionsresolvednone1 h 19 min
2026-05-26 22:33 UTCService Disruption Impacting Chase connectionsresolvedmajor8 min
2026-05-21 19:36 UTCIncreased Transactions webhook latencyresolvednone4 h 53 min
2026-05-21 19:33 UTCTransaction Updates Delayedresolvednone4 h 57 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Plaid with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "plaid"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}