Measured path
Public ingress
通常アクセスでは、ブラウザ → Playit ゲートウェイ → REALITY の HTTPS 転送 → Caddy → Raspberry Pi の経路を測定します。
A direct visit measures browser → Playit gateway → REALITY HTTPS forwarding → Caddy → Raspberry Pi.
Connection lab / single flow
Path signal単一フロー通信試験
一般的な多重接続の速度テストではありません。遅延、ダウンロード、アップロードを一つずつ順番に実行し、この Raspberry Pi までの実用的な通信状態を測ります。
This is not a conventional multi-connection speed test. It runs latency, download, and upload sequentially to estimate the practical state of the path to this Raspberry Pi.
Checking…HTTPS endpoint
— msMedian HTTP RTT
— msHTTP jitter
—Browser protocol
One request at a time
単一接続に近い測定
A single-flow approximation
Ready
Download—Mbps · one GET
Upload—Mbps · one POST
TTFB—ms · measured GET
P95 RTT—ms · sequential HTTP
12 sequential HTTP probes, one measured download, then one measured upload. No phase runs in parallel.
Test model
Sequential by design
各段階は直列です。複数ダウンロードで帯域を埋めず、一つの通常の TLS 転送に近い結果を優先します。
Every phase is sequential. The test favors the behavior of one ordinary TLS transfer instead of filling the link with parallel downloads.
Interpretation
Approximate signal
これは ICMP ping や iperf3 ではありません。REALITY クライアント経由で開いた場合は、そのプロキシ経路も結果に含まれますが、ページ側では利用経路を判別できません。
This is neither ICMP ping nor iperf3. If opened through your REALITY client, that proxy path contributes to the result, but the page cannot identify the route in use.
Method notes
What the numbers mean.
Median HTTP RTT is the middle result from sequential no-cache requests over the active browser connection. Jitter is the average change between adjacent samples. Neither value is an ICMP ping.
Download reads one random object for up to roughly twelve seconds after a short warm-up. Upload sends one adaptively sized binary request to a memory-free sink; the body is counted and discarded, never written to disk.
Results remain in this browser tab. The node stores no test result, account, identifier, or uploaded content.