Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-10-07 · 18 days ago

402utils.com/v1/rerank

Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://402utils.com/v1/rerank
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0xc55a2d530b53cbad1001e4afd4720b7e71f9c291
Declared price (base units)4000
Catalog statusdelisted (since 2026-10-08 13:03 UTC)
First seen / last seen2026-08-14 08:52 UTC / 2026-10-08 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-272026-10-07
Figure 1. Probe timeline, last 13 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-07 13:40 UTCPOSTfail—222 msdnsThe host name did not resolve.
2026-10-06 13:40 UTCPOSTfail—10001 mstimeoutNo response headers arrived within 10 seconds.
2026-10-04 22:40 UTCPOSTpass4021591 ms—
2026-10-04 04:40 UTCPOSTpass4021167 ms—
2026-10-03 13:40 UTCPOSTpass4027363 ms—
2026-09-28 10:30 UTCPOSTfail—10000 mstimeoutNo response headers arrived within 10 seconds.
2026-09-23 10:30 UTCPOSTpass4021541 ms—
2026-09-19 11:24 UTCPOSTpass40236 ms—
2026-09-17 11:24 UTCPOSTpass4028457 ms—
2026-09-11 11:24 UTCPOSTpass40213 ms—
2026-09-08 11:24 UTCPOSTpass4021572 ms—
2026-09-03 11:24 UTCPOSTpass4021521 ms—
2026-08-27 10:33 UTCPOSTfail4021354 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-08delisted{"status":"active"}{"status":"delisted"}
2026-09-17relisted{"status":"delisted"}{"status":"active"}
2026-09-13delisted{"status":"active"}{"status":"delisted"}

unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.

5.Dispute this record

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight. If it was right, it stands. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far