connection status

The connection status screen shows your device's current public IP address as seen from the internet, the Nettica VPN network you are connected through, and the measured round-trip latency to ip.nettica.com. Use it to verify that a tunnel service is routing your traffic correctly.

The app bar title is a tappable link — tap it to open ip.nettica.com in your browser.

Open connection status in the Nettica app →


Public IP Address

The large text in the center of the screen is your current public IP address, fetched from ip.nettica.com the moment the screen opens. Tap it to copy the address to the clipboard.

When a Nettica tunnel service is active and routing all traffic (Allowed IPs includes 0.0.0.0/0), the IP shown should match the tunnel service's server IP address — not your ISP's address. If it matches, the tunnel is working correctly.

When a relay service is active (split tunnel - traffic is not fully tunneled), the IP shown will be your ISP's address, which is expected.


VPN Status Line

Below the IP address, a status message describes the current connection:

Tap the status line to copy its text to the clipboard.


Server Description

When connected, a second line may appear showing the service description — the geographic location and datacenter name of the server your traffic is exiting through. This is useful to confirm you are connected to the region you intended.


Latency (Ping)

The latency value shown is an average of three consecutive round-trip requests to ip.nettica.com, measured in milliseconds. All three pings are made automatically when the screen opens. We use HTTPS, not ICMP ping, to measure performance. This provides more accurate results in real-world conditions.

Higher latency can indicate:

Latency through a tunnel VPN will always be somewhat higher than your baseline internet latency because traffic makes an extra hop through the service. Choose a server location close to you to minimize the added latency.


Fix Button

The Fix button appears only when the app detects a mismatch between the expected tunnel server IP and the IP address currently reported by ip.nettica.com — and the mismatch is not explained by On-Demand or Per-App VPN being active.

Tapping Fix:

  1. Stops the current WireGuard tunnel.
  2. Waits 2 seconds for the disconnect to complete.
  3. Re-adds and restarts the tunnel.
  4. Waits 3 seconds for the tunnel to establish.
  5. Re-fetches your public IP to verify the fix worked.

After the fix completes, the IP address updates automatically. If the address now matches the tunnel server, the Fix button disappears.