New ISP, new place... problems...

[Exige]

I just moved to Texas (Military) and got a new ISP, Sudden Link, I've never heard of them before, but it was the only one available where I'm staying. Initially things were great, download speeds are fantastic, the service is very solid and consistent. Probably the best I've had, ever.

However, now that I'm all situated I've been getting my games up to date. Alas, I am a WoW player. This doesn't bother me too much as I don't spend too much time on the game, but I'd like to do something about it if I can.

It seems when I open the game my pings on everything, the game, vent everything spike so bad and even web pages become hard to load. I ran some pings while on WoW and while off.

While on WoW:


Tracing route to google.com [74.125.45.100]

over a maximum of 30 hops:

1 221 ms 239 ms 108 ms 192.168.1.1
2 119 ms 70 ms 175 ms 10.250.0.1
3 182 ms 170 ms 153 ms cdm-66-76-46-169.susp.suddenlink.net [66.76.46.169]
4 36 ms 15 ms 86 ms cdm-66-76-46-181.susp.suddenlink.net [66.76.46.181]
5 101 ms 55 ms 64 ms cdm-66-76-31-73.lfkn.suddenlink.net [66.76.31.73]
6 237 ms 613 ms * cdm-66-76-31-65.lfkn.suddenlink.net [66.76.31.65]
7 132 ms 120 ms 81 ms cdm-66-76-30-137.tylrtx.suddenlink.net [66.76.30.137]
8 79 ms 51 ms 61 ms cdm-66-76-30-6.tylrtx.suddenlink.net [66.76.30.6]
9 81 ms 68 ms 63 ms 66-76-232-17.tyrd.suddenlink.net [66.76.232.17]
10 65 ms 63 ms 67 ms chicosrc01-10gex2-1.tex.sta.suddenlink.net [66.76.232.10]
11 97 ms 64 ms 79 ms 74.125.48.21
12 179 ms 109 ms 99 ms 216.239.48.154
13 123 ms 98 ms 127 ms 209.85.242.215
14 98 ms 108 ms 98 ms 72.14.232.213
15 127 ms 114 ms 129 ms 209.85.253.137
16 101 ms 95 ms 86 ms yx-in-f100.1e100.net [74.125.45.100]

Trace complete.



While not on WoW
Tracing route to google.com [74.125.45.100]

over a maximum of 30 hops:


1 7 ms 3 ms 3 ms 192.168.1.1
2 20 ms 24 ms 19 ms 10.250.0.1
3 13 ms 14 ms 13 ms cdm-66-76-46-169.susp.suddenlink.net [66.76.46.169]
4 21 ms 50 ms 25 ms cdm-66-76-46-181.susp.suddenlink.net [66.76.46.181]
5 44 ms 43 ms 50 ms cdm-66-76-31-73.lfkn.suddenlink.net [66.76.31.73]
6 52 ms 42 ms 41 ms cdm-66-76-31-65.lfkn.suddenlink.net [66.76.31.65]
7 45 ms 53 ms 54 ms cdm-66-76-30-137.tylrtx.suddenlink.net [66.76.30.137]
8 50 ms 51 ms 47 ms cdm-66-76-30-6.tylrtx.suddenlink.net [66.76.30.6]
9 84 ms 93 ms 82 ms 66-76-232-17.tyrd.suddenlink.net [66.76.232.17]
10 65 ms 65 ms 62 ms chicosrc01-10gex2-1.tex.sta.suddenlink.net [66.76.232.10]
11 71 ms 67 ms 67 ms 74.125.48.21
12 82 ms 73 ms 67 ms 216.239.48.154
13 92 ms 89 ms 91 ms 72.14.239.90
14 103 ms 98 ms 106 ms 72.14.232.213
15 88 ms 94 ms 90 ms 209.85.253.133
16 82 ms 83 ms 85 ms yx-in-f100.1e100.net [74.125.45.100]



Trace complete.

Anyone have any ideas on what is happening or what I can do? I'm thinking some throttling or something might be going on.

[mage_x]

1 221 ms 239 ms 108 ms 192.168.1.1 <-- The problem looks like its on your end if you're pinging in the 200's to your router while connected to WoW. What kind of router do you have? Are you on wireless? Does it do this with any other game?

[Exige]

1 221 ms 239 ms 108 ms 192.168.1.1 <-- The problem looks like its on your end if you're pinging in the 200's to your router while connected to WoW. What kind of router do you have? Does it do this with any other game?

I have a Linksys WRT54G2, and I'm about to hop on TF2 now to see just got done updating will post results.

[Exige]

Tracing route to google.com [74.125.45.100]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 192.168.1.1

