Is NextConstraint down?
Up
No, NextConstraint is up.
It passed its latest check 1 h ago in 1.3 s, and every check since we started checking it on 6 Nov 2026.
Latest check
- Last check
- 1 h ago (10 Nov 2026, 11:19 UTC)
- Response time
- 1.3 s (typical 2.4 s)
- Next check
- In about 10 h
- How often
- About every 11 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 11 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 |
|---|---|---|---|
| 10 Nov 2026, 11:19 UTC | Passed | 200 | 1.3 s |
| 9 Nov 2026, 23:28 UTC | Passed | 200 | 2.9 s |
| 9 Nov 2026, 12:10 UTC | Passed | 200 | 2.7 s |
| 9 Nov 2026, 01:35 UTC | Passed | 200 | 2.4 s |
| 8 Nov 2026, 13:17 UTC | Passed | 200 | 2.2 s |
| 8 Nov 2026, 01:47 UTC | Passed | 200 | 2.7 s |
| 7 Nov 2026, 15:04 UTC | Passed | 200 | 2.4 s |
| 7 Nov 2026, 02:34 UTC | Passed | 401 | 215 ms |
| 6 Nov 2026, 16:28 UTC | Passed | 401 | 1.2 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 11 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.