Is Broadcastwell down?
Possible problem
Broadcastwell may be having problems.
Its latest check failed 21 min ago: initialize returned HTTP 503. The check before passed. Two failed checks in a row count as an outage. Next check: not before 19 Oct 2026, 04:44 UTC.
Latest check
- Last check
- 21 min ago (18 Oct 2026, 23:11 UTC)
- Response time
- Not measured (typical 101 ms)
- Next check
- Not before 19 Oct 2026, 04:44 UTC
- How often
- About every 10 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 10 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 |
|---|---|---|---|
| 18 Oct 2026, 23:11 UTC | initialize returned HTTP 503 | 503 | 48 ms |
| 18 Oct 2026, 13:50 UTC | Passed | 401 | 66 ms |
| 18 Oct 2026, 03:48 UTC | Passed | 401 | 60 ms |
| 17 Oct 2026, 16:47 UTC | Passed | 401 | 80 ms |
| 17 Oct 2026, 05:50 UTC | Passed | 401 | 142 ms |
| 16 Oct 2026, 19:49 UTC | Passed | 401 | 67 ms |
| 16 Oct 2026, 10:03 UTC | Passed | 401 | 129 ms |
| 16 Oct 2026, 00:23 UTC | Passed | 401 | 47 ms |
| 15 Oct 2026, 14:10 UTC | Passed | 401 | 114 ms |
| 15 Oct 2026, 03:54 UTC | Passed | 401 | 61 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 10 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.