Plaid Outage History

Chase experienced downtime that prevented users from adding new bank account connections through Plaid's service. The disruption affected all channels and data recipients trying to link Chase accounts. The issue was resolved by Chase after 9.5 hours, restoring normal functionality for new account connections.

Plaid's Link service experienced elevated error rates for 4.1 hours due to AT&T messaging issues, causing some users to miss text messages. The API Production component was affected during this period. The issue has been mitigated and resolved.

Plaid's Link Analytics chart in the Dashboard incorrectly displayed a 100% error rate starting March 31, affecting data visualization accuracy for users monitoring their integration performance. The issue was identified and actively investigated by the Plaid team. The incident was resolved within 22 minutes of being reported.

Plaid experienced elevated latency for INITIAL_UPDATE and HISTORICAL_UPDATE Transactions webhooks affecting their production API. The latency issues impacted webhook delivery performance for approximately 8 minutes. The incident was resolved after active investigation and mitigation efforts.

Plaid experienced delays in transaction updates affecting their Production API for 9.4 hours. The underlying issue was resolved, though transaction updates continued to be delayed for several additional hours during system recovery. The incident was classified as minor severity.

Plaid experienced elevated error rates affecting API calls to /user/* endpoints for 1.6 hours. The issue impacted the production API service, causing failures for user-related requests. The problem was resolved and Plaid advised customers to retry any failed /user/* requests.

Wells Fargo experienced downtime that disrupted all channels and data recipients, preventing users from adding new items through Plaid's service. The outage lasted 2.1 hours and affected all Wells Fargo connections via Plaid. The incident was resolved once Wells Fargo restored their services.

Plaid experienced elevated error rates in their Dashboard service for 4.4 hours. The issue was classified as major and affected users' ability to access dashboard functionality normally. The problem was mitigated and resolved after active investigation and monitoring during recovery.

Plaid experienced elevated error rates in their Dashboard service for 40 minutes. The issue affected users' ability to access or use the Dashboard functionality normally. The problem was mitigated and then fully resolved, with Plaid monitoring systems during recovery.

Plaid experienced a service disruption affecting connections to Fidelity and Fidelity NetBenefits institutions, impacting item adds and API requests through their production API. The issue lasted approximately 1.2 hours before being resolved, with normal operations restored and continued monitoring in place.