Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago
netintel.dev/web/fetch
1.Catalog declaration
| Resource URL | https://netintel.dev/web/fetch |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xdadc335482ad545296fd7b28518a251ffcbeb9df |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-30 01:02 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
2026-09-042026-10-19
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 286 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 277 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 2166 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 284 ms | — |
| 2026-10-04 10:30 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-27 10:30 UTC | GET | pass | 402 | 222 ms | — |
| 2026-09-22 11:25 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 131 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 161 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 174 ms | — |
| 2026-09-04 11:24 UTC | GET | pass | 402 | 156 ms | — |
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.