Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · 1 day ago
multichain-rpc.clankerceo.workers.dev/gas-price
1.Catalog declaration
| Resource URL | https://multichain-rpc.clankerceo.workers.dev/gas-price |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0xca03fb4b1d2f66f5a83a5ca91021b874ac4a34a3 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-09-01 01:03 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-09-052026-10-20
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 13:40 UTC | GET | pass | 402 | 197 ms | — |
| 2026-10-18 22:40 UTC | GET | pass | 402 | 26 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 53 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-10-13 10:30 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-27 10:31 UTC | GET | pass | 402 | 51 ms | — |
| 2026-09-23 10:30 UTC | GET | pass | 402 | 13 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 11 ms | — |
| 2026-09-17 11:24 UTC | GET | pass | 402 | 53 ms | — |
| 2026-09-13 11:24 UTC | GET | pass | 402 | 40 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 12 ms | — |
| 2026-09-05 11:24 UTC | GET | pass | 402 | 55 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-11 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-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.