Is Web Supplier Sourcing Procurement down?
Up
No, Web Supplier Sourcing Procurement is up.
It passed its latest check 5 h ago in 8.0 s. It has passed every check since 20 Oct 2026, 01:22 UTC.
Latest check
- Last check
- 5 h ago (20 Oct 2026, 20:22 UTC)
- Response time
- 8.0 s (typical 83 ms)
- Next check
- In about 4 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 2 h of failed checks in total, the longest 2 days 3 h.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 17 Oct 2026, 22:40 UTC | 2 days 3 h | 5 | Expected HTTP 402, got 530 |
| 14 Oct 2026, 01:21 UTC | 11 h 52 min | 3 | Expected HTTP 402, got 530 |
| 12 Oct 2026, 23:17 UTC | 11 h 3 min | 3 | 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 |
|---|---|---|---|
| 20 Oct 2026, 20:22 UTC | Passed | 402 | 8.0 s |
| 20 Oct 2026, 11:06 UTC | Passed | 402 | 72 ms |
| 20 Oct 2026, 01:22 UTC | Passed | 402 | 66 ms |
| 18 Oct 2026, 20:06 UTC | Expected HTTP 402, got 530 | 530 | 42 ms |
| 18 Oct 2026, 14:36 UTC | Expected HTTP 402, got 530 | 530 | 44 ms |
| 18 Oct 2026, 08:54 UTC | Expected HTTP 402, got 530 | 530 | 38 ms |
| 18 Oct 2026, 03:45 UTC | Expected HTTP 402, got 530 | 530 | 36 ms |
| 17 Oct 2026, 22:40 UTC | Expected HTTP 402, got 530 | 530 | 37 ms |
| 17 Oct 2026, 17:30 UTC | Passed | 402 | 56 ms |
| 17 Oct 2026, 12:23 UTC | Passed | 402 | 58 ms |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0x8bc2…3C8C
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.