DrugHub Status — Is DrugHub Up or Down Right Now?

Is DrugHub Up Right Now? Latest Status Check

The latest entry records the outcome of the most recent verification probe: the timestamp of the probe, whether the service responded, and whether the response carried a fresh PGP-signed canary that matched the saved signing fingerprint. A DrugHub status of responsive indicates the probe completed and the canary verified; a result of unreachable indicates the probe timed out or returned a Tor-side error; a result of responsive, canary stale indicates the service answered but the canary timestamp is older than the configured freshness window.

Last verified responsive at drughubfcuiheyswp6hlkggjsigirlzjjk2i7vmcdygceaw2kvzhlfqd.onion: 2026-05-15. Canary signature: verified against saved fingerprint. Probe latency: within nominal range. For the full mirror list and PGP verification chain, see the verification record. The previous DrugHub status entry, alongside the full DrugHub uptime log, is recorded in the historical table below.

DrugHub Uptime Log — Connection History & Outages

The DrugHub uptime log preserves every probe outcome with its ISO-8601 timestamp, the probe result (responsive, unreachable, partial), and any anomaly notes. The uptime log is the primary research asset on this page; aggregate metrics like uptime percentage and mean time between observed outages are derived from this raw log rather than reported as headline numbers.

How uptime is measured here

Uptime in this log is measured per probe, not per second. A probe is an attempt to complete a Tor circuit to the recorded onion address and observe a response. A successful probe contributes to recorded uptime in the period it covers; a failed probe contributes to downtime. Continuous uptime is inferred from successful probes spaced across the period, with the inference explicitly noted; this DrugHub uptime log does not claim that every second between probes was online.

What DrugHub down looks like in the log

A DrugHub down entry is recorded when a probe completes with a Tor-side failure: timeout, descriptor lookup failure, or introduction-point unreachability. A failure that persists across multiple probes spaced over hours is logged as an outage event with a start and end timestamp once a subsequent probe returns the service to responsive. A single failed probe between two successes is logged as a transient miss rather than a DrugHub down event, since transient misses correlate with relay congestion rather than service failure.

Mirror observations in the log

Mirror availability is logged separately from primary availability. An entry where the primary onion is unreachable but a verified mirror is responsive is logged as partial, since the service-side state is reachable through the redundancy path even when the primary is degraded. Reading the partial entries is the practical way to distinguish primary-only outages from full-service outages; the latter are markedly less common and markedly more worth investigating.

How DrugHub Status Is Checked: Probe Methodology

The probe approach has three components: the probe construction, the signed-canary verification step, and the anomaly classification rule that decides how a borderline result is logged. Each component is documented here so a reader can independently evaluate whether the DrugHub status entries on this page are produced by a sound process.

Probe construction

Each probe builds a fresh Tor circuit, requests the service descriptor for the recorded onion address, and attempts an HTTP-level handshake against the introduction point. The probe records the round-trip time at each step and the Tor error code on failure. A probe that completes the handshake without retrieving the canary message is logged as a partial result; a probe that retrieves the canary message proceeds to the verification step. This procedure is consistent with the academic standard for darknet-market reachability research and is described, in different vocabulary, in published OPSEC literature.

Signed-canary verification

An entry of responsive requires the probe to successfully retrieve the operator's current signed canary message and verify the signature against the saved fingerprint. A probe that retrieves a canary whose signature does not validate is not logged as responsive; it is logged as responsive, canary signature failed, which is a security-relevant anomaly distinct from ordinary downtime. This distinction matters because canary-signature failure is the strongest available signal of clone-host substitution.

Anomaly classification

Borderline results (slow response, partial canary, intermittent reachability) are classified into one of four buckets: nominal, congested, degraded, and anomalous. Nominal and congested are routine and do not change the recorded state from responsive. Degraded results are logged as partial. Anomalous results are escalated and re-probed at increased frequency until the anomaly resolves or settles into a clear DrugHub down entry. The classification rules avoid over-claiming an outage on transient noise while still surfacing the genuine signals.

DrugHub Not Working? Frequently Asked Questions

Is DrugHub online?

The most recent DrugHub status entry above shows the latest observed state. Is DrugHub online as a real-time question cannot be answered from this page alone; the page records observations at probe timestamps. If the latest probe was within the last six hours and recorded a responsive result, the service was reachable at that time, and unless the log has recorded a subsequent failure, the service is reasonably likely to still be reachable. A reader seeking a stronger answer to is DrugHub online at this exact moment should run an independent probe.

Is DrugHub down?

A DrugHub down state is recorded when consecutive probes fail. The DrugHub uptime log shows the timestamp of the most recent transition from responsive to unreachable, and the timestamp of the most recent return to responsive if the transition has resolved. Is DrugHub down as a question is best answered by reading those two timestamps: a DrugHub down entry that has not yet been closed indicates a current outage; a closed entry indicates a past outage with a measurable duration.

Why does DrugHub status sometimes show as partial?

A partial entry indicates that the primary onion service was unreachable while a verified mirror remained responsive, or that the canary was retrieved but its timestamp was older than the configured freshness window. The partial state is a useful intermediate result because it distinguishes primary-only degradation from full-service outage, and stale-canary partials are an early warning for canary-cessation events that historically precede operator silence.

How is the DrugHub status verified to be real?

Every responsive entry is paired with a successful PGP signature check against the saved operator fingerprint. A result without a verified canary is not classified as responsive. This means a clone host imitating the service cannot produce a result of responsive in this log unless it controls the operator's signing key, which is the security property the entire approach depends on.

DrugHub Availability: Reading the Record Critically

The DrugHub status record is most useful when read alongside two other inputs: the verification record on the homepage that establishes the canonical onion address being probed, and the broader OPSEC reasoning behind probe-based monitoring. Verifying the address chain is upstream of monitoring its DrugHub status, and the probe process applied here borrows directly from the broader darknet market OPSEC reasoning documented elsewhere on the site. A reader who understands both the probe steps and the verification model treats the record as one input among several; a reader treating it as a real-time go/no-go indicator is using the page in a way the data does not support.

The pattern observable across years of darknet-market status logs, including this one and the historical logs preserved in research archives, is straightforward: services that maintain a clean signing chain through observable downtime survive the downtime; services that go silent during outages, or whose canary signatures fail mid-outage, do not. The record exists to make that signal observable for one specific service.