Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-26 · today
regionfetch.dev/api/fetch
1.Catalog declaration
| Resource URL | https://regionfetch.dev/api/fetch |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x97ac53d3bc5ae0a29fd2a40233533374589365be |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-09-02 01:03 UTC / 2026-09-27 01:02 UTC |
| Catalog-reported calls / payers (30d) | 4 / 2 |
2.Probe history
2026-09-072026-09-26
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 16:40 UTC | POST | fail | 400 | 296 ms | no_402 |
| 2026-09-26 04:40 UTC | POST | fail | 400 | 308 ms | no_402 |
| 2026-09-25 13:40 UTC | POST | fail | 400 | 396 ms | no_402 |
| 2026-09-24 16:40 UTC | POST | fail | 400 | 352 ms | no_402 |
| 2026-09-23 22:40 UTC | POST | fail | 400 | 229 ms | no_402 |
| 2026-09-23 04:40 UTC | POST | fail | 400 | 2094 ms | no_402 |
| 2026-09-22 13:40 UTC | POST | fail | 400 | 208 ms | no_402 |
| 2026-09-21 16:40 UTC | POST | fail | 400 | 332 ms | no_402 |
| 2026-09-20 22:40 UTC | POST | fail | 400 | 250 ms | no_402 |
| 2026-09-20 04:40 UTC | POST | fail | 400 | 360 ms | no_402 |
| 2026-09-19 13:40 UTC | POST | fail | 400 | 184 ms | no_402 |
| 2026-09-18 16:40 UTC | POST | fail | 400 | 230 ms | no_402 |
| 2026-09-18 04:40 UTC | POST | fail | 400 | 292 ms | no_402 |
| 2026-09-17 13:40 UTC | POST | fail | 400 | 179 ms | no_402 |
| 2026-09-16 16:40 UTC | POST | fail | 400 | 278 ms | no_402 |
| 2026-09-15 22:40 UTC | POST | fail | 400 | 2407 ms | no_402 |
| 2026-09-15 04:40 UTC | POST | fail | 400 | 209 ms | no_402 |
| 2026-09-14 16:40 UTC | POST | fail | 400 | 755 ms | no_402 |
| 2026-09-13 22:40 UTC | POST | fail | 400 | 2491 ms | no_402 |
| 2026-09-13 13:40 UTC | POST | fail | 400 | 188 ms | no_402 |
| 2026-09-12 16:40 UTC | POST | fail | 400 | 332 ms | no_402 |
| 2026-09-12 04:40 UTC | POST | fail | 400 | 434 ms | no_402 |
| 2026-09-11 13:40 UTC | POST | fail | 400 | 271 ms | no_402 |
| 2026-09-10 23:40 UTC | POST | fail | 400 | 238 ms | no_402 |
| 2026-09-10 14:40 UTC | POST | fail | 400 | 223 ms | no_402 |
| 2026-09-09 17:40 UTC | POST | fail | 400 | 242 ms | no_402 |
| 2026-09-09 05:40 UTC | POST | fail | 400 | 222 ms | no_402 |
| 2026-09-08 17:40 UTC | POST | fail | 400 | 2084 ms | no_402 |
| 2026-09-08 05:40 UTC | POST | fail | 400 | 219 ms | no_402 |
| 2026-09-07 17:40 UTC | POST | fail | 400 | 185 ms | no_402 |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
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.