Recent lag on just TNR

[Mr Fax Sender]

As of recently my ping has been over 100 on all TNR servers. It's only happening here, not anywhere else.

It's probably on my end, with my ISP raping my routes to Canada, but I'm just wondering if anyone else is getting this or not.

I live in Michigan, and I used to average 60 ping, if not less.

[manofphat]

Start > Run > cmd
tracert tf2pub1.northernresistance.com > tnr.txt

Post results of tnr.txt
It will be saved in the present working directory of your command prompt

[monty slick]

I've seen a few times lately where my ping could be as high as 300ms when I join and it settles down to something reasonable in ~30sec. I pretty much only play NR so don't know if it's specific to just NR.

We'll probably see in your traceroute that you're going through California or some crap.

[Mr Fax Sender]

Luke>tracert tf2pub1.northernresistance.com

Tracing route to tf2pub1.northernresistance.com [67.213.67.71]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms adsl-75-45-239-254.dsl.sfldmi.sbcglobal.net [75.45.239.254]
3 10 ms 9 ms 9 ms 67.36.65.66
4 9 ms 9 ms 9 ms bb2-p5-0.sfldmi.sbcglobal.net [151.164.98.107]
5 67 ms 68 ms 69 ms ppp-151-164-54-102.rcsntx.swbell.net [151.164.54.102]
6 69 ms 134 ms 67 ms 151.164.101.206
7 68 ms 69 ms 68 ms asn3356-level3.eqsjca.sbcglobal.net [151.164.250.138]
8 70 ms 80 ms 76 ms vlan69.csw1.SanJose1.Level3.net [4.68.18.62]
9 74 ms 71 ms 71 ms ae-82-82.ebr2.SanJose1.Level3.net [4.69.134.217]
10 85 ms 75 ms 85 ms ae-3-3.ebr1.Denver1.Level3.net [4.69.132.58]
11 84 ms 75 ms 85 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
12 68 ms 68 ms 68 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
13 69 ms 70 ms 71 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
14 83 ms 83 ms 83 ms ae-8-8.car1.Toronto2.Level3.net [4.69.140.246]
15 93 ms 92 ms 137 ms WBS-CONNECT.car1.Toronto2.Level3.net [4.59.180.94]
16 92 ms 92 ms 93 ms bb2.yyz01.3z.ca [208.68.88.2]
17 93 ms 92 ms 93 ms 67.213.67.71

Trace complete.

No wonder I'm getting such shitty ping. Here, SBC, route me through San Jose and Denver, why don't you.

[monty slick]

At hop 3 you're in Kansas Toto. You've seen that 8 puts you in California.

Could you post results for northernresistance.com and thestar.com and google.com?

[Passport]

We've been through this before: http://www.northernresistance.com/fo...901#post134901

I was being routed through SJ for over a month, as were quite a few people on this forum.

This was extremely frustrating, as you can imagine. I went through all the motions with my ISP but most people I spoke with were blatantly incompetent. When I eventually got through to someone who actually knew about routing they told me it's out of their control, which is partially true.

In my case, it eventually resolved itself. I suspect it'll be the same for you.

[Mr Fax Sender]

I hope so. This is annoying.

Is there anything I can do besides complain?

[monty slick]

Yes there is. Same thing I helped with in that thread. We'll figure out which hop seems to be sending you in the wrong direction and get you in contact with them. That's why I need those other traceroutes.

Is there something about the way I post that inspires a complete lack of confidence?

[Mr Fax Sender]

No. I forgot to do it. Why take it so personally?

Tracing route to northernresistance.com [174.120.138.58]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 11 ms 9 ms 9 ms adsl-75-45-239-254.dsl.sfldmi.sbcglobal.net [75.45.239.254]
3 10 ms 9 ms 9 ms 76.205.15.2
4 28 ms 9 ms 10 ms bb2-g10-0.sfldmi.sbcglobal.net [151.164.43.63]
5 18 ms 18 ms 41 ms 151.164.99.133
6 17 ms 16 ms 17 ms xe-11-1-0.edge4.Chicago3.Level3.net [4.68.62.37]
7 17 ms 17 ms 16 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
8 59 ms 53 ms 53 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
9 * 52 ms 53 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
10 48 ms 49 ms 53 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11 47 ms 48 ms * ae-2-70.edge4.Dallas3.Level3.net [4.69.145.77]
12 47 ms 46 ms 47 ms THE-PLANET.edge4.Dallas3.Level3.net [4.59.32.30]
13 47 ms 48 ms 47 ms 22.ff.5746.static.theplanet.com [70.87.255.34]
14 48 ms 47 ms 49 ms 82.fd.5746.static.theplanet.com [70.87.253.130]
15 47 ms 54 ms 47 ms te5-1.car12.dllstx6.theplanet.com [70.87.254.226]
16 48 ms 48 ms 48 ms 3a.8a.78ae.static.theplanet.com [174.120.138.58]

Trace complete.

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 31 ms 11 ms 10 ms adsl-75-45-239-254.dsl.sfldmi.sbcglobal.net [75.45.239.254]
3 248 ms 43 ms 35 ms 67.36.65.66
4 9 ms 10 ms 9 ms bb2-p5-0.sfldmi.sbcglobal.net [151.164.98.107]
5 16 ms 17 ms 17 ms 151.164.99.137
6 17 ms 17 ms 17 ms 72.14.218.49
7 23 ms 18 ms 28 ms 209.85.254.130
8 28 ms 27 ms 28 ms 72.14.232.141
9 28 ms 28 ms 28 ms 209.85.241.35
10 * * * Request timed out.
11 29 ms 28 ms 28 ms iw-in-f104.1e100.net [74.125.95.104]

Trace complete.

Thestar.com did nothing but timeout, so I'm not going to post it. Any other websites needed?

[monty slick]

Can you put up thestar.com anyway? Also toronto.ca

I'm trying to narrow down the problem then when we have the hop that seems to be responsible for the bad routes we'll get you a phone number or email address for the tech/admin of that router that you can contact directly to get some help, hopefully they'll talk to you and not say you have to go through your ISP's tech support.