Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago

social.gedx402.com/v1/sociavault/twitter/profile

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://social.gedx402.com/v1/sociavault/twitter/profile
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xb3c2776ce3f99cb3366520c27b4ac5d436942ab6
Declared price (base units)14000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-08-142026-10-19
Figure 1. Probe timeline, last 19 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-19 16:40 UTCPOSTpass402742 ms—
2026-10-18 04:40 UTCPOSTpass402585 ms—
2026-10-16 15:40 UTCPOSTpass402404 ms—
2026-10-15 03:40 UTCPOSTpass402680 ms—
2026-10-13 21:40 UTCPOSTpass402594 ms—
2026-10-12 15:40 UTCPOSTpass402757 ms—
2026-10-11 15:40 UTCPOSTpass4022531 ms—
2026-10-10 15:40 UTCPOSTpass402652 ms—
2026-10-09 15:40 UTCPOSTpass402822 ms—
2026-10-08 13:40 UTCPOSTpass402821 ms—
2026-10-01 10:30 UTCPOSTpass40248 ms—
2026-09-25 10:31 UTCPOSTpass402531 ms—
2026-09-21 11:24 UTCPOSTpass402383 ms—
2026-09-17 16:19 UTCPOSTpass402690 ms—
2026-09-14 11:24 UTCPOSTpass402388 ms—
2026-09-11 11:24 UTCPOSTpass402746 ms—
2026-09-07 11:24 UTCPOSTpass402103 ms—
2026-09-02 11:24 UTCPOSTpass402138 ms—
2026-08-14 08:53 UTCGETfail40215 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

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.

20–2,000 characters · 0 so far