2 8 ms 11 ms 5 ms 10.250.0.1

3 9 ms 9 ms 9 ms cdm-66-76-46-169.susp.suddenlink.net [66.76.46.169]

4 18 ms 23 ms 15 ms cdm-66-76-46-181.susp.suddenlink.net [66.76.46.181]

5 35 ms 30 ms 32 ms cdm-66-76-31-73.lfkn.suddenlink.net [66.76.31.73]

6 1193 ms 30 ms 30 ms cdm-66-76-31-65.lfkn.suddenlink.net [66.76.31.65]

7 77 ms 75 ms 75 ms cdm-66-76-30-137.tylrtx.suddenlink.net [66.76.30.137]

8 34 ms 39 ms 31 ms cdm-66-76-30-6.tylrtx.suddenlink.net [66.76.30.6]

9 62 ms 59 ms 61 ms 66-76-232-17.tyrd.suddenlink.net [66.76.232.17]

10 63 ms 60 ms 61 ms chicosrc01-10gex2-1.tex.sta.suddenlink.net [66.76.232.10]

11 122 ms 120 ms 111 ms 74.125.48.21

12 105 ms 120 ms 106 ms 216.239.48.154

13 82 ms 80 ms 81 ms 72.14.239.90

14 188 ms 131 ms 90 ms 72.14.232.213

15 90 ms 93 ms 84 ms 209.85.253.133

16 83 ms 82 ms 81 ms yx-in-f100.1e100.net [74.125.45.100]



Trace complete.

That was while on TF2.

[mage_x]

Looks like WoW is overloading your router with connections or data for some reason, or at least the router is not handling what it's sending well. Are your pings to your router consistently high while on WoW (ping 192.168.1.1 -t)? I have the same router and nobody has any issue playing it on my network. Not sure what to say here other than to try bypassing your router just to make sure it's the issue.

Make sure the ports WoW requires are open and update the router's firmware, perhaps.

[Exige]

Hmm, well I'm on WoW now and everything is running as good as can be. New trace route while on WoW:



Tracing route to google.com [74.125.53.100]

over a maximum of 30 hops:



1 1 ms 2 ms 1 ms 192.168.1.1

2 34 ms 28 ms 25 ms 10.250.0.1

3 44 ms 23 ms 24 ms cdm-66-76-46-169.susp.suddenlink.net [66.76.46.169]

4 35 ms 37 ms 46 ms cdm-66-76-46-181.susp.suddenlink.net [66.76.46.181]

5 35 ms 38 ms 36 ms cdm-66-76-31-73.lfkn.suddenlink.net [66.76.31.73]

6 54 ms 52 ms 50 ms okcb-crs02.suddenlink.net [66.76.30.145]

7 72 ms 71 ms 71 ms 66-76-232-17.tyrd.suddenlink.net [66.76.232.17]

8 73 ms 70 ms 72 ms chicosrc01-10gex2-1.tex.sta.suddenlink.net [66.76.232.10]

9 73 ms 72 ms 73 ms 74.125.48.237

10 88 ms 79 ms 78 ms 216.239.48.154

11 114 ms 124 ms 127 ms 216.239.43.80

12 136 ms 174 ms 132 ms 209.85.250.126

13 141 ms 145 ms 155 ms 209.85.250.144

14 123 ms 117 ms 121 ms 216.239.48.137

15 130 ms 155 ms 117 ms 72.14.232.70

16 132 ms 123 ms 117 ms pw-in-f100.1e100.net [74.125.53.100]



Trace complete.



And this is a ping test I did to my router while on woW:



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=15ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=697ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Ping statistics for 192.168.1.1:

Packets: Sent = 62, Received = 62, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 697ms, Average = 12ms

It went pretty well. Random 697... but whatever. It was raining pretty ridiculously when I was testing before and trying to play, could that affect anything? I mean I'm on a cable connection, and as far as I know there is no Analog Dish or anything like that. Although I'm using the router wirelessly.

[mage_x]

If it's an intermittent issue there is probably something interfering with your wireless signal.

[Albaholic]

Although I'm using the router wirelessly.

Anyway to test it on ethernet to rule out the wifi as the issue?

[Exige]

Anyway to test it on ethernet to rule out the wifi as the issue?

I ordered some cat cables today, will hopefully get them by friday.

[dumpa]

I ordered some cat cables today, will hopefully get them by friday.

Also make sure your router firmware is up to date. It sure looks like it is on your end BTW.

[deed]

Also make sure your router firmware is up to date. It sure looks like it is on your end BTW.

Agreed.... although do you have more then 1 wireless connection? My router pings out on games when more then 4 users are on at a time.