Traceroute to the broker: finding where the delay lives

[Amanhasnoname]

When fills feel slow, the cause could be the broker, the platform, the local network or somewhere along the route. A traceroute narrows it down.

The command lists every hop between the computer and the broker's server, with the delay at each stage. On Windows it's tracert followed by the server address. The output shows where the latency jumps. A big step at the first or second hop points at the local router or ISP. A jump partway through suggests congestion on the wider internet. A high delay only at the last hop suggests the broker's side.

Running it at different times of day gives a fuller picture. Some routes degrade in the evening when residential traffic rises.

Armed with the data, it's possible to ask the ISP specific questions, or to decide whether a VPS with a better route is worth it.

Some brokers publish several server addresses, and the best one can differ by location.

Has a traceroute ever revealed something unexpected for you?