Is Pyrimid Protocol down?
Up
No, Pyrimid Protocol is up.
It passed its latest check 8 h ago in 107 ms. It has passed every check since 14 Oct 2026, 14:52 UTC.
Latest check
- Last check
- 8 h ago (19 Oct 2026, 04:27 UTC)
- Response time
- 107 ms (typical 125 ms)
- Next check
- In about 2 h
- 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 |
|---|---|---|---|
| 19 Oct 2026, 04:27 UTC | Passed | 402 | 107 ms |
| 18 Oct 2026, 19:31 UTC | Passed | 402 | 49 ms |
| 18 Oct 2026, 08:59 UTC | Passed | 402 | 152 ms |
| 17 Oct 2026, 22:28 UTC | Passed | 402 | 118 ms |
| 17 Oct 2026, 11:56 UTC | Passed | 402 | 109 ms |
| 17 Oct 2026, 01:52 UTC | Passed | 402 | 127 ms |
| 16 Oct 2026, 15:51 UTC | Passed | 402 | 130 ms |
| 16 Oct 2026, 05:51 UTC | Passed | 402 | 85 ms |
| 15 Oct 2026, 19:41 UTC | Passed | 402 | 125 ms |
| 15 Oct 2026, 10:20 UTC | Passed | 402 | 1.3 s |
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.