dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
961
share rss forum feed

MEeastern_ca

join:2012-01-12
Brampton, ON

Electronicbox traceroute to www.google.com?

I would like a comparison from anyone on the electronicbox network to google.com. I believe my traceroute is not correct to google.com and I am experiencing slow downs. Here is an example of a traceroute from Electronicbox to www.google.com. My public IP is 74.116.190.239.

2 erx01-mtl.electronicbox.net (74.116.184.12) 60.329 ms 68.252 ms 63.983 ms
3 mx480-ge-1-3-0.electronicbox.net (74.116.184.2) 72.053 ms 59.804 ms 64.407 ms
4 xe-0-0-1-613.cr1.mtl1.ca.nlayer.net (69.31.141.1) 84.615 ms * 95.555 ms
5 xe-0-1-0.cr1.tor1.ca.nlayer.net (69.22.142.81) 69.764 ms * 92.384 ms
6 gw-google.torontointernetxchange.net (206.108.34.6) 108.220 ms 109.467 ms 152.141 ms
7 209.85.255.232 (209.85.255.232) 76.623 ms
216.239.47.114 (216.239.47.114) 97.489 ms
209.85.255.232 (209.85.255.232) 79.110 ms
8 72.14.236.226 (72.14.236.226) 83.174 ms
72.14.236.224 (72.14.236.224) 146.445 ms
72.14.236.226 (72.14.236.226) 78.053 ms
9 72.14.236.209 (72.14.236.209) 91.709 ms 178.807 ms
72.14.236.207 (72.14.236.207) 81.848 ms
10 209.85.251.88 (209.85.251.88) 87.581 ms
209.85.251.37 (209.85.251.37) 98.321 ms 95.166 ms
11 209.85.249.11 (209.85.249.11) 88.217 ms *
72.14.239.93 (72.14.239.93) 87.658 ms
12 209.85.243.114 (209.85.243.114) 140.884 ms 161.752 ms 105.981 ms
13 64.233.174.117 (64.233.174.117) 94.855 ms
64.233.174.87 (64.233.174.87) 97.636 ms
216.239.48.103 (216.239.48.103) 96.353 ms
14 * * *
15 * vb-in-f147.1e100.net (173.194.73.147) 92.815 ms 151.506 ms

MEeastern_ca

join:2012-01-12
Brampton, ON
Here is the same post with host names

2 erx01-mtl.electronicbox.net (74.116.184.12) 77.608 ms 131.805 ms 66.652 ms
3 mx480-ge-1-3-0.electronicbox.net (74.116.184.2) 106.683 ms 134.043 ms 66.744 ms
4 te0-5-0-6.ccr21.ymq02.atlas.cogentco.com (38.104.154.13) 97.583 ms 63.599 ms 71.568 ms
5 te0-3-0-4.mpd21.jfk02.atlas.cogentco.com (66.28.4.202) 90.309 ms
te0-6-0-6.mpd21.jfk02.atlas.cogentco.com (154.54.46.34) 89.163 ms
te0-1-0-6.mpd22.jfk02.atlas.cogentco.com (154.54.46.22) 69.706 ms
6 te0-3-0-3.mpd22.dca01.atlas.cogentco.com (154.54.5.73) 97.651 ms
te0-0-0-6.mpd22.dca01.atlas.cogentco.com (154.54.26.173) 76.182 ms
te0-0-0-2.mpd22.dca01.atlas.cogentco.com (154.54.5.253) 79.385 ms
7 te0-1-0-7.mpd22.atl01.atlas.cogentco.com (154.54.28.14) 86.470 ms
te0-0-0-6.mpd22.atl01.atlas.cogentco.com (154.54.3.65) 83.934 ms
te0-3-0-7.mpd22.atl01.atlas.cogentco.com (154.54.27.98) 86.577 ms
8 te0-2-0-7.mpd22.iah01.atlas.cogentco.com (154.54.42.221) 135.317 ms
te0-1-0-2.mpd22.iah01.atlas.cogentco.com (154.54.5.53) 130.316 ms 109.983 ms
9 te8-1.ccr01.sat01.atlas.cogentco.com (154.54.29.38) 105.614 ms
te4-3.ccr01.sat01.atlas.cogentco.com (154.54.46.6) 159.256 ms
te8-1.ccr01.sat01.atlas.cogentco.com (154.54.29.38) 147.083 ms
10 te7-2.ccr01.phx02.atlas.cogentco.com (154.54.40.161) 128.727 ms
te7-1.ccr01.phx02.atlas.cogentco.com (154.54.6.249) 134.279 ms
te8-2.ccr01.phx02.atlas.cogentco.com (154.54.83.62) 170.121 ms
11 te2-1.mag02.phx02.atlas.cogentco.com (154.54.85.86) 159.665 ms
te2-1.mag01.phx02.atlas.cogentco.com (154.54.85.82) 147.707 ms
te2-1.mag02.phx02.atlas.cogentco.com (154.54.85.86) 129.150 ms
12 vl3510.na41.b022559-0.phx02.atlas.cogentco.com (38.20.54.182) 138.673 ms
vl3810.na41.b022559-0.phx02.atlas.cogentco.com (66.28.64.210) 125.233 ms
vl3510.na41.b022559-0.phx02.atlas.cogentco.com (38.20.54.182) 201.250 ms
13 38.104.116.178 (38.104.116.178) 127.934 ms 167.034 ms 127.758 ms
14 ae2-0.io-phx1-ex8216-2.cnet.com (64.30.227.118) 194.112 ms 205.472 ms 155.706 ms
15 phx1-rb-gtm1-tron-xw-lb.cnet.com (64.30.224.103) 133.761 ms 123.222 ms 154.507 ms

