ForceVPS Network Tools

Looking Glass for route inspection and reachability checks

Use ForceVPS Looking Glass to diagnose network routes, verify server reachability, and analyze BGP routing. The tool allows you to perform Ping, Traceroute, and BGP Lookup tests from multiple network points of presence, helping you quickly identify connectivity issues and evaluate routing quality.

Back to Diagnostics Open Ticket
4 launch POPs
3 query modes
IPv4/IPv6 address families
Looking Glass Route View ForceVPS mockup
Kyiv POP
Traceroute
BGP Lookup
Query

Network Testing Interface

Choose a test type, enter an IP address or domain name, and select the location from which the test will be performed. The service supports Ping, Traceroute, and BGP Lookup over IPv4 and IPv6, helping you analyze latency, traffic paths, and resource availability from multiple ForceVPS network locations.

Query target
Launch node
Protocol
Extra options
Primary settings
Output options
The agent response or transport error will appear in the console on the right.
CLI

Result preview

$ lg ping --node kyiv --family ipv4 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data 64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=18.4 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=18.1 ms --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss

Frequently Asked Questions

Looking Glass is an online network diagnostic tool that lets you check the availability of an IP address or domain from servers in different locations. You can use it to run Ping and Traceroute tests, measure network latency and packet loss, and inspect the route taken by traffic.
Enter an IP address or domain name, select a test location, and start the Ping test. The tool will show whether the destination is reachable, its response time in milliseconds, and any detected packet loss.
Traceroute shows the network path from the selected ForceVPS server to an IP address or domain. The results include intermediate network hops and the latency at each stage, helping you identify routing points with high latency or connectivity problems.
Ping and Traceroute results can vary depending on the user's location, internet provider, and network route. Testing from multiple locations helps determine whether an issue is global, regional, or related to the routing of a specific network operator.
Latency below 30 ms is considered very good, while 30–70 ms is generally suitable for most websites and applications. Latency above 100 ms may become noticeable. However, a normal Ping depends on the physical distance to the server, route quality, and type of service being used.
Packet loss means that some test requests did not receive a response. It may be caused by network congestion, an unstable connection, ICMP filtering, routing problems, or the configuration of the destination server. Occasional missed responses do not always indicate a fault, so compare the result with Traceroute tests from other locations.
The server may block or limit ICMP requests using a firewall or DDoS protection system. In this case, the website or service can remain available even though the online Ping test receives no response. For further network diagnostics, run a Traceroute test and check whether the required service port is reachable.

Powered by WHMCompleteSolution