Is Browser Forest down?
Up
No, Browser Forest is up.
It passed its latest check 4 h ago in 1.1 s, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 4 h ago (14 Oct 2026, 18:02 UTC)
- Response time
- 1.1 s (typical 391 ms)
- Next check
- In about 5 h
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 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 |
|---|---|---|---|
| 14 Oct 2026, 18:02 UTC | Passed | 401 | 1.1 s |
| 14 Oct 2026, 08:15 UTC | Passed | 401 | 317 ms |
| 13 Oct 2026, 23:04 UTC | Passed | 401 | 385 ms |
| 13 Oct 2026, 13:19 UTC | Passed | 401 | 737 ms |
| 13 Oct 2026, 04:32 UTC | Passed | 401 | 269 ms |
| 12 Oct 2026, 19:27 UTC | Passed | 401 | 391 ms |
| 12 Oct 2026, 10:04 UTC | Passed | 401 | 403 ms |
| 12 Oct 2026, 01:57 UTC | Passed | 401 | 384 ms |
| 11 Oct 2026, 17:16 UTC | Passed | 401 | 483 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 9 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.