Is Module Trending down?
Down
Yes, Module Trending is down.
It has failed every check since 14 Oct 2026, 01:22 UTC (4 days 10 h, 10 checks). Latest error: Expected HTTP 402, got 530. It last passed on 13 Oct 2026, 16:31 UTC.
Latest check
- Last check
- 44 h ago (16 Oct 2026, 15:43 UTC)
- Response time
- Not measured (typical 302 ms)
- Next check
- In about 24 h
- How often
- About every 5 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 5 hours over the last 7 days.
Outages in the last 30 days
1 outage, 4 days 10 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 14 Oct 2026, 01:22 UTC | Ongoing, 4 days 10 h so far | 10 | Expected HTTP 402, got 530 |
Times are when our checks ran, about every 5 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 16 Oct 2026, 15:43 UTC | Expected HTTP 402, got 530 | 530 | 210 ms |
| 15 Oct 2026, 13:00 UTC | Expected HTTP 402, got 530 | 530 | 203 ms |
| 15 Oct 2026, 08:09 UTC | Expected HTTP 402, got 530 | 530 | 180 ms |
| 15 Oct 2026, 03:21 UTC | Expected HTTP 402, got 530 | 530 | 161 ms |
| 14 Oct 2026, 22:37 UTC | Expected HTTP 402, got 530 | 530 | 128 ms |
| 14 Oct 2026, 17:55 UTC | Expected HTTP 402, got 530 | 530 | 154 ms |
| 14 Oct 2026, 13:20 UTC | Expected HTTP 402, got 530 | 530 | 223 ms |
| 14 Oct 2026, 08:49 UTC | Expected HTTP 402, got 530 | 530 | 166 ms |
| 14 Oct 2026, 05:06 UTC | Expected HTTP 402, got 530 | 530 | 124 ms |
| 14 Oct 2026, 01:22 UTC | Expected HTTP 402, got 530 | 530 | 135 ms |
Price and payment address
- Price
- $0.001 per call on Base
- Pays to
- 0x8E00…6841
No price or payment address changes recorded.
How we check
Up means the endpoint answered an unpaid test request with a valid x402 payment challenge. We never pay, so we can't see whether the paid response works.
Checks come from our server, about every 5 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. To see what an agent gets right now, check it yourself.