Is NetFlow version nibble, bytes discarded down?
Up
No, NetFlow version nibble, bytes discarded is up.
It passed its latest check 9 h ago in 44 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 9 h ago (18 Oct 2026, 08:51 UTC)
- Response time
- 44 ms (typical 62 ms)
- Next check
- In about 79 min
- 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 |
|---|---|---|---|
| 18 Oct 2026, 08:51 UTC | Passed | 200 | 44 ms |
| 17 Oct 2026, 21:34 UTC | Passed | 200 | 66 ms |
| 17 Oct 2026, 11:22 UTC | Passed | 200 | 44 ms |
| 17 Oct 2026, 00:30 UTC | Passed | 200 | 62 ms |
| 16 Oct 2026, 13:51 UTC | Passed | 200 | 211 ms |
| 16 Oct 2026, 03:57 UTC | Passed | 200 | 301 ms |
| 15 Oct 2026, 17:27 UTC | Passed | 200 | 238 ms |
| 15 Oct 2026, 07:23 UTC | Passed | 200 | 357 ms |
| 14 Oct 2026, 21:08 UTC | Passed | 200 | 39 ms |
| 14 Oct 2026, 11:13 UTC | Passed | 200 | 55 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.