Is Hash Encoding Direct Credits down?
Down
Yes, Hash Encoding Direct Credits is down.
It has failed every check since 13 Oct 2026, 23:24 UTC (4 days 4 h, 5 checks). Latest error: initialize returned HTTP 404. It last passed on 13 Oct 2026, 13:51 UTC.
Latest check
- Last check
- 25 h ago (17 Oct 2026, 02:22 UTC)
- Response time
- Not measured (typical 258 ms)
- Next check
- In about 37 min
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 hours over the last 7 days.
Outages in the last 30 days
1 outage, 4 days 4 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 13 Oct 2026, 23:24 UTC | Ongoing, 4 days 4 h so far | 5 | initialize returned HTTP 404 |
Times are when our checks ran, about every 9 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 17 Oct 2026, 02:22 UTC | initialize returned HTTP 404 | 404 | 236 ms |
| 15 Oct 2026, 23:04 UTC | initialize returned HTTP 404 | 404 | 140 ms |
| 14 Oct 2026, 18:49 UTC | initialize returned HTTP 404 | 404 | 139 ms |
| 14 Oct 2026, 08:40 UTC | initialize returned HTTP 404 | 404 | 141 ms |
| 13 Oct 2026, 23:24 UTC | initialize returned HTTP 404 | 404 | 116 ms |
| 13 Oct 2026, 13:51 UTC | Passed | 200 | 240 ms |
| 13 Oct 2026, 04:44 UTC | Passed | 200 | 213 ms |
| 12 Oct 2026, 20:11 UTC | Passed | 200 | 258 ms |
| 12 Oct 2026, 11:14 UTC | Passed | 200 | 258 ms |
| 12 Oct 2026, 02:05 UTC | Passed | 200 | 400 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 9 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.