Timestamp
The record should state when a route was tested. “Online” without time can remain visible long after the condition changed.
Mirror availability / preserved path
This page preserves the established Mars mirror-list intent while removing raw destination strings. Its purpose is to explain how availability records should be assessed before a route is trusted or opened.
Mirror record anatomy
A long list is not automatically a good list. The value comes from provenance, recency and a clear account of how each observation was produced.
The record should state when a route was tested. “Online” without time can remain visible long after the condition changed.
The reader should know whether a fresh Tor circuit was used, how long the checker waited and what counted as a response.
A response, timeout or protocol error is an observation. Labels such as safe, official or verified require different evidence.
The source of the route must be checked separately. Availability cannot transform an unknown address into an authentic one.
Several observations reveal whether a route is stable, intermittent or consistently silent. A single row cannot show that pattern.
A responsible directory says what it did not test: login behavior, account safety, payments and operator control.
Compare carefully
Response time varies with the circuit, geographic path and load. Small timing differences do not establish that one route is safer or more legitimate.
A route that responded once in two seconds may fail on the next circuit. A slower but repeatedly responsive route can provide stronger availability evidence, but it still needs the same identity check.
A timeout can reflect descriptor propagation, circuit construction or service load. Record the result and retry later rather than permanently declaring a route dead from one attempt.
A mirror list copied without timestamps or method inherits none of the original evidence. It is merely a set of strings, and strings are easy to replace.
Mirror list questions
The status desk separates public explanatory content from the destination handoff. This reduces stale copied strings and keeps the page focused on availability methodology.
No. An answer proves only that something responded. Identity must be established through independent, expected evidence.
No. Circuit speed changes from attempt to attempt and is not an authenticity signal. Consistency and provenance matter more.
Confirm that Tor works elsewhere, retry with spacing, and wait for better evidence. Do not lower the identity standard to find a replacement quickly.
Manual handoff
No destination address is printed on this site. The route begins in this tab only after an explicit button press.