xcimo
Ebox 60Mbps

join:2007-11-21
Gatineau, QC
reply to MEeastern_ca
Tracing route to google.ca [173.194.75.94]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.100.0.1
2 8 ms 7 ms 7 ms 10.251.113.193
3 14 ms 14 ms 12 ms 10.170.168.225
4 14 ms 11 ms 11 ms 10.170.177.209
5 16 ms 23 ms 23 ms 10.170.178.113
6 10 ms 11 ms 11 ms cable-10g.electronicbox.net [74.116.184.78]
7 11 ms 9 ms 21 ms mx480-xe-1-0-1.electronicbox.net [74.116.184.73]
8 10 ms 9 ms 11 ms xe-0-0-1-613.cr1.mtl1.ca.nlayer.net [69.31.141.1]
9 18 ms 17 ms 17 ms xe-0-1-0.cr1.tor1.ca.nlayer.net [69.22.142.81]
10 32 ms 29 ms 29 ms gw-google.torontointernetxchange.net [206.108.34.6]
11 28 ms 27 ms 28 ms 209.85.255.232
12 31 ms 29 ms 29 ms 72.14.236.226
13 30 ms 31 ms 69 ms 72.14.236.207
14 29 ms 29 ms 29 ms 209.85.251.88
15 34 ms 35 ms 36 ms 209.85.249.11
16 46 ms 47 ms 46 ms 209.85.243.114
17 44 ms 48 ms 44 ms 216.239.48.157
18 * * * Request timed out.
19 48 ms 47 ms 47 ms ve-in-f94.1e100.net [173.194.75.94]

BTW this is EBox cable, and it's not a good idea to post your IP

singerie3

join:2008-10-12
Saint-Constant, QC
reply to MEeastern_ca
traceroute to google.com (74.125.226.37), 30 hops max, 60 byte packets

2 10.245.243.1 (10.245.243.1) 10.643 ms 11.539 ms 11.624 ms
3 mx480-xe-1-0-1.electronicbox.net (74.116.184.73) 11.752 ms 11.706 ms 11.768 ms
4 mx480-xe-1-0-1.electronicbox.net (74.116.184.73) 12.356 ms 11.715 ms 12.436 ms
5 xe-0-0-1-613.cr1.mtl1.ca.nlayer.net (69.31.141.1) 11.500 ms * 11.563 ms
6 xe-0-1-0.cr1.tor1.ca.nlayer.net (69.22.142.81) 18.703 ms 18.036 ms 18.112 ms
7 gw-google.torontointernetxchange.net (206.108.34.6) 28.881 ms 29.651 ms 27.684 ms
8 216.239.47.114 (216.239.47.114) 32.627 ms 31.617 ms 32.683 ms
9 64.233.175.132 (64.233.175.132) 32.663 ms 32.740 ms 32.720 ms
10 yyz06s06-in-f5.1e100.net (74.125.226.37) 30.448 ms 30.288 ms 29.375 ms

traceroute to www.google.com (173.194.75.106), 30 hops max, 60 byte packets

