Explain how trace routes work and clarify private IPs when converting to external IPs.
Explain how trace routes work and clarify private IPs when converting to external IPs.
Hello, I'm not familiar with network details so I'm curious about this private IP's role. It seems I'm troubleshooting latency problems for a game. Looking at the tracing, the route goes through several hops before reaching api.bethesda.net. The path shows a mix of high and low latency values, which might explain the performance issues.
It means something technical or complex that most people don't understand. It's like talking about gadgets or systems in a way that's hard to grasp for someone who isn't familiar with the subject.
Connecting to your ISP involves a DNS lookup, typically handled by a data center or internet exchange. The DNS server translates the URL you entered into an IP address that directs traffic to the website host. When your router leaves your local network, it always routes through your ISP's DNS first. It seems your router was initially connecting to the DNS, which then forwarded you to another server in the same exchange but on a different subnet. Each transition to a new server is referred to as a bounce. In short, your packets were redirected between subnets within the same network. This is just my interpretation; I might be mistaken.