User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
plaid.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 457 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:30 | 0 | 0.0 | 1287 ms | 0 |
| 03:45 | 0 | 0.0 | 748 ms | 0 |
| 04:00 | 0 | 0.0 | 499 ms | 0 |
| 04:15 | 0 | 0.0 | 314 ms | 0 |
| 04:30 | 0 | 0.0 | 379 ms | 0 |
| 04:45 | 0 | 0.0 | 1748 ms | 0 |
| 05:00 | 0 | 0.0 | 547 ms | 0 |
| 05:15 | 0 | 0.0 | 608 ms | 0 |
| 05:30 | 0 | 0.0 | 174 ms | 0 |
| 05:45 | 0 | 0.0 | 888 ms | 0 |
| 06:00 | 0 | 0.0 | 528 ms | 0 |
| 06:15 | 0 | 0.0 | 957 ms | 0 |
| 06:30 | 0 | 0.0 | 212 ms | 0 |
| 06:45 | 0 | 0.0 | 328 ms | 0 |
| 07:00 | 0 | 0.0 | 262 ms | 0 |
| 07:15 | 0 | 0.0 | 236 ms | 0 |
| 07:30 | 0 | 0.0 | 1494 ms | 0 |
| 07:45 | 0 | 0.0 | 337 ms | 0 |
| 08:00 | 0 | 0.0 | 455 ms | 0 |
| 08:15 | 0 | 0.0 | 1362 ms | 0 |
| 08:30 | 0 | 0.0 | 923 ms | 0 |
| 08:45 | 0 | 0.0 | 646 ms | 0 |
| 09:00 | 0 | 0.0 | 367 ms | 0 |
| 09:15 | 0 | 0.0 | 409 ms | 0 |
| 09:30 | 0 | 0.0 | 579 ms | 0 |
| 09:45 | 0 | 0.0 | 590 ms | 0 |
| 10:00 | 0 | 0.0 | 345 ms | 0 |
| 10:15 | 0 | 0.0 | 877 ms | 0 |
| 10:30 | 0 | 0.0 | 1254 ms | 0 |
| 10:45 | 0 | 0.0 | 544 ms | 0 |
| 11:00 | 0 | 0.0 | 1708 ms | 0 |
| 11:15 | 0 | 0.0 | 1047 ms | 0 |
| 11:30 | 0 | 0.0 | 312 ms | 0 |
| 11:45 | 0 | 0.0 | 1058 ms | 0 |
| 12:00 | 0 | 0.0 | 1453 ms | 0 |
| 12:15 | 0 | 0.0 | 619 ms | 0 |
| 12:30 | 0 | 0.0 | 667 ms | 0 |
| 12:45 | 0 | 0.0 | 887 ms | 0 |
| 13:00 | 0 | 0.0 | 194 ms | 0 |
| 13:15 | 0 | 0.0 | 656 ms | 0 |
| 13:30 | 0 | 0.0 | 700 ms | 0 |
| 13:45 | 0 | 0.0 | 807 ms | 0 |
| 14:00 | 0 | 0.0 | 623 ms | 0 |
| 14:15 | 0 | 0.0 | 1348 ms | 0 |
| 14:30 | 0 | 0.0 | 245 ms | 0 |
| 14:45 | 0 | 0.0 | 486 ms | 0 |
| 15:00 | 0 | 0.0 | 593 ms | 0 |
| 15:15 | 0 | 0.0 | 457 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Plaid yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Plaid goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Plaid alerts to Slack, Discord or a webhook — free.
Runs on: AWS
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Plaid is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Plaid's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.