2 10.245.243.1 (10.245.243.1) 10.744 ms 11.689 ms 11.775 ms
3 mx480-xe-1-0-1.electronicbox.net (74.116.184.73) 11.877 ms 11.807 ms 11.789 ms
4 mx480-xe-1-0-1.electronicbox.net (74.116.184.73) 11.859 ms 12.456 ms 12.540 ms
5 xe-0-0-1-613.cr1.mtl1.ca.nlayer.net (69.31.141.1) 24.257 ms * 25.166 ms
6 xe-0-1-0.cr1.tor1.ca.nlayer.net (69.22.142.81) 18.834 ms 18.100 ms 18.177 ms
7 gw-google.torontointernetxchange.net (206.108.34.6) 29.021 ms 29.942 ms 43.777 ms
8 209.85.255.232 (209.85.255.232) 32.395 ms 32.231 ms 31.193 ms
9 72.14.236.224 (72.14.236.224) 32.370 ms 72.14.236.226 (72.14.236.226) 29.182 ms 72.14.236.224 (72.14.236.224) 31.888 ms
10 209.85.252.251 (209.85.252.251) 44.012 ms 40.214 ms 39.422 ms
11 209.85.251.88 (209.85.251.88) 29.812 ms 209.85.251.35 (209.85.251.35) 26.494 ms 27.348 ms
12 209.85.249.11 (209.85.249.11) 47.646 ms 29.275 ms 31.089 ms
13 209.85.241.222 (209.85.241.222) 55.358 ms 45.503 ms 46.398 ms
14 216.239.48.157 (216.239.48.157) 46.316 ms 216.239.48.59 (216.239.48.59) 43.499 ms 216.239.48.157 (216.239.48.157) 46.457 ms
15 * * *
16 ve-in-f106.1e100.net (173.194.75.106) 45.793 ms 45.821 ms 44.555 ms


EUS
Kill cancer
Premium
join:2002-09-10
canada
reply to MEeastern_ca
said by MEeastern_ca:

Here is the same post with host names

2 erx01-mtl.electronicbox.net (74.116.184.12) 77.608 ms 131.805 ms 66.652 ms
3 mx480-ge-1-3-0.electronicbox.net (74.116.184.2) 106.683 ms 134.043 ms 66.744 ms
4 te0-5-0-6.ccr21.ymq02.atlas.cogentco.com (38.104.154.13) 97.583 ms 63.599 ms 71.568 ms
5 te0-3-0-4.mpd21.jfk02.atlas.cogentco.com (66.28.4.202) 90.309 ms
te0-6-0-6.mpd21.jfk02.atlas.cogentco.com (154.54.46.34) 89.163 ms
te0-1-0-6.mpd22.jfk02.atlas.cogentco.com (154.54.46.22) 69.706 ms
6 te0-3-0-3.mpd22.dca01.atlas.cogentco.com (154.54.5.73) 97.651 ms
te0-0-0-6.mpd22.dca01.atlas.cogentco.com (154.54.26.173) 76.182 ms
te0-0-0-2.mpd22.dca01.atlas.cogentco.com (154.54.5.253) 79.385 ms
7 te0-1-0-7.mpd22.atl01.atlas.cogentco.com (154.54.28.14) 86.470 ms
te0-0-0-6.mpd22.atl01.atlas.cogentco.com (154.54.3.65) 83.934 ms
te0-3-0-7.mpd22.atl01.atlas.cogentco.com (154.54.27.98) 86.577 ms
8 te0-2-0-7.mpd22.iah01.atlas.cogentco.com (154.54.42.221) 135.317 ms
te0-1-0-2.mpd22.iah01.atlas.cogentco.com (154.54.5.53) 130.316 ms 109.983 ms
9 te8-1.ccr01.sat01.atlas.cogentco.com (154.54.29.38) 105.614 ms
te4-3.ccr01.sat01.atlas.cogentco.com (154.54.46.6) 159.256 ms
te8-1.ccr01.sat01.atlas.cogentco.com (154.54.29.38) 147.083 ms
10 te7-2.ccr01.phx02.atlas.cogentco.com (154.54.40.161) 128.727 ms
te7-1.ccr01.phx02.atlas.cogentco.com (154.54.6.249) 134.279 ms
te8-2.ccr01.phx02.atlas.cogentco.com (154.54.83.62) 170.121 ms
11 te2-1.mag02.phx02.atlas.cogentco.com (154.54.85.86) 159.665 ms
te2-1.mag01.phx02.atlas.cogentco.com (154.54.85.82) 147.707 ms
te2-1.mag02.phx02.atlas.cogentco.com (154.54.85.86) 129.150 ms
12 vl3510.na41.b022559-0.phx02.atlas.cogentco.com (38.20.54.182) 138.673 ms
vl3810.na41.b022559-0.phx02.atlas.cogentco.com (66.28.64.210) 125.233 ms
vl3510.na41.b022559-0.phx02.atlas.cogentco.com (38.20.54.182) 201.250 ms
13 38.104.116.178 (38.104.116.178) 127.934 ms 167.034 ms 127.758 ms
14 ae2-0.io-phx1-ex8216-2.cnet.com (64.30.227.118) 194.112 ms 205.472 ms 155.706 ms
15 phx1-rb-gtm1-tron-xw-lb.cnet.com (64.30.224.103) 133.761 ms 123.222 ms 154.507 ms

