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

www.cultos.dev/services/relics/open

1.Catalog declaration

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

2.Probe history

2026-09-102026-09-26
Figure 1. Probe timeline, last 26 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 UTCPOSTfail4001787 msno_402
2026-09-25 22:40 UTCPOSTfail400319 msno_402
2026-09-25 04:40 UTCPOSTfail400240 msno_402
2026-09-24 13:40 UTCPOSTfail400167 msno_402
2026-09-23 16:40 UTCPOSTfail400140 msno_402
2026-09-22 22:40 UTCPOSTfail400240 msno_402
2026-09-22 13:40 UTCPOSTfail400315 msno_402
2026-09-21 16:40 UTCPOSTfail400174 msno_402
2026-09-20 22:40 UTCPOSTfail400194 msno_402
2026-09-20 04:40 UTCPOSTfail400229 msno_402
2026-09-19 13:40 UTCPOSTfail40082 msno_402
2026-09-18 16:40 UTCPOSTfail40060 msno_402
2026-09-17 22:40 UTCPOSTfail400170 msno_402
2026-09-17 13:40 UTCPOSTfail40098 msno_402
2026-09-16 16:40 UTCPOSTfail400371 msno_402
2026-09-15 16:40 UTCPOSTfail40068 msno_402
2026-09-15 04:40 UTCPOSTfail400265 msno_402
2026-09-14 13:40 UTCPOSTfail400366 msno_402
2026-09-13 22:40 UTCPOSTfail400387 msno_402
2026-09-13 04:40 UTCPOSTfail400197 msno_402
2026-09-12 16:40 UTCPOSTfail400142 msno_402
2026-09-12 04:40 UTCPOSTfail400237 msno_402
2026-09-11 13:40 UTCPOSTfail400120 msno_402
2026-09-10 23:40 UTCPOSTfail4003431 msno_402
2026-09-10 11:24 UTCPOSTfail400388 msno_402
2026-09-10 05:40 UTCPOSTfail400270 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.