Is R3 down?
Up
No, R3 is up.
It passed its latest check 9 h ago in 241 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 9 h ago (18 Oct 2026, 11:52 UTC)
- Response time
- 241 ms (typical 237 ms)
- Next check
- In about 76 min
- How often
- About every 10 hours over the last 7 days
Uptime
Last 24 hours100%2 checks
Last 7 days100%16 checks
Last 30 days100%17 checks
All checks passedSome failedAll failedNot checked
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, 11:52 UTC | Passed | 200 | 241 ms |
| 18 Oct 2026, 01:36 UTC | Passed | 200 | 241 ms |
| 17 Oct 2026, 14:21 UTC | Passed | 200 | 180 ms |
| 17 Oct 2026, 03:42 UTC | Passed | 200 | 222 ms |
| 16 Oct 2026, 17:20 UTC | Passed | 200 | 523 ms |
| 16 Oct 2026, 06:36 UTC | Passed | 200 | 422 ms |
| 15 Oct 2026, 20:50 UTC | Passed | 200 | 415 ms |
| 15 Oct 2026, 10:54 UTC | Passed | 200 | 234 ms |
| 15 Oct 2026, 01:21 UTC | Passed | 401 | 259 ms |
| 14 Oct 2026, 15:09 UTC | Passed | 401 | 201 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.