Is Prior down?
Down
Yes, Prior is down.
It has failed every check since 12 Oct 2026, 12:44 UTC (2 days 16 h, 4 checks). Latest error: Connection failed (ENOTFOUND). It last passed on 12 Oct 2026, 03:50 UTC.
Latest check
- Last check
- 20 h ago (14 Oct 2026, 08:38 UTC)
- Response time
- Not measured (typical 546 ms)
- Next check
- In about 3 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
1 outage, 2 days 16 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 12 Oct 2026, 12:44 UTC | Ongoing, 2 days 16 h so far | 4 | Connection failed (ENOTFOUND) |
Times are when our checks ran, about every 9 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 14 Oct 2026, 08:38 UTC | Connection failed (ENOTFOUND) | - | - |
| 13 Oct 2026, 06:17 UTC | Connection failed (ENOTFOUND) | - | - |
| 12 Oct 2026, 21:22 UTC | Connection failed (ENOTFOUND) | - | - |
| 12 Oct 2026, 12:44 UTC | Connection failed (ENOTFOUND) | - | - |
| 12 Oct 2026, 03:50 UTC | Passed | 401 | 551 ms |
| 11 Oct 2026, 17:50 UTC | Passed | 401 | 546 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.