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

www.cultos.dev/services/builder-code-validator

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://www.cultos.dev/services/builder-code-validator
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xd494a454888a390b2b05df74ae2b5fd9c9902b71
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-09-13 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)24 / 10

2.Probe history

2026-09-132026-09-26
Figure 1. Probe timeline, last 21 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-26 16:40 UTCPOSTfail400123 msno_402
2026-09-25 22:40 UTCPOSTfail40088 msno_402
2026-09-25 04:40 UTCPOSTfail400162 msno_402
2026-09-24 13:40 UTCPOSTfail400140 msno_402
2026-09-23 22:40 UTCPOSTfail400369 msno_402
2026-09-23 04:40 UTCPOSTfail400236 msno_402
2026-09-22 13:40 UTCPOSTfail400222 msno_402
2026-09-21 16:40 UTCPOSTfail400176 msno_402
2026-09-20 22:40 UTCPOSTfail400155 msno_402
2026-09-20 04:40 UTCPOSTfail400280 msno_402
2026-09-19 13:40 UTCPOSTfail400330 msno_402
2026-09-18 16:40 UTCPOSTfail40055 msno_402
2026-09-18 04:40 UTCPOSTfail400599 msno_402
2026-09-17 13:40 UTCPOSTfail40083 msno_402
2026-09-16 16:40 UTCPOSTfail400236 msno_402
2026-09-15 22:40 UTCPOSTfail400152 msno_402
2026-09-15 04:40 UTCPOSTfail40092 msno_402
2026-09-14 13:40 UTCPOSTfail400296 msno_402
2026-09-13 22:40 UTCPOSTfail400120 msno_402
2026-09-13 11:24 UTCPOSTfail400494 msno_402
2026-09-13 04:40 UTCPOSTfail400139 msno_402

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.