Looking Glass Speed Test & Route Tracing Guide
Use FlawlessNode's public Looking Glass nodes (AS60068, AS4837, AS9929) for ICMP ping tests, MTR routing diagnostics, and real payload speed benchmarks.
Evaluating cloud server connectivity requires inspecting latency stability, jitter, and return BGP paths rather than relying solely on peak port ratings. FlawlessNode operates dedicated public Looking Glass (LG) portals across all three Los Angeles network tiers so you can verify route performance before and after deployment.
1. What Is a Looking Glass?
A Looking Glass is a public diagnostic portal deployed directly on our datacenter edge routers. It enables you to run bidirectional tests between our Los Angeles facility and your local IP:
- Ping: Measures Round-Trip Time (RTT) and jitter between our LAX router and your client IP;
- Traceroute / MTR: Maps every autonomous system (AS) hop along the outbound return path;
- Speed Test Files / LibreSpeed: Provides browser speed tests and direct 100MB / 1GB test payloads to benchmark sustained throughput.
2. Official Looking Glass Endpoints
You can launch live diagnostics from our Datacenters Overview or visit the tier-specific Looking Glass portals directly:
- Basic Looking Glass (AS60068): https://lg.lax1.basic.flawlessnode.com — Benchmark high-volume international BGP transit;
- Plus Looking Glass (AS4837): https://lg.lax1.plus.flawlessnode.com — Test China Unicom China169 optimized trans-Pacific return routing;
- Pro Looking Glass (AS9929): https://lg.lax1.pro.flawlessnode.com — Experience CUII Enterprise A-Net zero-loss performance during peak evening hours.
3. Running Accurate Route Diagnostics with MTR
Single-shot ping commands only show end-to-end RTT. When analyzing route handoffs or suspected congestion, use MTR (My Traceroute) for multi-cycle statistical sampling.
3.1 Recommended Client Diagnostic Tools
- Windows: Use portable WinMTR;
- macOS / Linux: Install and run MTR directly in your terminal:
# Install MTR (macOS via Homebrew / Debian & Ubuntu via APT) brew install mtr # macOS apt install mtr -y # Debian / Ubuntu # Run a 50-packet MTR report to a Looking Glass IP or your instance IP mtr -c 50 -r your_test_ip
3.2 How to Interpret an MTR Report
Host Loss% Snt Last Avg Best Wrst StDev
1.|-- 192.168.1.1 0.0% 50 1.2 1.5 1.1 3.2 0.4
2.|-- 100.64.0.1 0.0% 50 4.3 4.6 3.9 10.1 1.1
3.|-- 219.158.113.129 0.0% 50 145.2 146.1 144.5 152.0 1.8 (China Unicom AS4837)
4.|-- 219.158.103.38 0.0% 50 148.4 149.0 147.1 155.3 1.5 (Subsea Landing PoP)
5.|-- 154.xxx.xxx.xxx 0.0% 50 150.1 150.5 149.2 153.4 0.8 (FlawlessNode LAX)
- Intermediate Hop
Loss%with0.0%Final Hop Loss: If an intermediate router shows packet loss (e.g., 30%~60%) while Hop 5 (the final destination) remains at0.0%, this is benign ICMP control-plane rate limiting—not actual data packet loss; - Final Hop
Loss% > 0%: Genuine congestion only exists if packet loss starts at a specific transit hop and persists all the way to the final destination hop. For a deeper dive, see Bi-directional MTR Diagnostics & Packet Loss Analysis.
4. Benchmarking Real Throughput
Open any of the Looking Glass links above in your browser to run the interactive LibreSpeed multi-threaded speed test, or use iPerf3 Throughput & BDP Analysis from your terminal to measure single-stream vs. multi-stream TCP delivery rates.