Traceroute

[Tosa]

It may not be as traditional as the speedtest thread, but it's still an important factor to measure the quality of your internet connection. While the speedtest thread is about measuring how much data you can push through your internet connection at once, this checks checks how far the data has to travel and how fast each packet reaches each point.

 

What I'd like you to do, is to open the command line (terminal or cmd, depending on what OS you use) and type this in and copy&paste the output here

 

Windows:

Quote

tracert www.google.com

 

Mac/Linux:

Quote

traceroute www.google.com

 

If your ISP, router and computer supports IPv6, you can run it with ipv6.google.com and ipv4.google.com instead to measure both your IPv6 and IPv4 connectivity.

[Tosa]

Here's mine

IPv6:

Tracing route to ipv6.l.google.com [2a00:1450:400f:805::200e]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  2001:464b:13ef::1
  2    <1 ms    <1 ms    <1 ms  ti0013a400-lo0-0.ti.telenor.net [2001:4600:0:200::1d]
  3    13 ms    13 ms    14 ms  ti0033c400-lo0-0.ti.telenor.net [2001:4600:0:100::12]
  4    14 ms    13 ms    13 ms  ti0030c400-lo0-0.ti.telenor.net [2001:4600:0:100::11]
  5    13 ms    14 ms    14 ms  ti0001c360-lo0-0.ti.telenor.net [2001:4600:0:100::23]
  6    15 ms    14 ms    14 ms  ti3001c400-lo0-0.ti.telenor.net [2001:4600:0:100::6]
  7    16 ms    15 ms    14 ms  ti3001b400-lo0-0.ti.telenor.net [2001:4600::11]
  8    14 ms    14 ms    14 ms  2001:4860:1:1:0:847::
  9    15 ms    24 ms    15 ms  2001:4860::1:0:26eb
 10    15 ms    15 ms    15 ms  2001:4860:0:1::3e5
 11    14 ms    14 ms    13 ms  arn06s07-in-x0e.1e100.net [2a00:1450:400f:805::200e]

Trace complete.

IPv4:

Tracing route to ipv4.l.google.com [148.123.25.108]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2     1 ms    <1 ms    <1 ms  ti0013a400-gw.ti.telenor.net [88.91.163.1]
  3     6 ms     6 ms     6 ms  ti0013c400-ae2-0.ti.telenor.net [146.172.101.41]
  4     7 ms     6 ms     6 ms  ti0016c400-ae4-0.ti.telenor.net [146.172.98.14]
  5     7 ms     6 ms     6 ms  ti0300c360-ae82-0.ti.telenor.net [146.172.102.133]
  6     6 ms     5 ms     9 ms  ti0267i400-ae0-0.ti.telenor.net [146.172.13.38]
  7     7 ms     7 ms     6 ms  193.212.177.134
  8     6 ms     6 ms     7 ms  148.123.25.108

Trace complete.

Interestingly enough, IPv6 has a few more hops and about twice the ping compared to IPv4.

[Samfisher]

Why .com?  A lot of countries have their local google domain so they should be tracing it there instead.

[Tosa]

Just now, Samfisher said:

Why .com?  A lot of countries have their local google domain so they should be tracing it there instead.

Google has servers all around the globe working together as a CDN (Content Delivery Network), and it would amaze me if using the .com domain (or any other, for that matter) wouldn't lead you to the closest server(s).

[Samfisher]

Just now, Tosa said:

Google has servers all around the globe working together as a CDN (Content Delivery Network), and it would amaze me if using the .com domain (or any other, for that matter) wouldn't lead you to the closest server(s).

On a tracert probably, brain fart.  Browsers however can be forced to load Google from a different region.

 

 

[Tosa]

5 minutes ago, Samfisher said:

On a tracert probably, brain fart.  Browsers however can be forced to load Google from a different region.

I ran nslookup www.google.com, which by my count returned 17 IP adresses, 16 of which are IPv4 adresses. Looking them up, I found they're all within my country and belongs to my ISP. Google apparently use DNS to route your traffic to the nearest server.