Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-01 · 5 days ago
api.locus.report/api/locus-flood-zone
1.Catalog declaration
| Resource URL | https://api.locus.report/api/locus-flood-zone |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xf121fbecec43e1b616d47285851c20d5fc64431b |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-06 07:55 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
2026-08-192026-10-01
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 10:31 UTC | POST | fail | 200 | 1536 ms | no_402HTTP 200 instead of 402 to an unpaid POST. |
| 2026-09-26 10:30 UTC | POST | fail | 200 | 1156 ms | no_402HTTP 200 instead of 402 to an unpaid POST. |
| 2026-09-22 11:24 UTC | POST | fail | 200 | 150 ms | no_402HTTP 200 instead of 402 to an unpaid POST. |
| 2026-09-17 16:19 UTC | POST | fail | 200 | 2244 ms | no_402HTTP 200 instead of 402 to an unpaid POST. |
| 2026-09-15 11:24 UTC | POST | fail | 200 | 1604 ms | no_402HTTP 200 instead of 402 to an unpaid POST. |
| 2026-09-11 11:24 UTC | POST | fail | 200 | 38 ms | no_402HTTP 200 instead of 402 to an unpaid POST. |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 1106 ms | — |
| 2026-09-02 11:25 UTC | POST | pass | 402 | 1134 ms | — |
| 2026-08-19 10:56 UTC | POST | fail | 402 | 98 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
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.