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

lauf.halowerk.com/v1/browser-task

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://lauf.halowerk.com/v1/browser-task
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x2880edfff13100677bf97a3cbdf3bc34771c4e5e
Declared price (base units)16000
Catalog statusdelisted (since 2026-09-11 01:03 UTC)
First seen / last seen2026-08-14 08:52 UTC / 2026-09-10 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-312026-09-10
Figure 1. Probe timeline, last 18 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-10 17:40 UTCPOSTfail400201 msno_402
2026-09-10 05:40 UTCPOSTfail400641 msno_402
2026-09-09 17:40 UTCPOSTfail400332 msno_402
2026-09-09 05:40 UTCPOSTfail400369 msno_402
2026-09-08 14:40 UTCPOSTfail400584 msno_402
2026-09-07 23:40 UTCPOSTfail400513 msno_402
2026-09-07 14:40 UTCPOSTfail400492 msno_402
2026-09-06 23:40 UTCPOSTfail402501 msprice_mismatch
2026-09-06 14:40 UTCPOSTfail402317 msprice_mismatch
2026-09-05 23:40 UTCPOSTfail402513 msprice_mismatch
2026-09-05 14:40 UTCPOSTfail4022238 msprice_mismatch
2026-09-04 23:40 UTCPOSTfail402444 msprice_mismatch
2026-09-04 14:40 UTCPOSTfail402837 msprice_mismatch
2026-09-03 23:40 UTCPOSTfail402438 msprice_mismatch
2026-09-03 14:40 UTCPOSTfail402517 msprice_mismatch
2026-09-02 23:40 UTCPOSTfail402466 msprice_mismatch
2026-09-02 14:40 UTCPOSTfail402529 msprice_mismatch
2026-08-31 11:24 UTCPOSTfail402109 msaccepts_invalid

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-11delisted{"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.

lauf.halowerk.com/v1/browser-task — L0 observations | vet402