Is Royally down?
Up
No, Royally is up.
It passed its latest check 2 h ago in 667 ms, and every check since we started checking it on 1 Nov 2026.
Latest check
- Last check
- 2 h ago (7 Nov 2026, 17:27 UTC)
- Response time
- 667 ms (typical 503 ms)
- Next check
- In about 11 h
- How often
- About every 13 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 13 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 |
|---|---|---|---|
| 7 Nov 2026, 17:27 UTC | Passed | 401 | 667 ms |
| 7 Nov 2026, 05:28 UTC | Passed | 401 | 530 ms |
| 6 Nov 2026, 18:05 UTC | Passed | 401 | 434 ms |
| 6 Nov 2026, 07:03 UTC | Passed | 401 | 543 ms |
| 5 Nov 2026, 16:56 UTC | Passed | 401 | 491 ms |
| 5 Nov 2026, 02:18 UTC | Passed | 401 | 503 ms |
| 4 Nov 2026, 11:03 UTC | Passed | 401 | 471 ms |
| 3 Nov 2026, 20:18 UTC | Passed | 401 | 465 ms |
| 3 Nov 2026, 05:26 UTC | Passed | 401 | 596 ms |
| 2 Nov 2026, 15:21 UTC | Passed | 401 | 608 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 13 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.