Plaid is down: what we know so far
This page is live and updates as StatusBird re-checks Plaid, every 2 minutes. First non-operational reading 02:05 UTC on October 26, 2026.
StatusBird recorded its first non-operational reading for Plaid at 02:05 UTC on 26 October 2026. The worst status we measured was major. We poll every two minutes, and we have recorded 30 non-operational readings, covering one hour. The problem was still running when this was written, so we have not observed a recovery. Plaid's status page showed no incident.
Incident at a glance
| Service | Plaid |
|---|---|
| Date | October 26, 2026 |
| StatusBird first saw it | 02:05 UTC |
| Vendor posted an incident | Not published |
| Recovery observed | Not yet |
| Duration | 3 hours 10 minutes and counting |
| Worst status observed | major |
| Non-operational readings | 95 |
All times UTC. StatusBird polls Plaid every 2 minutes from its own infrastructure, so the true start and end sit within 2 minutes of the times above.
Was Plaid down on October 26, 2026?
Yes. StatusBird recorded Plaid as major from 02:05 UTC, and it was still non-operational 3 hours 10 minutes later at the most recent reading. 95 consecutive checks came back non-operational.
Customers may not be able to complete purchases.
What caused the Plaid outage?
No cause is known. Plaid had posted no incident on its status page when this was written, and it has published no explanation. We will not guess at what went wrong. Everything above comes from our own checks of the service, not from the vendor.
The cause has not yet been published by Plaid. StatusBird measures availability from outside the vendor, which shows when a service stopped responding normally but never why. This section is updated if Plaid publishes a root cause.
How long was Plaid down?
3 hours 10 minutes so far, measured from the first non-operational reading at 02:05 UTC to the most recent reading, which was still non-operational. StatusBird counts a service down from the first reading it fails, not from the moment the vendor admits it, which is why this number can be larger than the one on the vendor's own incident report.
Timeline, in UTC
| Time (UTC) | Event |
|---|---|
| 02:05 UTC | StatusBird records its first non-operational reading |
| 02:08 UTC | A second consecutive non-operational reading confirms the outage, alerts go out and this page is published |
| 05:15 UTC | Still non-operational at the last reading |
Who and what was affected
This affects stores that rely on Plaid to take payment. During the readings we recorded, customers may not have been able to complete purchases, so checkout attempts can fail at the final step. Bank account linking and any payment confirmation that depends on Plaid are the workflows most likely to break.
How StatusBird detected it
StatusBird recorded its first non-operational reading for Plaid at 02:05 UTC, polling the vendor's status endpoint every 2 minutes from its own infrastructure. No incident had been posted on Plaid's own status page when this page was written, so the times here are StatusBird's observations rather than a restatement of the vendor's report.
Method: StatusBird reads Plaid's published status endpoint every 2 minutes and records every reading. Availability figures count major and critical only. The full method is at statusbird.io/methodology.
Lessons for merchants
- Do not rely on a vendor status page alone. It showed nothing here while payments were failing.
- Set up your own alert on checkout completions so a payment outage reaches you within minutes.
- Keep a second payment route you can switch on, so customers can still pay during an outage.
- Write down what you tell customers when checkout fails, and keep failed orders so you can follow up.
The longer version, with the checks specific to this service, is in the Plaid outage playbook.
Frequently asked questions
Was Plaid down on October 26, 2026?
Yes. StatusBird recorded Plaid as major from 02:05 UTC on October 26, 2026. The incident was still running 3 hours 10 minutes later when this page last updated.
How long was Plaid down?
3 hours 10 minutes, measured from the first non-operational reading at 02:05 UTC to the most recent reading, which was still non-operational. Readings are taken every 2 minutes, so the true start and end sit within 2 minutes of those times.
What caused the Plaid outage?
The cause has not yet been published by Plaid. StatusBird measures availability from outside the vendor, which shows when a service stopped responding normally but never why. This section is updated if Plaid publishes a root cause.
How was this Plaid outage detected?
StatusBird recorded its first non-operational reading for Plaid at 02:05 UTC, polling the vendor's status endpoint every 2 minutes from its own infrastructure. No incident had been posted on Plaid's own status page when this page was written, so the times here are StatusBird's observations rather than a restatement of the vendor's report.
Was my store affected?
If your store calls Plaid during checkout or fulfillment, the requests to check are the ones made between 02:05 UTC and now on October 26, 2026. Customers may not be able to complete purchases.
Monitor Plaid with StatusBird
This page exists because StatusBird was already watching. It checks Plaid and the rest of the stack an online store runs on every 2 minutes and sends an SMS, email, Slack, Teams or Discord alert the moment a reading goes non-operational, which on this incident was 02:05 UTC.