outages.live
Live
PlaidIncident ·

Transfer RTP Requests are Temporarily Disabled for Some Customers

ResolvedOfficial update
0

Plaid disabled Transfer RTP requests for some customers. Other payment rail types worked. Plaid reports that the incident is resolved, and it lasted 69 minutes.

State

Resolved

Started

Lasted

1 h 9 min

Worst impact

Partial outage

Timeline

2 updates
16:4116:5817:1617:3317:50
Partial outageUpdate postedTimes in UTC

Identified

1 h 9 min 100%

Updates

Times in UTC

As posted by Plaid

Resolved

This incident has been resolved.

Identified

Transfer RTP requests are temporarily disabled for some customers. Transfer will resume full RTP activity in a couple of hours. Other payment rail types are fully functional.

Plaid in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

21

Median duration

2 h 56 min

This incident

61% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

15 h 37 min
median 2 h 56 min
90 days agoToday

Other Plaid incidents

All incidents

Plaid·Service Disruption Impacting Wells Fargo connections

This incident has been resolved.

Resolved

Plaid·Service Disruption Impacting Chase connections

This incident has been resolved.

Resolved

Plaid·Service Disruption Impacting Chase connections

This incident has been resolved.

Resolved

Plaid·Link performance degradation

This incident has been resolved.

Resolved

Plaid·Elevated API errors

This incident has been resolved.

Resolved

Follow Plaid

Your coding agent knows when Plaid is down, and tells you when a failure is theirs, not yours. You can also get Plaid incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "plaid" and tell me if Plaid has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=plaid
Slack
/feed subscribe https://outages.live/feed.xml?providers=plaid

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane