traceroute explains low speeds

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I Plan to Stick Around
Posts: 8

traceroute explains low speeds

Hi all,

 

In an effort to understand why speed has become ridiculously slow with my W35, I did a few traceroutes and here's a typical one:

 

traceroute to ftp.xxx.org (64.34.120.xx), 30 hops max, 40 byte packets using UDP
1 FWT (192.168.1.1) 0.910 ms 0.703 ms 0.657 ms
2 74.198.64.254 (74.198.64.254) 3533.530 ms 3612.166 ms 3610.857 ms
3 172.25.199.65 (172.25.199.65) 3658.916 ms 3697.919 ms 3816.628 ms
4 10.118.20.10 (10.118.20.10) 3816.093 ms 3814.594 ms 3872.375 ms
5 10.118.20.77 (10.118.20.77) 3871.226 ms 3939.219 ms 4017.881 ms
6 192.168.1.69 (192.168.1.69) 4027.244 ms 4074.989 ms 4093.230 ms
7 192.168.1.18 (192.168.1.18) 4162.193 ms 4180.632 ms 4209.460 ms
8 172.25.192.176 (172.25.192.176) 58.668 ms 57.283 ms 76.009 ms
9 10.118.2.209 (10.118.2.209) 75.396 ms 74.469 ms 73.266 ms
10 74.198.64.34 (74.198.64.34) 72.480 ms 70.989 ms 69.840 ms
11 69.63.248.133 (69.63.248.133) 126.875 ms 146.487 ms 145.493 ms
12 69.63.249.165 (69.63.249.165) 144.584 ms 143.473 ms 142.650 ms
13 64.71.240.66 (64.71.240.66) 141.407 ms 140.295 ms 176.974 ms
14 * * *

 

It doesn't stop there but the point is that up to the 13th hop, we are still on the Rogers network. I ran a whois on all ips and learned that 74.198.xxx.xxx are Rogers Wireless, 69.63.240.xxx and 64.71.240.xxx are Rogers Cable and the others are private address space. I cannot explain what is going on at hops 6 and 7...

 

It doesn't matter what site you are tracing, it will always make those 13 hops first and this is where most of the delays occur.

 

So the problem is not my hub, the signal strength, the distance to the tower or weather conditions. The problem is how Rogers route the traffic. And whatever is going on in hops 2 to 11 (before it reaches the cabled network).

 

Where can I go from here?

 

cheers

 

 

 

 

***Edited labels***

Highlighted
Resident Expert
Resident Expert
Posts: 14,259

Re: traceroute explains low speeds

That is one seriously messed up traceroute...

There is no reason at hop 6-7 that it should be going back into someones private IP network range.

 

Maybe if someone else who has the w25 can do a tracert on theirs, and see what the outcome is, if its similar or not, etc.



Highlighted
I'm an Advisor
Posts: 842

Re: traceroute explains low speeds

@Gdkitty:

 

I like your suggestion that others post traceroute results.  But I should point out several things: Rogers has never supplied the (Ericsson) W25 to the best of my knowledge.  The Ericsson W35 was supplied however.  Also, there should not really be much difference in traceroute results for any RocketHub variant.  There are a lot of Netcomm RocketHubs in service, with at least three different models being in use.  So those results will also be relevant.

 

I have been using the Rogers RocketHub W35 for about 30 months now.  I have on a number of occasions done traceroutes to attempt an analysis of the network connections between me and the Internet at large.

 

Here is my current traceroute to 8.8.8.8 from my home, through the Rogers RocketHub:

********************************

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  FWT [192.168.1.1]
  2   129 ms   204 ms   284 ms  74.198.28.241
  3   210 ms   101 ms   204 ms  172.25.120.65
  4   232 ms   204 ms   408 ms  172.25.11.65
  5   232 ms   194 ms   111 ms  192.168.1.72
  6    54 ms   199 ms  1331 ms  192.168.1.18
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9   642 ms   204 ms   101 ms  74.198.28.18
 10   532 ms   217 ms   330 ms  24.153.3.89
 11   407 ms   204 ms   101 ms  69.63.248.81
 12   232 ms   306 ms   203 ms  gw01.esna.phub.net.cable.rogers.com [66.185.80.1
97]
 13   738 ms   613 ms   614 ms  72.14.216.189
 14  2482 ms  2764 ms  2021 ms  209.85.254.120
 15   413 ms   204 ms   409 ms  209.85.242.209
 16   233 ms   203 ms   204 ms  72.14.236.200
 17   232 ms   204 ms   408 ms  72.14.232.21
 18   232 ms   204 ms   409 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

*********************************

 

My location is just west of the Greater Toronto Area.  I would assume that there would be a difference in the routing one would see on a traceroute between different locations in Canada.  But I am making an assumption there.

 

I have never been impressed with the speeds we experience through our RocketHub.  I also am not impressed by the random disconnects we experience caused I believe by overloading of the cellular network.

 

But this is about the best we can get in our rural location.

 

skinorth

 

Highlighted
I Plan to Stick Around
Posts: 8

Re: traceroute explains low speeds


