Testing Your Connection

Torus Echo the— Connectivity Test Service

Once you have configured your VPN connection, you can verify it is working correctly by connecting to the Torus Echo service. This is a dedicated test endpoint that is always available on the Torus mesh network.

Test Endpoint

Testing via Web Browser

The easiest way to test your connection:

1. Connect to the Torus VPN using your WireGuard configuration
2. Open a web browser
3. Navigate to http://10.254.16.50/100.102
4. You
5. If youshould see a dark-themed page with a pulsing green ring and the "Torustext Echo“Connected -to ConnectionTorus”

The Successful"page page,automatically measures your VPNround-trip islatency working!(average of 4 samples) and displays your WireGuard tunnel IP address.

Testing via Command Line

Using ping

ping 10.254.100.102

Expected output for a user connected to the London hub:

PING 10.254.100.102 (10.254.100.102): 56 data bytes
64 bytes from 10.254.100.102: icmp_seq=0 ttl=64 time=12.3 ms

Using curl (HTTP)

curl http://10.254.16.50/100.102/ping

Expected output: HTML content with "Connection Successful" message

Using ping

ping {"status":"ok","remoteIp":"10.254.16.50100.109","rtt":"0.01","node":"10.254.100.102","hub":"eu-west-2"}

The

ExpectedremoteIp output:field Repliesshows your WireGuard tunnel IP address — useful for verifying you are connecting from 10.254.16.50the withcorrect interface.

Expected Latency

The echo service runs on the London (eu-west-2) hub. Your latency typicallydepends 100-150mson physical distance:

telnet 10.254.16.50

Troubleshooting

Cannot reach 10.254.16.50100.102

• Check VPN is connected -— Verifyrun WireGuardsudo showswg "Latestshow handshake"and verify latest handshake is within the last few2–3 minutes. Even if theyour client shows connected...connected, it could be lying to you :)you.
• Check your AllowedIPs -— Mustyour WireGuard config must include 10.254.16.0/24 (Note: this subnet is the Torus overlay).subnets. For Plus/Pro users with 0.0.0.0/0, all traffic is tunnelled. For Basic users, ensure 10.254.100.0/24 is included.
• Branch router users — if you connect through a MikroTik on your LAN, ensure you have a masquerade NAT rule for LAN traffic going out the WireGuard interface. Without this, your packets arrive with a private LAN IP that the echo service cannot route back to.
• Firewall rules -— Ensureensure your local gateway devicenetwork allows trafficoutbound UDP on port 13231 (the WireGuard listen port for all Torus hubs).
• Cross-hub users — if you are connected to Ohio or Frankfurt, reaching the echo service requires working inter-hub routing. Try pinging your own hub gateway first (e.g. 10.254.16.0/2417.1 for Ohio).

High latencyLatency (>300ms)

• The echo server is located in Dubai, UAE - expect 100-250ms from Europe/US
• If latency exceeds 500ms, checkCheck your internet connection quality.quality Some— pingpacket toolsloss timeand outjitter aton 1000msyour (1upstream second),ISP solink ifwill compound inside the tunnel.
• If you getare 'nofar replyfrom from'the or'London unreachable',hub thengeographically, high latency is expected. See the table above for reference values.
• If latency is significantly higher than expected for your region, try to increaserestarting your timeout.WireGuard interface.

Latency Shows 0ms in Browser

Your browser is serving a cached version of the page. Hard refresh with Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (macOS).

Still notNot working?Working?

See

Contactthe Connection Issues guide in the Troubleshooting book for a step-by-step diagnostic walkthrough, or contact support via the Support pageForum (Forum will be coming 2026).

Technical Details

The Torus Echo service runsis a lightweight Node.js HTTP server running on anthe isolatedFreeBSD networkapplication segment behind a Mikrotik Cloud Hosted Routerserver (CHR)10.255.9.11). It provides:listens on a dedicated WireGuard tunnel IP (10.254.100.102) within the London hub’s user subnet.

• HTTP (port 80): nginx web server with— connectivity confirmation page with client-side latency measurement
• TelnetICMP — responds to ping for basic reachability testing
• Firewall — accepts only ICMP and HTTP from the Torus network (port10.254.0.0/16). 23):Not Securereachable echofrom daemonthe -public charactersinternet.

The are reflected, no shell access

IP Addressaddress 10.254.16.50100.102 is permanently reserved for this service and will never be allocated to users.