Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-10 · today
api.hyperd.ai/api/privacy/mixer-risk
1.Catalog declaration
| Resource URL | https://api.hyperd.ai/api/privacy/mixer-risk |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x61b51131e1e44552de2f151ca59dac707d9cf1c6 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-10 01:02 UTC |
| Catalog-reported calls / payers (30d) | 3 / 1 |
2.Probe history
2026-09-162026-10-10
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-10 03:40 UTC | GET | fail | 400 | 366 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-08 22:40 UTC | GET | fail | 400 | 459 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-07 22:40 UTC | GET | fail | 400 | 159 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-06 22:40 UTC | GET | fail | 400 | 169 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-06 04:41 UTC | GET | fail | 400 | 398 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-04 16:40 UTC | GET | fail | 400 | 230 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-03 22:40 UTC | GET | fail | 400 | 229 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-03 04:40 UTC | GET | fail | 400 | 297 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-02 04:40 UTC | GET | fail | 400 | 783 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-10-01 13:40 UTC | GET | fail | 400 | 80 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-30 16:40 UTC | GET | fail | 400 | 388 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-29 22:40 UTC | GET | fail | 400 | 206 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-29 04:40 UTC | GET | fail | 400 | 213 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-28 13:40 UTC | GET | fail | 400 | 356 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-27 16:40 UTC | GET | fail | 400 | 367 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-26 22:40 UTC | GET | fail | 400 | 254 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-26 04:40 UTC | GET | fail | 400 | 342 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-25 13:40 UTC | GET | fail | 400 | 314 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-24 16:40 UTC | GET | fail | 400 | 80 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-23 22:40 UTC | GET | fail | 400 | 326 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-23 04:40 UTC | GET | fail | 400 | 83 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-22 13:40 UTC | GET | fail | 400 | 68 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-21 22:40 UTC | GET | fail | 400 | 131 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-21 04:40 UTC | GET | fail | 400 | 175 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-20 13:40 UTC | GET | fail | 400 | 115 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-19 16:40 UTC | GET | fail | 400 | 146 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-18 22:40 UTC | GET | fail | 400 | 84 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-18 04:40 UTC | GET | fail | 400 | 145 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-17 16:40 UTC | GET | fail | 400 | 152 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-16 22:40 UTC | GET | fail | 400 | 107 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-29 | 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.