Plaid experienced a critical incident on October 21, 2025 affecting API - Production, lasting 15h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 03:56 PM UTC
The Transfer API is currently experiencing a degradation, and requests may fail with a 500 HTTP status error code. We are actively investigating and will update this incident as we have more updates. For more information on how to handle 500s, please see the documentation here: https://plaid.com/docs/transfer/troubleshooting/#handling-500-errors-in-transfer-creation
- monitoring Oct 20, 2025, 07:15 PM UTC
We're seeing recovery across endpoints and will continue to monitor.
- investigating Oct 20, 2025, 09:05 PM UTC
Instant Payment Transfer rails are temporarily unavailable. This applies to Instant Payouts (RTP and FedNow) and RfP (Request for Payments). ACH Transfer creation requests will be accepted as usual via /transfer/create, but processing these payments might be delayed. We are actively monitoring and will update this incident as it is resolved. We will provide an update if any ACH settlement windows are missed. Once the incident is resolved, you may retry failed requests using identical idempotency keys.
- investigating Oct 20, 2025, 11:05 PM UTC
Automated deposits and withdrawals are delayed until tomorrow
- monitoring Oct 21, 2025, 01:42 AM UTC
Transfer processing across all rails — ACH, RTP, RfP, and Wires — is now fully restored. We are gradually processing all creation requests submitted during the incident period. New originations should function normally, though some may experience additional delays as we work through the backlog.
- monitoring Oct 21, 2025, 01:42 AM UTC
We are continuing to monitor for any further issues.
- investigating Oct 21, 2025, 02:57 AM UTC
We are actively investigating an elevated error rates on the /transfer/authorization/create endpoint. This will result in increased responses with "decision=approved" and "decision_rationale.code=ERROR".
- monitoring Oct 21, 2025, 05:09 AM UTC
We're seeing recovery and will continue to monitor.
- resolved Oct 21, 2025, 05:22 PM UTC
This incident has been resolved.