Is BuildPulse down?
Up
No, BuildPulse is up.
It passed its latest check 5 h ago in 843 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 5 h ago (4 Nov 2026, 23:24 UTC)
- Response time
- 843 ms (typical 851 ms)
- Next check
- In about 8 h
- How often
- About every 14 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 14 hours over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 4 Nov 2026, 23:24 UTC | Passed | 401 | 843 ms |
| 4 Nov 2026, 08:26 UTC | Passed | 401 | 939 ms |
| 3 Nov 2026, 17:21 UTC | Passed | 401 | 813 ms |
| 3 Nov 2026, 03:25 UTC | Passed | 401 | 881 ms |
| 2 Nov 2026, 12:57 UTC | Passed | 401 | 866 ms |
| 2 Nov 2026, 01:31 UTC | Passed | 401 | 885 ms |
| 1 Nov 2026, 15:36 UTC | Passed | 401 | 854 ms |
| 1 Nov 2026, 04:15 UTC | Passed | 401 | 827 ms |
| 31 Oct 2026, 14:34 UTC | Passed | 401 | 821 ms |
| 31 Oct 2026, 00:38 UTC | Passed | 401 | 915 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 14 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.