Is Active Storms down?
Up
No, Active Storms is up again.
It passed its latest check 4 h ago in 552 ms. Before that it failed our checks for 24 h 8 min, from 25 Oct 2026, 18:47 UTC.
Latest check
- Last check
- 4 h ago (27 Oct 2026, 07:49 UTC)
- Response time
- 552 ms (typical 525 ms)
- Next check
- In about 9 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
2 outages, 3 days 21 h of failed checks in total, the longest 2 days 21 h.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 25 Oct 2026, 18:47 UTC | 24 h 8 min | 2 | Expected HTTP 402, got 530 |
| 22 Oct 2026, 09:55 UTC | 2 days 21 h | 5 | 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 |
|---|---|---|---|
| 27 Oct 2026, 07:49 UTC | Passed | 402 | 552 ms |
| 26 Oct 2026, 18:55 UTC | Passed | 402 | 568 ms |
| 26 Oct 2026, 06:41 UTC | Expected HTTP 402, got 530 | 530 | 144 ms |
| 25 Oct 2026, 18:47 UTC | Expected HTTP 402, got 530 | 530 | 106 ms |
| 25 Oct 2026, 07:13 UTC | Passed | 402 | 530 ms |
| 24 Oct 2026, 03:58 UTC | Expected HTTP 402, got 530 | 530 | 125 ms |
| 22 Oct 2026, 23:49 UTC | Expected HTTP 402, got 530 | 530 | 135 ms |
| 22 Oct 2026, 18:31 UTC | Expected HTTP 402, got 530 | 530 | 99 ms |
| 22 Oct 2026, 14:07 UTC | Expected HTTP 402, got 530 | 530 | 237 ms |
| 22 Oct 2026, 09:55 UTC | Expected HTTP 402, got 530 | 530 | 149 ms |
Price and payment address
- Price
- $0.03 per call on Polygon
- Pays to
- 0xb531…DBDa
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.