O Canada! > Canadian > TekSavvy > "Teksavvy Routing Issues (Jan 24th - Present)"

"Teksavvy Routing Issues (Jan 24th - Present)"

.... you lost 1 packet out of 150, and you ping is slightly high to google?

i don't think that's a routing issue, i think that might be odd DNS on your system.

even then that's hardly a problem!

reply to captainbrew
Tracing route to 67.213.218.156 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.135.251
2 9 ms 11 ms 9 ms 10.125.251.129
3 17 ms 10 ms 14 ms 66.185.90.77
4 10 ms 14 ms 14 ms richmond2.cable.teksavvy.com [69.196.175.66]
5 43 ms 18 ms 16 ms richmond1.cable.teksavvy.com [24.246.55.9]
6 23 ms 25 ms 23 ms tge11-3.fr4.yyz.llnw.net [208.111.134.241]
7 36 ms 33 ms 38 ms tge22-4.fr3.ord.llnw.net [69.28.189.137]
8 32 ms 34 ms 31 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223
.119.63]
9 119 ms 122 ms 123 ms ae7.bbr02.eq01.chi01.networklayer.com [173.192.1
8.171]
10 135 ms 147 ms 137 ms ae0.bbr02.eq01.wdc02.networklayer.com [173.192.1
8.154]
11 46 ms 47 ms 46 ms ae1.dar01.sr01.wdc01.networklayer.com [173.192.1
8.193]
12 87 ms 44 ms 47 ms po1.fcr03.sr02.wdc01.networklayer.com [208.43.11
8.157]
13 139 ms 138 ms 140 ms 67.213.218.156

Trace complete.

reply to captainbrew

Re: "Teksavvy Routing Issues (Jan 24th - Present)"

reply to PlatooN

Re: "Teksavvy Routing Issues (Jan 24th - Present)"

reply to Anon
Umm....very helpful post.
Thanks....

I was asked to post my results here by the owner of a site I've been having buffering issues with.

reply to captainbrew
If you need further assistance from us at any point, please post your account details in Direct and we can look into it for you.

Thank you.

reply to captainbrew
Networklayer is actually SoftLayer and I'm surprised their Chicago POP has such a jump in ping. Something is wrong with their gear there.

reply to PlatooN
Windows IP Configuration

Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethern
et Controller
Physical Address. . . . . . . . . : 00-26-18-4A-40-72
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d34:1bba:c7d4:f912%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.135.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : February-03-13 8:10:04 AM
Lease Expires . . . . . . . . . . : February-09-13 2:42:00 AM
Default Gateway . . . . . . . . . : 192.168.135.251
DHCP Server . . . . . . . . . . . : 192.168.135.251
DHCPv6 IAID . . . . . . . . . . . : 285222424
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-DB-1F-33-00-26-18-4A-40-72

DNS Servers . . . . . . . . . . . : 206.248.154.22
206.248.154.170
192.168.135.251
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{86D298FC-1679-4CAD-ABFD-77CD14EF1B3A}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:4c2:3406:3fff:7a18(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::4c2:3406:3fff:7a18%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Try placing 192.168.135.251 as your ONLY dns server, and let the router/modem handle the external requests instead of bypassing it and going right to Teksavvy.

reply to PlatooN

reply to PlatooN

reply to brad
yes i did assume that .... and it COULD have made all the different with his route to google, as your DNS will resolve the closest google server to him.

considering his route was crossing half the US, it was a pretty sound assumption too.

reply to captainbrew
Of what you have posted the only thing to question is why the latency is higher than it should be. But you didn't post anything about your connection type, location, etc.. The rest of what you have posted is fine.

reply to captainbrew
I was pointed to this thread by the site as well, SoftLayer says it's a TSI problem, TSI is saying it's a SoftLayer problem - who's problem is it?

It seems like all of us on teksavvy have been having issues with this site (non-teksavvy users say everything is great...)

Tracing route to 67.213.218.156 over a maximum of 30 hops

1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 151 ms 11 ms 6 ms 206.248.154.104
3 22 ms 6 ms 6 ms 2120.ae0.bdr01.tor.packetflow.ca [69.196.136.66]

4 6 ms 6 ms 6 ms peer1.bdr02.tor.packetflow.ca [64.34.236.121]
5 16 ms 16 ms 16 ms 10ge.xe-2-0-0.chi-eqx-dis-1.peer1.net [216.187.1
14.37]
6 17 ms 44 ms 16 ms te1-7.bbr01.eq01.chi01.networklayer.com [206.223
.119.63]
7 16 ms 16 ms 16 ms ae7.bbr02.eq01.chi01.networklayer.com [173.192.1
8.171]
8 30 ms 30 ms 30 ms ae0.bbr02.eq01.wdc02.networklayer.com [173.192.1
8.154]
9 31 ms 31 ms 31 ms ae1.dar02.sr01.wdc01.networklayer.com [173.192.1
8.189]
10 32 ms 32 ms 36 ms po2.fcr03.sr02.wdc01.networklayer.com [208.43.11
8.159]
11 33 ms 32 ms 32 ms 67.213.218.156

I am on Teksavvy DSL (Bell). Also going through chicago to washington for whatever reason.

At this point I thought it was Soft Layer, but why on earth are our routes going to chicago THEN to washington? Please advise.