Network

Measure the route that matters to your users.

Network marketing numbers are not enough. Test latency and transfer performance from the actual regions and ISPs that matter to your application.

Quick answer

For network-sensitive workloads, test from representative client networks to the actual VPS network. Measure latency, packet loss, route stability and real transfer performance. A single headline bandwidth number does not describe every path on the Internet.

Testing

What to measure

Latency

Measure round-trip time from important user and office networks, not only from a cloud test node.

Packet loss

Persistent loss can harm interactive applications even when nominal bandwidth looks high.

Route

Traceroute or MTR can help identify where a path changes, but interpret results carefully because some hops deprioritise probes.

Real transfer

Use application-relevant transfers and several locations. One speed test should not be treated as universal performance.

Transparency

Looking Glass endpoints are published only when they are real

This package intentionally does not invent test IPs or benchmark URLs. Add production test endpoints in config.php once you have confirmed which SERVER1 network resources are intended for public testing.

Test IP

Publish an address designed for public diagnostics, not a customer or management interface.

Test file

Use a controlled public test object and monitor abuse or unexpected transfer cost.

Looking Glass

Expose only safe diagnostic functions and rate-limit them appropriately.

FAQ

Questions people ask before ordering

Choose by workload, not by guesswork.

If you know the resources you need, open the live catalogue. If not, send the workload and we will help narrow the choice.

Find my VPS