Is AgentWorld Discovery down?
Possible problem
AgentWorld Discovery may be having problems.
Its latest check failed 48 min ago: initialize returned HTTP 530. The check before passed. Two failed checks in a row count as an outage. Next check: not before 18 Oct 2026, 14:18 UTC.
Latest check
- Last check
- 48 min ago (18 Oct 2026, 07:44 UTC)
- Response time
- Not measured (typical 276 ms)
- Next check
- Not before 18 Oct 2026, 14:18 UTC
- 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, 07:44 UTC | initialize returned HTTP 530 | 530 | 238 ms |
| 17 Oct 2026, 21:00 UTC | Passed | 200 | 237 ms |
| 17 Oct 2026, 10:54 UTC | Passed | 200 | 231 ms |
| 16 Oct 2026, 23:49 UTC | Passed | 200 | 221 ms |
| 16 Oct 2026, 13:44 UTC | Passed | 200 | 789 ms |
| 16 Oct 2026, 03:59 UTC | Passed | 200 | 293 ms |
| 15 Oct 2026, 17:59 UTC | Passed | 200 | 466 ms |
| 15 Oct 2026, 08:09 UTC | Passed | 200 | 285 ms |
| 14 Oct 2026, 21:56 UTC | Passed | 200 | 225 ms |
| 14 Oct 2026, 11:42 UTC | Passed | 200 | 282 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.