Is who.is down?
Up
No, who.is is up.
It passed its latest check 11 h ago in 512 ms, and every check since we started checking it on 23 Oct 2026.
Latest check
- Last check
- 11 h ago (7 Nov 2026, 02:38 UTC)
- Response time
- 512 ms (typical 527 ms)
- Next check
- In about 3 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 |
|---|---|---|---|
| 7 Nov 2026, 02:38 UTC | Passed | 401 | 512 ms |
| 6 Nov 2026, 16:17 UTC | Passed | 401 | 548 ms |
| 6 Nov 2026, 04:51 UTC | Passed | 401 | 510 ms |
| 5 Nov 2026, 13:41 UTC | Passed | 401 | 504 ms |
| 4 Nov 2026, 22:55 UTC | Passed | 401 | 565 ms |
| 4 Nov 2026, 08:09 UTC | Passed | 401 | 549 ms |
| 3 Nov 2026, 17:14 UTC | Passed | 401 | 453 ms |
| 3 Nov 2026, 02:22 UTC | Passed | 401 | 493 ms |
| 2 Nov 2026, 12:15 UTC | Passed | 401 | 476 ms |
| 2 Nov 2026, 01:11 UTC | Passed | 401 | 547 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.