Is Retry-outcome resolution dedup proxy down?
Up
No, Retry-outcome resolution dedup proxy is up.
It passed its latest check 4 h ago in 341 ms. It has passed every check since 2 Nov 2026, 16:55 UTC.
Latest check
- Last check
- 4 h ago (7 Nov 2026, 07:08 UTC)
- Response time
- 341 ms (typical 345 ms)
- Next check
- In about 10 h
- How often
- About every 14 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 14 hours over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 7 Nov 2026, 07:08 UTC | Passed | 200 | 341 ms |
| 6 Nov 2026, 19:21 UTC | Passed | 200 | 351 ms |
| 6 Nov 2026, 08:58 UTC | Passed | 200 | 470 ms |
| 5 Nov 2026, 19:16 UTC | Passed | 200 | 380 ms |
| 5 Nov 2026, 03:48 UTC | Passed | 200 | 359 ms |
| 4 Nov 2026, 12:53 UTC | Passed | 200 | 364 ms |
| 3 Nov 2026, 21:37 UTC | Passed | 200 | 346 ms |
| 3 Nov 2026, 07:41 UTC | Passed | 200 | 334 ms |
| 2 Nov 2026, 16:55 UTC | Passed | 200 | 333 ms |
| 2 Nov 2026, 03:23 UTC | initialize returned HTTP 502 | 502 | 371 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 14 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.