← Back to the carnage
PLAID
⚪ Chase decided to take an unscheduled sabbatical, nuking Plaid connections and API calls across the board. Item adds? Dead. Your financial data pipeline? Also dead. Chase eventually remembered how banking works. (Auto-resolved: no updates in 24h)
// The official story
Service Disruption Impact Chase Customers
// Status page says
Feb 10 , 19:00 UTC Resolved - Chase is currently experiencing downtime impacting all channels and data recipients. Item adds and API calls through Plaid are impacted. We will provide an update when Chase has resolved the issue.
🔗 Official status page (for the PR-approved version)
https://status.plaid.com/incidents/kvb7q3wbmjt1Plaid's Greatest Hits
🟢 PLAID
Sep 17, 2026
🟡 Plaid watching helplessly as Chime goes dark across all channels—your transaction data is taking an unscheduled nap. The 'investigating' phase: that beautiful moment between 'oops' and 'we have no idea.'. (Auto-resolved: no updates in 24h)
🟢 PLAID
Sep 11, 2026
🟡 Plaid's /statements/download endpoint decided to take an unscheduled sabbatical. Engineers are currently playing detective with their own API, which is less 'Sherlock Holmes' and more 'staring at logs while internal Slack burns.'. (Auto-resolved: no updates in 24h)
🟢 PLAID
Aug 16, 2026
🟡 Plaid's API is having trust issues with Navy Federal—item adds and API calls are getting the silent treatment. Apparently their data partner decided to take an unscheduled sabbatical, and nobody told the integration layer. Engineering team is now playing detective in the incident channel. (Auto-resolved: no updates in 24h)
🟢 PLAID
Aug 12, 2026
🔴 Navy Federal Credit Union decided to ghost Plaid harder than a bad Tinder date. Item adds and API calls are DOA while the bank pretends to fix things. Your money's probably fine, but good luck proving it exists. (Auto-resolved: no updates in 24h)