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

milan-wells-linux-puts.trycloudflare.com/api/stats

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://milan-wells-linux-puts.trycloudflare.com/api/stats
Sourcecdp_bazaar
Declared methodGET
Networkbase
Receiving address0x16706c173e945a1949695a2517b32f635e50fd4d
Declared price (base units)—
Catalog statusactive
First seen / last seen2026-09-17 01:03 UTC / 2026-09-17 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-172026-09-24
Figure 1. Probe timeline, last 4 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-24 10:30 UTCGETfail—13 msdns
2026-09-20 11:24 UTCGETfail—18 msdns
2026-09-17 12:35 UTCGETfail—384 msdns
2026-09-17 11:24 UTCGETfail—11 msdns

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

No listing changes observed.

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.