Prime Market Infrastructure Health
Real-time operational data, mirror availability, and a running changelog of every meaningful platform update. All Prime Market subsystems are monitored continuously through automated health probes distributed across the Tor network.
The onion address below has been cryptographically verified against the Prime Market signing key. Cross-reference this URL every time you open the marketplace to ensure you are connecting to the authentic platform.
http://primeyr5lrerg5wigkzd7qp46kaq7f2qco7tgbmdmo2bdvmiwnbixkid.onion
Last Verified: Feb 2026
Feature CAPTCHA Upgraded to Proof-of-Work
The traditional image-based CAPTCHA has been replaced with a lightweight proof-of-work challenge. This eliminates accessibility issues for visually impaired users while raising the cost of automated scraping and credential-stuffing attacks. Each challenge takes roughly two seconds on standard hardware and requires no user interaction beyond clicking a single button. Read more about platform defenses in the features section.
Feature Mirror Infrastructure Expanded to 5
Two new mirrors have been provisioned across geographically separated hosting providers, bringing the total active count to five. This expansion improves load distribution during peak hours and adds additional redundancy against localized takedown attempts. All five mirrors share a synchronized database backend with sub-second replication lag. The mirror architecture is outlined on the security page.
Update Monero Subaddress Per-Transaction
Every incoming deposit now generates a unique Monero subaddress, replacing the previous rotating-address model. This ensures that deposits can never be correlated on-chain even if multiple transactions land in the same block. The wallet backend handles key derivation locally with no external RPC dependency. Learn how this fits into the broader payment flow in the getting started guide.
Security Phishing Campaign Detected
A coordinated phishing operation targeting Prime Market users was identified and publicly disclosed. The attackers deployed cloned login portals on four separate onion addresses, distributing links through Dread threads and Telegram groups. The fraudulent domains have been reported and documented. Users should always verify the URL before logging in — consult the security page for the canonical address.
Feature Vendor Verification v2
The vendor onboarding pipeline now requires PGP key ownership proof and a refundable bond denominated in Monero. Vendors who pass the expanded verification receive a visible trust badge on their storefront. This makes it significantly harder for scam accounts to gain initial traction. The complete vendor workflow is documented in the platform guide.
Update Tor v3 Migration Complete
All legacy v2 onion addresses have been retired. The platform now operates exclusively on Tor v3 hidden services, which use longer 56-character addresses derived from ed25519 keys. This provides stronger cryptographic guarantees and prevents certain classes of address-enumeration attacks that affected the older protocol version. Visit the security overview for more details on cryptographic standards.
Update Auto-Finalization Extended to 14 Days
The escrow auto-finalization window has been lengthened from 10 to 14 days, giving buyers additional time to confirm receipt of physical goods shipped over long distances. This change was driven by community feedback on the dispute forum. Vendors retain the option to request early release once tracking confirms delivery. Details on escrow mechanics are available in the features breakdown.
Security Security Audit Published
An independent security audit covering the marketplace codebase, server hardening, and cryptographic implementations has been completed and published in full. The audit identified zero critical vulnerabilities and three medium-severity findings, all of which were remediated before publication. The summary is available on the security page.
The latest stable Tor Browser release ships with an upgraded circuit-building algorithm that reduces connection latency by approximately fifteen percent. The new version also patches three medium-severity vulnerabilities in the rendering engine. All Prime Market users should update immediately because older builds may expose timing metadata that weakens anonymity. Download exclusively from the official Tor Project website and verify the GPG signature before installation. Keeping your browser current is one of the most impactful steps you can take to maintain operational security while browsing the Prime Market platform.
Monero's latest consensus upgrade increases the mandatory ring size from 11 to 16, substantially expanding the anonymity set for every transaction. Larger rings make statistical de-anonymization techniques less effective, strengthening the privacy guarantees that Prime Market relies on for its payment infrastructure. Users who hold Monero in personal wallets should update their client software to remain compatible with the new consensus rules. This hard fork represents one of the most significant privacy improvements in Monero's recent history.
Tails 6.0 transitions from the legacy X11 display server to Wayland, closing an entire category of screen-capture and keylogging attack vectors that affected earlier releases. The new display protocol isolates application windows from one another, preventing malicious programs from reading input intended for other applications. For users who access Prime Market through Tails, this upgrade is a meaningful security improvement. The Tails team recommends a fresh installation rather than an in-place upgrade for maximum integrity assurance.
How Prime Market Tracks Platform Health
The status indicators displayed on this dashboard are powered by a distributed monitoring system that operates entirely within the Tor network. Unlike clearnet uptime services that rely on centralized probe infrastructure, Prime Market uses a mesh of independent monitoring nodes that each perform health checks against every mirror and subsystem on a sixty-second cycle. When a mirror fails three consecutive checks from at least two separate monitoring nodes, the automated failover system reroutes traffic to the remaining active instances without any user intervention required.
Multi-Layer Health Probes
Each health check tests multiple layers of the stack. The first probe verifies TCP connectivity to the onion address. The second probe issues an HTTP request and confirms the response code and body hash match the expected baseline. The third probe authenticates against a canary endpoint that exercises the database connection, the escrow signing module, and the Monero wallet daemon in a single round trip. Only when all three probes return a passing result does a mirror remain in the active rotation. This layered approach catches partial failures that simpler ping-based monitoring would miss — for example, a scenario where the web server responds but the database cluster is in a degraded state.
Incident Response Workflow
When a subsystem enters a degraded or offline state, the monitoring mesh triggers an automated incident workflow. First, the affected component is isolated from the load balancer to prevent user-facing errors. Second, a diagnostic snapshot is captured for later forensic analysis. Third, the failover controller activates a standby instance from the reserve pool. This entire sequence completes in under ninety seconds for most failure scenarios. The development team receives a parallel notification through an encrypted channel and begins manual investigation while the automated recovery stabilizes the platform. Historical incident data is retained for ninety days and informs ongoing capacity planning decisions.
Transparency and User Trust
Prime Market publishes this status dashboard as part of its commitment to operational transparency. Many marketplace platforms operate with zero visibility into their infrastructure health, leaving users to guess whether a slow page load indicates a server problem, a network issue, or an active attack. By exposing real-time status data, Prime Market enables users to make informed decisions about when to transact. If you are new to the platform and want to understand the full user workflow, the step-by-step guide covers everything from initial Tor Browser setup to placing your first order with multi-signature escrow protection. For an in-depth look at the cryptographic and operational security measures that protect the infrastructure behind this dashboard, visit the security page.
Status Indicators
- Green dot — subsystem is fully operational and passing all health checks
- Orange dot — subsystem is experiencing degraded performance but remains functional
- Red dot — subsystem is offline or unreachable from the monitoring mesh
Monitoring Frequency
All subsystems are checked every 60 seconds from multiple vantage points within the Tor network. Mirror failover activates after 3 consecutive failed checks.
Useful Links
- Prime Market Overview — platform introduction and key features summary
- Features — escrow, encryption, and vendor tools
- Getting Started Guide — complete walkthrough for new users
- Security — threat model, audit results, and best practices