Is AskScores down?
Possible problem
AskScores may be having problems.
Its latest check failed 2 h ago: initialize returned HTTP 429. The check before passed. Two failed checks in a row count as an outage. Next check: in about 7 h.
Latest check
- Last check
- 2 h ago (15 Oct 2026, 04:22 UTC)
- Response time
- Not measured (typical 243 ms)
- Next check
- In about 7 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
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 |
|---|---|---|---|
| 15 Oct 2026, 04:22 UTC | initialize returned HTTP 429 | 429 | 197 ms |
| 14 Oct 2026, 18:42 UTC | Passed | 200 | 234 ms |
| 14 Oct 2026, 09:25 UTC | Passed | 200 | 282 ms |
| 14 Oct 2026, 00:26 UTC | Passed | 200 | 134 ms |
| 13 Oct 2026, 15:05 UTC | Passed | 200 | 243 ms |
| 13 Oct 2026, 05:50 UTC | Passed | 200 | 174 ms |
| 12 Oct 2026, 21:14 UTC | Passed | 200 | 183 ms |
| 12 Oct 2026, 12:12 UTC | Passed | 200 | 305 ms |
| 12 Oct 2026, 02:26 UTC | Passed | 200 | 266 ms |
| 11 Oct 2026, 17:15 UTC | Passed | 200 | 326 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.