dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
302

hw
@198.84.207.x

hw

Anon

Routing strangeness

Is anyone else seeing intermittent mis-routing? Like google.com routing to a Cogeco landing page. I'm on TSI/Rogers and using TSI's own DNS.

MBP:sbin user$ sudo ./mtr -c 20 -w -r google.com
Password:
HOST: MBP.local Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.0.1.1 0.0% 20 47.0 16.5 0.9 184.8 44.2
2.|-- 10.124.6.129 0.0% 20 145.1 35.6 7.7 156.7 49.9
3.|-- 24.156.150.57 0.0% 20 240.8 45.3 17.6 240.8 58.6
4.|-- so-5-0-3.gw02.bloor.phub.net.cable.rogers.com 0.0% 20 112.2 45.2 18.2 184.8 49.7
5.|-- ae1_2150-bdr04-tor.teksavvy.com 0.0% 20 62.4 36.7 19.3 170.2 37.1
6.|-- gw-cogeco.torontointernetxchange.net 0.0% 20 149.8 54.9 20.7 159.7 52.9
7.|-- d226-6-22.home.cgocable.net 0.0% 20 26.5 38.0 22.4 241.0 47.9
8.|-- d226-16-158.home.cgocable.net 5.0% 20 281.8 53.1 22.6 281.8 68.9

noyb8
join:2004-04-20
canada

noyb8

Member

»extratorrent.cc/article/ ··· ted.html

read this little tid bit!!!! internet crashed in europe
DigitalRain
join:2013-03-16

DigitalRain

Member

said by noyb8:

»extratorrent.cc/article/ ··· ted.html

read this little tid bit!!!! internet crashed in europe

Charles de Gaulle and Vladimir Lenin are both laughing from beyond the grave about now.
dra6o0n
join:2011-08-15
Mississauga, ON

3 edits

dra6o0n to hw

Member

to hw
Me trying to connect to a friend in Michigan is odd because for some reason....

1 1 ms 1 ms 19 ms 192.168.1.1
2 3 ms 3 ms 3 ms mynetwork.home [192.168.2.1]
3 39 ms 32 ms 21 ms 206.248.154.104
4 20 ms 20 ms 19 ms ae2_2110-bdr03-tor.teksavvy.com [69.196.136.41]
5 30 ms 25 ms 25 ms 10ge15-2.core1.tor1.he.net [209.51.184.253]
6 35 ms 29 ms 30 ms 100ge13-1.core1.chi1.he.net [184.105.80.5]
7 * * * Request timed out.
8 31 ms 31 ms 30 ms ae2---0.cor02.chcg.il.frontiernet.net [74.40.4.141]
9 37 ms 36 ms 35 ms ae0---0.car01.mskg.mi.frontiernet.net [74.40.2.122]
10 49 ms 47 ms 48 ms ae0---0.adr02.mskg.mi.frontiernet.net [74.42.151.114]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 ^C

At #5, my packet went to New Jersey.
At #6, packet went to california.
at #7 it timed out.
At #8 it flew to Kansas
At #9 it went to some unknown state or location
At #10 it went to new york...
Then lots of time outs.
In the end its circling the entire USA just to connect to someone to the south east of Ontario in Michigan?

EDIT: Oh look, when i further want to see the locations of those ip again it shows unknown.

Yes I understand that my friend lives in a rural area south of Kalamazoo, but that doesn't mean it's several times slower in response in regards to latency when it comes to connecting to him.

Edit: speed test to Kalamazoo showed 42ms, so reaching his computer won't surpass 90ms as the line to him is weaker in general and frontier covers Michigan.

I used tracert services to tracert my IP...
For some reason the Texas server traveled to Ontario the immediately plows past Toronto and ends in Ottawa.
Every single server even Montreal had to go to Toronto the Ottawa.
The UK went to new York then Toronto then Ottawa.

So my IP tracert to my friend was strange because I'm given IP to route to Ottawa first then to elsewhere.