Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-11 · 15 days ago
vet402Back to the registerMethodology

link-preview-cache-api.onrender.com/preview

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://link-preview-cache-api.onrender.com/preview
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x7556a8772e508a8b63f8bbb4f9e6945de0017f4f
Declared price (base units)3000
Catalog statusdelisted (since 2026-09-12 01:03 UTC)
First seen / last seen2026-08-28 01:11 UTC / 2026-09-11 01:03 UTC
Catalog-reported calls / payers (30d)4 / 1

2.Probe history

2026-09-022026-09-11
Figure 1. Probe timeline, last 19 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-09-11 16:40 UTCGETfail503223 msno_402
2026-09-11 04:40 UTCGETfail402140 msprice_mismatch
2026-09-10 17:40 UTCGETfail402144 msprice_mismatch
2026-09-09 23:40 UTCGETfail402367 msprice_mismatch
2026-09-09 14:40 UTCGETfail402251 msprice_mismatch
2026-09-08 23:40 UTCGETfail402339 msprice_mismatch
2026-09-08 14:40 UTCGETfail402496 msprice_mismatch
2026-09-07 23:40 UTCGETfail402672 msprice_mismatch
2026-09-07 05:40 UTCGETfail402462 msprice_mismatch
2026-09-06 17:40 UTCGETfail402459 msprice_mismatch
2026-09-06 05:40 UTCGETfail402200 msprice_mismatch
2026-09-05 17:40 UTCGETfail4022382 msprice_mismatch
2026-09-05 05:40 UTCGETfail4022117 msprice_mismatch
2026-09-04 17:40 UTCGETfail402117 msprice_mismatch
2026-09-04 05:40 UTCGETfail40299 msprice_mismatch
2026-09-03 17:40 UTCGETfail402323 msprice_mismatch
2026-09-03 05:40 UTCGETfail402323 msprice_mismatch
2026-09-02 23:40 UTCGETfail402344 msprice_mismatch
2026-09-02 14:40 UTCGETfail402163 msprice_mismatch

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.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-12delisted{"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

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. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.