Is NoCodeCSV down?
Up
No, NoCodeCSV is up.
It passed its latest check 4 h ago in 1.5 s, and every check since we started checking it on 15 Oct 2026.
Latest check
- Last check
- 4 h ago (4 Nov 2026, 20:57 UTC)
- Response time
- 1.5 s (typical 363 ms)
- Next check
- In about 10 h
- How often
- About every 14 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 14 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 |
|---|---|---|---|
| 4 Nov 2026, 20:57 UTC | Passed | 200 | 1.5 s |
| 4 Nov 2026, 05:41 UTC | Passed | 200 | 1.3 s |
| 3 Nov 2026, 15:24 UTC | Passed | 200 | 1.6 s |
| 3 Nov 2026, 01:26 UTC | Passed | 200 | 687 ms |
| 2 Nov 2026, 10:46 UTC | Passed | 200 | 1.2 s |
| 1 Nov 2026, 23:40 UTC | Passed | 200 | 338 ms |
| 1 Nov 2026, 14:15 UTC | Passed | 200 | 485 ms |
| 1 Nov 2026, 01:52 UTC | Passed | 200 | 663 ms |
| 31 Oct 2026, 11:44 UTC | Passed | 200 | 1.2 s |
| 30 Oct 2026, 21:39 UTC | Passed | 200 | 319 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 14 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.