O Canada! > Canadian > TekSavvy > TekSavvy - glorified reseller, not ISP

reply to elwoodblues

Re: TekSavvy - glorified reseller, not ISP

get him to do a traceroute and you do the same, try to see if you have the same node.

can you ask him to PM us his info so we can look at what's going on?

it could be all sorts of things.. could be wiring, could be a router, could be PC issues. Maybe he's surfing places you're not and those places are slower.

There is nothing but speculation that can be said based on this info. Something is going on. What it is, is unknown.
--
Marc - CEO/TekSavvy

He's not on here, but I'll copy your post and email it to him.

reply to elwoodblues
That being said, this issue of two homes with totally different experiences despite presumably being on the same node has come up before, and it's interesting. No matter what the two services are, there should be no difference so long as they're on the same profile and there's no POI congestion or weird downstream issues. I'd love to hear what, if anything, comes out of the situation elwoodblues describes.

reply to The Mongoose

reply to elwoodblues
Post a traceroute to say google.ca, we will see if you're on McNicol and we should also be able to see what Node you're on.

Mongoose, can you do it too for fun?
--
Marc - CEO/TekSavvy

I'm on Dupont so not sure I'm of any use in troubleshooting this one, but here's mine:

Tracing route to google.com [74.125.225.32]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms CISCOE4200V2 [192.168.1.1]
2 8 ms 9 ms 10 ms 10.126.211.129
3 16 ms 18 ms 11 ms 24.156.150.9
4 18 ms 17 ms 8 ms dupont.cable.teksavvy.com [24.52.255.130]
5 11 ms 50 ms 11 ms dupont2.cable.teksavvy.com [24.246.55.117]
6 10 ms 9 ms 10 ms 72.14.212.134
7 17 ms 10 ms 12 ms 216.239.47.114
8 26 ms 26 ms 26 ms 216.239.46.160
9 27 ms 26 ms 28 ms 72.14.237.109
10 25 ms 26 ms 25 ms 209.85.250.28
11 26 ms 26 ms 28 ms ord08s06-in-f0.1e100.net [74.125.225.32]

Trace complete.

reply to The Mongoose

reply to TSI Marc
Tracing route to google.ca [74.125.133.94]
over a maximum of 30 hops:

1 1 ms 1 ms 1ms 192.168.1.1
2 7 ms 14 ms 29 ms 10.140.8.129
3 15 ms 13 ms 20 ms 66.185.89.21
4 15 ms 14 ms 23 ms 24.153.5.217
5 55 ms 48 ms 47 ms gw-google.torontointernetxchange.net [206.108.34.6]
6 64 ms 45 ms 45 ms 216.239.47.114
7 50 ms 62 ms 62 ms 216.239.46.160
8 60 ms 73 ms 53 ms 209.85.241.22
9 73 ms 59 ms 78 ms 209.85.241.29
10 * * * Request timed out.
11 81 ms 63 ms 59 ms ia-in-f94.1e100.net [74.125.133.94]
--
No, I didn't. Honest... I ran out of gas. I... I had a flat tire. I didn't have enough money for cab fare. My tux didn't come back from the cleaners. An old friend came in from out of town. Someone stole my car. There was an earthquake.......

What else would it be? I live in Scarberia ( the most SW) besides comstock, the next POI would be Bloor (I don't see going up to york)

Seriously though, OP has every right to raise a stink in public and try to get his problem solved. These direct forums can be nice for getting things done, but they also serve to try to shove problems off the public's radar. I think that's the real reason they exist, to try to head off the vocal, knowledgeable user with a problem that frequents these types of forums.

I said in another thread, and I'll say it again, TekSavvy's business model is broken. You can't be the the customer-facing entity whose business depends on the goodwill of a hostile oligopoly like Rogers or Bell or any of the other big telecoms. They can, and will, screw with you relentlessly and there's no fixing it unless you can get the CRTC to put firm rules in place to help solve these types of issues.

I know TSI people have argued that Rogers should see them as a great business partner that makes them lots of money. That might be true, but I can tell you with certainty that Rogers will never see it that way. They want those customers for themselves and TekSavvy is nothing more than a regulator-imposed nuisance.