Is Echo down?
Down
Yes, Echo is down.
It has failed every check since 14 Oct 2026, 02:07 UTC (4 days 16 h, 6 checks). Latest error: initialize returned HTTP 530. It last passed on 13 Oct 2026, 16:49 UTC.
Latest check
- Last check
- 4 h ago (18 Oct 2026, 14:25 UTC)
- Response time
- Not measured (typical 616 ms)
- Next check
- In about 23 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, 4 days 16 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 14 Oct 2026, 02:07 UTC | Ongoing, 4 days 16 h so far | 6 | initialize returned HTTP 530 |
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 |
|---|---|---|---|
| 18 Oct 2026, 14:25 UTC | initialize returned HTTP 530 | 530 | 179 ms |
| 17 Oct 2026, 07:42 UTC | Connection failed (ENOTFOUND) | - | - |
| 16 Oct 2026, 04:08 UTC | initialize returned HTTP 530 | 530 | 176 ms |
| 14 Oct 2026, 21:48 UTC | Timed out | - | - |
| 14 Oct 2026, 12:05 UTC | initialize returned HTTP 502 | 502 | 595 ms |
| 14 Oct 2026, 02:07 UTC | initialize returned HTTP 530 | 530 | 123 ms |
| 13 Oct 2026, 16:49 UTC | Passed | 200 | 818 ms |
| 13 Oct 2026, 07:31 UTC | Passed | 200 | 583 ms |
| 12 Oct 2026, 22:00 UTC | Passed | 200 | 563 ms |
| 12 Oct 2026, 12:32 UTC | Passed | 200 | 622 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.