Plaid did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-11-12 15:59 UTC and ended at 2026-11-12 16:39 UTC. It lasted 39 min.

How do I get alerts for Plaid?

Subscribe to the Plaid live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Plaid. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

PlaidIncident ·

Elevated /signal/evaluate errors

Q: What happened?

Plaid reported "Elevated /signal/evaluate errors" on its status page at 2026-11-12 15:59 UTC. Plaid reported elevated errors on the /signal/evaluate endpoint. Plaid identified the cause and applied a mitigation. The incident is resolved and lasted 39 minutes.

ResolvedOfficial update

Plaid reported elevated errors on the /signal/evaluate endpoint. Plaid identified the cause and applied a mitigation. The incident is resolved and lasted 39 minutes.

State

Resolved

Started

Lasted

39 min

Worst impact

Degraded

Timeline

3 updates

15:5916:0916:1916:2916:39

DegradedUpdate postedTimes in UTC

Identified

12 min 32%

Monitoring

27 min 68%

Updates

Times in UTC

As posted by Plaid

Resolved

We have mitigated the root cause of the /signal/evaluate failures and ensured we will not regress.

Monitoring

We have mitigated the cause of /signal/evaluate requests elevated error rates. We are actively monitoring the mitigation to prevent any regression.

Identified

/signal/evaluate requests are experiencing elevated error rates. We are actively investigating and working to mitigate this issue.

Plaid in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 34 min

This incident

58% 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 1 h 34 min

90 days agoToday

Other Plaid incidents

All incidents

Plaid·Transfer RTP Requests are Temporarily Disabled for Some Customers

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.

Resolved

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

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