Is BankWeave down?
Down
Yes, BankWeave is down.
It has failed every check since 26 Oct 2026, 03:26 UTC (13 days 2 h, 10 checks). Latest error: Timed out. It last passed on 25 Oct 2026, 15:30 UTC.
Latest check
- Last check
- 3 days ago (5 Nov 2026, 08:19 UTC)
- Response time
- Not measured (typical 263 ms)
- Next check
- In about 71 min
- How often
- About every 31 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 31 hours over the last 7 days.
Outages in the last 30 days
1 outage, 13 days 2 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 26 Oct 2026, 03:26 UTC | Ongoing, 13 days 2 h so far | 10 | initialize returned HTTP 503 |
Times are when our checks ran, about every 31 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 5 Nov 2026, 08:19 UTC | Timed out | - | - |
| 4 Nov 2026, 00:02 UTC | Timed out | - | - |
| 2 Nov 2026, 17:15 UTC | Timed out | - | - |
| 1 Nov 2026, 10:52 UTC | Timed out | - | - |
| 31 Oct 2026, 01:32 UTC | initialize returned HTTP 503 | 503 | 630 ms |
| 29 Oct 2026, 18:23 UTC | initialize returned HTTP 503 | 503 | 247 ms |
| 28 Oct 2026, 12:31 UTC | initialize returned HTTP 503 | 503 | 240 ms |
| 27 Oct 2026, 04:07 UTC | initialize returned HTTP 503 | 503 | 225 ms |
| 26 Oct 2026, 15:31 UTC | initialize returned HTTP 503 | 503 | 390 ms |
| 26 Oct 2026, 03:26 UTC | initialize returned HTTP 503 | 503 | 272 ms |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 31 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.