Skip to content

Outage tracker

Plaid: incident history

The last 24 hours in detail, Plaid's declared incident record, and our regional check results beside it.

← Back to Plaid's check readings

We started checking Plaid on August 20, 2026, which is 67 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Plaid reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Plaid's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Plaid's own status page declared. Below it, any public chatter we saw about Plaid and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Plaid's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Plaid in the last 24 hours, which is not evidence that nothing is wrong.
Plaid's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Plaid's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Plaid next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%3105
US-West100.00%3105

Their declared record

Plaid's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Service Disruption Impacting Chase connectionsPartial outage
Oct 22, 2026, 3:34 AM UTC to Oct 22, 2026, 3:52 AM UTC (18 min)resolved
their latest update (Oct 22, 2026, 3:52 AM UTC): This incident has been resolved.
Service Disruption Impacting Chase connectionsPartial outage
Oct 21, 2026, 3:18 AM UTC to Oct 21, 2026, 4:37 AM UTC (1h 19m)resolved
their latest update (Oct 21, 2026, 4:37 AM UTC): This incident has been resolved.
Link performance degradationAll systems operational
Oct 15, 2026, 2:39 PM UTC to Oct 15, 2026, 2:47 PM UTC (9 min)resolved
their latest update (Oct 15, 2026, 2:47 PM UTC): This incident has been resolved.
Elevated API errorsAll systems operational
Oct 14, 2026, 9:27 PM UTC to Oct 14, 2026, 9:59 PM UTC (32 min)resolved
their latest update (Oct 14, 2026, 9:59 PM UTC): This incident has been resolved.
Delayed Transactions Update WebhooksMinor incident
Oct 13, 2026, 7:40 AM UTC to Oct 13, 2026, 8:50 AM UTC (1h 10m)resolved
their latest update (Oct 13, 2026, 8:50 AM UTC): This incident has been resolved and the backlog of delayed transaction updates has cleared. Some customers may have observed elevated `SYNC_UPDATES_AVAILABLE` webhook volume while processing caught up. We did not observe an abnormal increase in webhook delivery failures, and no c…
Service Disruption Impacting Chase connectionsPartial outage
Oct 11, 2026, 8:25 AM UTC to Oct 11, 2026, 9:09 AM UTC (44 min)resolved
their latest update (Oct 11, 2026, 9:09 AM UTC): This incident has been resolved.
Service Disruption Impacting Bank of America connectionsPartial outage
Sep 26, 2026, 3:40 AM UTC to Sep 26, 2026, 5:15 AM UTC (1h 34m)resolved
their latest update (Sep 26, 2026, 5:15 AM UTC): This incident has been resolved.
Service Disruption Impacting Chime connectionsAll systems operational
Sep 17, 2026, 8:22 PM UTC to Sep 18, 2026, 2:23 AM UTC (6h 2m)resolved
their latest update (Sep 18, 2026, 2:23 AM UTC): This incident has been resolved.
Transaction Updates DelayedAll systems operational
Sep 15, 2026, 5:56 PM UTC to Sep 16, 2026, 12:24 AM UTC (6h 28m)resolved
their latest update (Sep 16, 2026, 12:24 AM UTC): This incident has been resolved.
Elevated Item add errorsMinor incident
Sep 15, 2026, 4:31 PM UTC to Sep 15, 2026, 6:45 PM UTC (2h 13m)resolved
their latest update (Sep 15, 2026, 6:45 PM UTC): This incident has been resolved.

Showing the 10 most recent of 37 incidents Plaid has declared in the history we hold.

These entries are Plaid's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Plaid's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.