Is Gcd Lcm down?
Up
No, Gcd Lcm is up again.
It passed its latest check 4 h ago in 522 ms. Before that it failed our checks for 24 h 52 min, from 25 Oct 2026, 18:36 UTC.
Latest check
- Last check
- 4 h ago (27 Oct 2026, 08:15 UTC)
- Response time
- 522 ms (typical 522 ms)
- Next check
- In about 8 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
3 outages, 3 days 7 h of failed checks in total, the longest 45 h 35 min.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 25 Oct 2026, 18:36 UTC | 24 h 52 min | 2 | Expected HTTP 402, got 530 |
| 22 Oct 2026, 22:23 UTC | 45 h 35 min | 3 | Expected HTTP 402, got 530 |
| 22 Oct 2026, 09:00 UTC | 8 h 33 min | 2 | 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, 08:15 UTC | Passed | 402 | 522 ms |
| 26 Oct 2026, 19:29 UTC | Passed | 402 | 561 ms |
| 26 Oct 2026, 06:34 UTC | Expected HTTP 402, got 530 | 530 | 130 ms |
| 25 Oct 2026, 18:36 UTC | Expected HTTP 402, got 530 | 530 | 688 ms |
| 25 Oct 2026, 07:04 UTC | Passed | 402 | 526 ms |
| 24 Oct 2026, 19:58 UTC | Passed | 402 | 571 ms |
| 23 Oct 2026, 12:52 UTC | Expected HTTP 402, got 530 | 530 | 132 ms |
| 23 Oct 2026, 03:01 UTC | Expected HTTP 402, got 530 | 530 | 79 ms |
| 22 Oct 2026, 22:23 UTC | Expected HTTP 402, got 530 | 530 | 97 ms |
| 22 Oct 2026, 17:33 UTC | Passed | 402 | 496 ms |
Price and payment address
- Price
- $0.02 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.