Is gitignore rule count, body discarded down?
Up
No, gitignore rule count, body discarded is up.
It passed its latest check 3 h ago in 277 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 3 h ago (17 Oct 2026, 22:45 UTC)
- Response time
- 277 ms (typical 47 ms)
- Next check
- In about 7 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 |
|---|---|---|---|
| 17 Oct 2026, 22:45 UTC | Passed | 200 | 277 ms |
| 17 Oct 2026, 12:18 UTC | Passed | 200 | 60 ms |
| 17 Oct 2026, 01:57 UTC | Passed | 200 | 112 ms |
| 16 Oct 2026, 15:04 UTC | Passed | 200 | 57 ms |
| 16 Oct 2026, 04:45 UTC | Passed | 200 | 35 ms |
| 15 Oct 2026, 18:54 UTC | Passed | 200 | 51 ms |
| 15 Oct 2026, 09:28 UTC | Passed | 200 | 63 ms |
| 14 Oct 2026, 23:13 UTC | Passed | 200 | 288 ms |
| 14 Oct 2026, 13:43 UTC | Passed | 200 | 47 ms |
| 14 Oct 2026, 04:01 UTC | Passed | 200 | 40 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 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.