@skinorth:
Your results are pretty close to mine although your response times are faster. I ran another one this morning and got around 1800ms for the first 7 hops. Ran it again tonight and got 300-400ms for the same hops. So it seems to vary greatly. I am located in a rural region 20km north of Gatineau where Rogers is the only option for internet access. As you say, seems it's the best we can get...

@Gdkitty:

 

Those 192.168.1.xxxx  hops make no sense to me either... I recall reading about why that is but cannot remember where.

 

cheers

 

Highlighted
Resident Expert
Resident Expert
Posts: 14,259

Re: traceroute explains low speeds

woops, the w25 was a typo by me, meant w35, was typing from my phone 🙂



Highlighted
I Plan to Stick Around
Posts: 8

Re: traceroute explains low speeds

I wish we had more traceroutes to compare... even some from cable internet users would help. I am pretty sure they don't get those 7 first hops. And can we speculate that the second hop's IP is the IP of the first server actually connected to the internet? So the time between hops 1 and 2 would be the time it takes for a packet to travel from the W35 to the tower and from tower to tower until it reaches the server (or the other way around), right? I wish I knew the physical location of that server but of course, this information is classified 🙂

 

I am asking this because speedtest.net seems to think I am in Montreal but I am much closer to the one in Kanata. So I'm not sure what to make of that...

 

cheers

PS: that spell check is a joke!

Highlighted
Resident Expert
Resident Expert
Posts: 14,259

Re: traceroute explains low speeds

While not at home, so i cant post it.. i can tell you that a cabled one, is much less hops.

From my laptop, you usualy see the router, my modem IP, then from there rogers network ones.. maybe 2-3 sometimes more depending on where its going, then out to bell, at&t, etc.

 

While not a cellular expert.. there i know there is a lot more translation between the two networks.  A mobible IP address, often can not be pinned from the regular ineternet.. as there is a translation somewhere, between the regular internet and the mobile network (its almost like the IPs used for that companies celular network, are a HUGE private network, if you get what im saying).



Highlighted
I'm an Advisor
Posts: 842

Re: traceroute explains low speeds

Here is the traceroute from my work location to 8.8.8.8, which I previously posted for my home location, via RocketHub and Rogers cellular:

 

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  192.168.1.1
  2    10 ms    10 ms    10 ms  ip195.216.145.111.nas.net [216.145.111.195]
  3    11 ms    10 ms    10 ms  g3-17.h.rd01.caonham02.0000.nas.net [216.145.111
.89]
  4    13 ms    12 ms    11 ms  g1-0-1.h.sd01.caontor01.0000.nas.net [216.145.11
1.49]
  5    12 ms    12 ms    11 ms  g0-3.h.rt01.caontor01.0000.nas.net [216.145.111.
69]
  6    13 ms    13 ms    14 ms  gw-google.torontointernetxchange.net [206.108.34
.6]
  7    13 ms    13 ms    12 ms  209.85.255.232
  8    32 ms    33 ms    32 ms  209.85.255.235
  9    42 ms    43 ms    39 ms  209.85.249.11
 10    37 ms    37 ms    38 ms  72.14.238.16
 11    42 ms    38 ms    50 ms  72.14.232.21
 12    38 ms    38 ms    39 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

My work location uses an ADSL connection through a smaller local ISP, which obviously uses DSL provided by the Bell network.  Note that the times are much, much, much faster, and there are a third fewer hops to get to 8.8.8.8.

 

skinorth

 

Highlighted
I Plan to Stick Around
Posts: 8

Re: traceroute explains low speeds

Well, I guess we won't get more...

Good news though: the situation has improved since. I now get 1-2 Mbps downlink which is much better than the 0.3-0.5 I had at the time. Still not the promised speed but I doubt we will ever get there...

 

If anything, the traceroute exercise taught me that the mobile route to the internet is more convoluted than the regular one, regardless of the provider. It takes 10 hops or more to actually reach the internet; everything before that happens between the provider's servers. And asking them what really goes on and why it takes so long is futile.

 

cheers

Highlighted
I'm an Advisor
Posts: 842

Re: traceroute explains low speeds

Here is tonight's traceroute to 8.8.8.8 through my W35 and the Rogers cellular network:

 

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  FWT [192.168.1.1]
  2  1875 ms   204 ms   409 ms  74.198.28.241
  3   233 ms   204 ms   101 ms  172.25.120.65
  4   232 ms   204 ms   101 ms  172.25.11.65
  5   232 ms   204 ms   408 ms  192.168.1.72
  6   654 ms   613 ms   479 ms  192.168.1.18
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9  1775 ms   613 ms   613 ms  74.198.28.18
 10   446 ms   613 ms   613 ms  24.153.3.89
 11   642 ms   613 ms   613 ms  69.63.248.233
 12   641 ms   613 ms   613 ms  69.63.250.154
 13   642 ms   613 ms   613 ms  72.14.216.185
 14   641 ms   613 ms   613 ms  209.85.254.128
 15   697 ms   613 ms   531 ms  72.14.237.130
 16   560 ms   613 ms   613 ms  209.85.241.22
 17   641 ms   613 ms   613 ms  216.239.46.191
 18     *        *        *     Request timed out.
 19  1919 ms   613 ms   613 ms  google-public-dns-a.google.com [8.8.8.8]

 

Impressive, what?????

 

skinorth