Is Verified Numbers down?
Down
Yes, Verified Numbers is down.
It has failed every check since 12 Oct 2026, 23:18 UTC (2 days 14 h, 4 checks). Latest error: initialize returned HTTP 500. It last passed on 12 Oct 2026, 13:43 UTC.
Latest check
- Last check
- 16 h ago (14 Oct 2026, 21:38 UTC)
- Response time
- Not measured (typical 587 ms)
- Next check
- In about 10 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
1 outage, 2 days 14 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 12 Oct 2026, 23:18 UTC | Ongoing, 2 days 14 h so far | 4 | initialize returned HTTP 500 |
Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 14 Oct 2026, 21:38 UTC | initialize returned HTTP 500 | 500 | 555 ms |
| 13 Oct 2026, 17:44 UTC | initialize returned HTTP 500 | 500 | 757 ms |
| 13 Oct 2026, 08:23 UTC | initialize returned HTTP 500 | 500 | 551 ms |
| 12 Oct 2026, 23:18 UTC | initialize returned HTTP 500 | 500 | 637 ms |
| 12 Oct 2026, 13:43 UTC | Passed | 401 | 587 ms |
| 12 Oct 2026, 03:51 UTC | Passed | 401 | 649 ms |
| 11 Oct 2026, 18:17 UTC | Passed | 401 | 559 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.