That is a lot of hops.
Is every 3-letter agency scraping data now?
--
~ Project Hope ~


fromscarboro

@electronicbox.net
reply to MEeastern_ca
Tracing route to www.google.com [173.194.73.105]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 20 ms 21 ms 20 ms 74.116.184.12
3 19 ms 21 ms 20 ms 74.116.184.2
4 21 ms 20 ms 21 ms 69.31.141.1
5 29 ms 28 ms 28 ms 69.22.142.81
6 39 ms 38 ms 38 ms 206.108.34.6
7 41 ms 40 ms 40 ms 216.239.47.114
8 39 ms 38 ms 38 ms 72.14.236.224
9 41 ms 40 ms 40 ms 72.14.236.209
10 39 ms 40 ms 40 ms 209.85.251.37
11 47 ms 49 ms 61 ms 72.14.239.93
12 55 ms 56 ms 87 ms 209.85.243.114
13 56 ms 56 ms 56 ms 64.233.174.117
14 * * * Request timed out.
15 56 ms 54 ms 56 ms 173.194.73.105

Trace complete.


JoePro

join:2006-11-01
canada
reply to MEeastern_ca
You can use their looking glass server @ »lg.electronicbox.net/


creed3020
Premium
join:2006-04-26
Kitchener, ON
kudos:2
Reviews:
·TekSavvy Cable
reply to MEeastern_ca
That is some detailed routing that Cogent has going on. I only see 15 hops but many more IPs at each hop which is odd.

I see:

Montreal to New York
New York to Washington DC
DC to Atlanta
Atlanta to Idaho
Idaho to San Antonio, TX
San Antonio, TX to Phoenix
bunch of hops in Phoenix...
Guessing at this point this tracert is to cnet.com not google.com
Finally at the server/s

BrianON

join:2011-09-30
Ottawa, ON
Reviews:
·TekSavvy Cable
If you use a DNS server Google doesn't know the location of you will likely get sent to servers further away resulting in extra hops. Generally your ISP's name servers will direct you to closer Google servers. Try a tracert using the end addresses or domain names others going through fewer hops are getting directed to.

An example of using an ISP's DNS servers when on that ISP (in this case Teksavvy cable internet):

Tracing route to www.google.com [74.125.226.20]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  dlinkrouter [192.168.0.1]
  2     7 ms     7 ms     7 ms  10.125.241.1
  3    17 ms    15 ms    15 ms  69.63.242.13
  4     7 ms     7 ms     7 ms  richmond3.cable.teksavvy.com [24.52.255.74]
  5    13 ms    13 ms    13 ms  richmond1.cable.teksavvy.com [24.246.55.9]
  6    13 ms    13 ms    13 ms  72.14.212.134
  7    13 ms    13 ms    13 ms  216.239.47.114
  8    15 ms    15 ms    13 ms  72.14.233.142
  9    13 ms    13 ms    15 ms  yyz06s05-in-f20.1e100.net [74.125.226.20]
 
Trace complete.
 


LOOK at it

@videotron.ca
His copy & paste doesn't even make sense. The guy must have made some sort of copy/paste error. Look at it.

Hop #7 goes to 3 diff ip's?
Hop 8 to 3 diff IP's
Hop 9 3 diff IP's

Some of the IP's are even repeating. As if he get through, then the tracert backs-up to start over. heh

I think someone has a copy/paste problem and not a routing problem.

He likely has 15 hops to google and not the 25 to 30 or so hops he's pasting.

So my recommendation is to double check before hitting the post button Because no spell check is going to catch your double-copy/paste.

Bottom line:
No issue. The problem appears to be your copy/paste.

BrianON

join:2011-09-30
Ottawa, ON
Reviews:
·TekSavvy Cable
said by LOOK at it :

His copy & paste doesn't even make sense. The guy must have made some sort of copy/paste error. Look at it.

Hop #7 goes to 3 diff ip's?
Hop 8 to 3 diff IP's
Hop 9 3 diff IP's

Some of the IP's are even repeating. As if he get through, then the tracert backs-up to start over. heh

No that is normal if the packets take different routes.

For each hop count Tracert sends out 3 packets that will get dropped after the specified number of hops at which time the router that drops the packet should send back a notice it has done so. If the three packets take different routes they could end up being dropped by different routers.