Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
→ 0 more columns
L0 probe history, newest first
Probed at
Method
Verdict
HTTP
Latency
Reason
2026-09-05 11:24 UTC
GET
pass
402
32 ms
—
2026-08-14 08:53 UTC
GET
pass
402
38 ms
—
3.L1 — real purchases
0 of 1 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
0/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
→ 0 more columns
L1 purchase history, newest first
Attempted at
Result
HTTP
Receipt (tx)
Latency
08-14 10:092026-08-14 10:09 UTC
settle_failed
400
—
170 ms
250000 units (≈ $0.25 USDC) · L2 not_checked
4.Catalog listing events
→ 0 more columns
Catalog listing events, newest first
Detected on
Event
Before
After
2026-09-02
relisted
{"status":"delisted"}
{"status":"active"}
2026-09-01
delisted
{"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.