High Latency, and terrible performance

[Exige]

So, I play World of Warcraft, and randomly my ping spikes to ridiculous latencies, so I got on the Tech boards and started asking around. They had me run a Tracert. I ran it and posted my findings. A bunch of members, (No reps from Blizzard gave me any help.) told me that hop #2 was ridiculous and that I needed to contact my ISP.

I said okay, I honestly figured it was going to be my ISP's problem. So, I asked them what the deal with the numbers was, what hop #2 meant and whatnot because I don't really understand any of this. Basically all I get is that high millisecond pings are obviously bad. (Networking is not my strong suit...)

Here's a copy of my tracert:

Tracing route to us.logon.worldofwarcraft.com [12.129.232.111]

over a maximum of 30 hops:



1 1 ms <1 ms 1 ms 192.168.1.1

2 505 ms 139 ms 512 ms 1.234.171.66.subscriber.vzavenue.net [66.171.234.1]

3 485 ms 72 ms 42 ms 1.117.171.66.subscriber.vzavenue.net [66.171.117.1]

4 848 ms 1075 ms 107 ms POS5-2.GW5.SJC1.ALTER.NET [63.65.131.209]

5 1187 ms 976 ms 1280 ms 0.so-0-2-0.XL1.SJC1.ALTER.NET [152.63.54.18]

6 778 ms 449 ms 100 ms 0.so-2-0-0.XL1.SJC7.ALTER.NET [152.63.49.45]

7 1308 ms 1749 ms 699 ms 0.so-6-0-0.BR1.SJC7.ALTER.NET [152.63.48.249]

8 819 ms 589 ms 340 ms uu-gw.sffca.ip.att.net [192.205.32.73]

9 511 ms 532 ms 1289 ms tbr1.sffca.ip.att.net [12.123.13.189]

10 307 ms 836 ms 101 ms cr1.sffca.ip.att.net [12.122.19.33]

11 836 ms 773 ms 1201 ms cr1.la2ca.ip.att.net [12.122.3.122]

12 364 ms 607 ms 265 ms tbr1.la2ca.ip.att.net [12.122.19.162]

13 81 ms 60 ms 91 ms 12.127.3.185

14 172 ms 72 ms 96 ms 12.122.255.74

15 872 ms 351 ms 118 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

16 * * * Request timed out.

So, I'm obviously going to call up my ISP and get angry, because it's been like this for about seven months. The issue I have is the consistency, it changes quite literally every single day. One day, I'll have a nice 140ms steady the entire day. Sometimes even for a couple days. Then it just goes to hell, skyrocketing and spiking between 1000-6000.

It's just a game, but now it's begun to effect my work too, which is extremely frustrating.

So, I'm going to call up my ISP but my problem is I have absolutely no idea what to say other than, "My internet is slow, and sucky, and completely inconsistent, and I ran a tracert, and it has bad numbers."

So, if anyone could help me out with the Tracert, and as to what it means, and what the numbers are and stuff, that'd be awesome. Thanks for the help!

 

[Rilian]

alright HOP #2, is either your ISP's DNS server or your ISP period, what they are talking about is the fact that your latency is really high between you and your ISP, which in about 75% of cases should be sub 100 numbers, theres no reason the connection between you and your ISP should be that slow... unless your using cable with ALOT of people bogging down the node you run on, but your lagging from the start line... i have damn near 1 of the worst ISP's in the world, and hop #2 is only 70ms... =P so you can see where your problem is... ask a friend or someone with the same ISP as you to do a tracert, someone who doesnt neccessarily live on the same block as you... then ask a neighbor to do a tracert, it could be your "node" being bogged way down from a bunch of filesharers, if this is so you actually have a reason to complain.... but is this DSL or cable or what? because DSL lines are guaranteed bandwidth, cable however is not, just a couple things to think about.

 

[dark_15]

Run that same tracert again, but add a -n to the command. So the final command would be:

tracert -n <ip address>

This will help rule out the DNS server being slow.

Also, what is your router's MTU configuration?

 

[Ebola]

Complain all you want. Your ISP does not care. And maybe you should stop playing if it effects your life.

Only bad things happen when you adjust MTU

 

[Exige]

alright HOP #2, is either your ISP's DNS server or your ISP period, what they are talking about is the fact that your latency is really high between you and your ISP, which in about 75% of cases should be sub 100 numbers, theres no reason the connection between you and your ISP should be that slow... unless your using cable with ALOT of people bogging down the node you run on, but your lagging from the start line... i have damn near 1 of the worst ISP's in the world, and hop #2 is only 70ms... =P so you can see where your problem is... ask a friend or someone with the same ISP as you to do a tracert, someone who doesnt neccessarily live on the same block as you... then ask a neighbor to do a tracert, it could be your "node" being bogged way down from a bunch of filesharers, if this is so you actually have a reason to complain.... but is this DSL or cable or what? because DSL lines are guaranteed bandwidth, cable however is not, just a couple things to think about.

Alright, I'll get a couple of my friends together. But my internet is actually DSL, and not Cable.

Run that same tracert again, but add a -n to the command. So the final command would be:

tracert -n <ip address>

This will help rule out the DNS server being slow.

Also, what is your router's MTU configuration?

I ran the tracer like that and I got an error-

-n is not a valid command option.



Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name



Options:

-d Do not resolve addresses to hostnames.

-h maximum_hops Maximum number of hops to search for target.

-j host-list Loose source route along host-list.

-w timeout Wait timeout milliseconds for each reply.

As for the MTU config, I don't know how to figure that out. I'll be consulting my friend Google, or wait for a response telling me how to do it. To both of you, dark_15 and Rilian, really thank you a lot for helping me I appreciate it. Can't tell you how many times I have an issue like this (rarely) and get no help.

Complain all you want. Your ISP does not care. And maybe you should stop playing if it effects your life.

Only bad things happen when you adjust MTU

As for you, I went back and read what I wrote and worded that terrible. This is what I meant to say: "It's just a game, but the internet issues have begun to effect my work as well."

If you've got nothing useful to say, then please feel free not to post.

Thanks

 

[Exige]

I've been google searching around to figure out how to find out my MTU configurations and one forum suggested to someone to find the latest Firmware upgrade, so I went and found mine and upgraded it, but really no luck. Wasn't much of an upgrade either heh.

 

[Exige]

I got it:

MTU: 1500

 

[RJARRRPCGP]

Rearrange the cables and unplug the router then plug the router back in and *do that with the PC shut down.* (otherwise Windows may complain about being denied an IP address)

You may be having receive errors.

 

[Exige]

Rearrange the cables and unplug the router then plug the router back in and do that with the PC shut down. (otherwise Windows may complain about being denied an IP)

Sure thing.

 

[Exige]

Rearrange the cables and unplug the router then plug the router back in and *do that with the PC shut down.* (otherwise Windows may complain about being denied an IP address)

You may be having receive errors.

No luck, nothing happened.

 

[dark_15]

Whoops - I'm sorry about that. In OSX we use -n

-d will do the same thing. Try that and post the results.

As for the MTU, are you using DSL? If so, then try dropping the MTU (on the router) to 1492. Also, if you have the make and model of your router that will help out as well.

 

[Exige]

Whoops - I'm sorry about that. In OSX we use -n

-d will do the same thing. Try that and post the results.

As for the MTU, are you using DSL? If so, then try dropping the MTU (on the router) to 1492. Also, if you have the make and model of your router that will help out as well.

Here are the results:

Tracing route to us.logon.worldofwarcraft.com [12.129.224.110]

over a maximum of 30 hops:



1 1 ms <1 ms <1 ms 192.168.1.1

2 384 ms 322 ms 336 ms 66.171.234.1

3 184 ms 279 ms 245 ms 66.171.117.1

4 507 ms 407 ms 552 ms 63.65.131.209

5 118 ms 114 ms 162 ms 152.63.54.18

6 315 ms 253 ms 183 ms 152.63.49.45

7 319 ms 620 ms 730 ms 152.63.48.249

8 60 ms 29 ms 36 ms 192.205.32.73

9 866 ms 287 ms 656 ms 12.123.13.186

10 538 ms 366 ms 318 ms 12.122.19.89

11 211 ms 395 ms 210 ms 12.122.3.122

12 268 ms 199 ms 142 ms 12.122.19.130

13 238 ms 203 ms 103 ms 12.127.3.185

14 308 ms 145 ms 240 ms 12.122.255.74

15 482 ms 357 ms 204 ms 12.129.193.246

16 * * * Request timed out.

My internet is better than it was last night. Not much, but a little, like I said it varies a ton.

We just got off the phone with our ISP, we got them to send a technician out, they said if the problem was actually with them than they wouldn't charge us a dime, I think they expect that I have no idea what I'm talking about, like any company. Then again, I don't know a whole lot about this, but I definitely feel like this is their problem.

Changing the MTU configuration now.

Router = Linksys WRT54GS Wireless (I'm plugged in. And no, no one is on the network unexpectedly, it's just me, my wife, my laptop, and my 360) I just upgraded the Firmware like I said before, so that's at the highest possible.

Thanks for helping me out again, really appreciating this!

 

[dark_15]

OK, the high latency on the 2nd hop is indicative of a problem, and not on your end.

Try this:
run a "ping -t" for about a minute each to the first three hops on that traceroute. Let's see if one of those is dropping packets somewhere along the line. Post the summaries here.

 

[Exige]

OK, the high latency on the 2nd hop is indicative of a problem, and not on your end.

Try this:
run a "ping -t" for about a minute each to the first three hops on that traceroute. Let's see if one of those is dropping packets somewhere along the line. Post the summaries here.

First Hop:

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<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<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<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<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<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<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<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<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<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<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<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<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<1ms TTL=64



Ping statistics for 192.168.1.1:

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

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms

Ping from Hop 2:

Pinging 66.171.234.1 with 32 bytes of data:



Reply from 66.171.234.1: bytes=32 time=7ms TTL=254

Reply from 66.171.234.1: bytes=32 time=94ms TTL=254

Reply from 66.171.234.1: bytes=32 time=98ms TTL=254

Reply from 66.171.234.1: bytes=32 time=157ms TTL=254

Reply from 66.171.234.1: bytes=32 time=188ms TTL=254

Reply from 66.171.234.1: bytes=32 time=277ms TTL=254

Reply from 66.171.234.1: bytes=32 time=223ms TTL=254

Reply from 66.171.234.1: bytes=32 time=63ms TTL=254

Reply from 66.171.234.1: bytes=32 time=151ms TTL=254

Reply from 66.171.234.1: bytes=32 time=205ms TTL=254

Reply from 66.171.234.1: bytes=32 time=52ms TTL=254

Reply from 66.171.234.1: bytes=32 time=359ms TTL=254

Reply from 66.171.234.1: bytes=32 time=34ms TTL=254

Reply from 66.171.234.1: bytes=32 time=124ms TTL=254

Reply from 66.171.234.1: bytes=32 time=94ms TTL=254

Reply from 66.171.234.1: bytes=32 time=436ms TTL=254

Reply from 66.171.234.1: bytes=32 time=616ms TTL=254

Reply from 66.171.234.1: bytes=32 time=424ms TTL=254

Reply from 66.171.234.1: bytes=32 time=345ms TTL=254

Reply from 66.171.234.1: bytes=32 time=620ms TTL=254

Reply from 66.171.234.1: bytes=32 time=341ms TTL=254

Reply from 66.171.234.1: bytes=32 time=242ms TTL=254

Reply from 66.171.234.1: bytes=32 time=120ms TTL=254

Reply from 66.171.234.1: bytes=32 time=146ms TTL=254

Reply from 66.171.234.1: bytes=32 time=18ms TTL=254

Reply from 66.171.234.1: bytes=32 time=43ms TTL=254

Reply from 66.171.234.1: bytes=32 time=432ms TTL=254

Reply from 66.171.234.1: bytes=32 time=321ms TTL=254

Reply from 66.171.234.1: bytes=32 time=296ms TTL=254

Reply from 66.171.234.1: bytes=32 time=87ms TTL=254

Reply from 66.171.234.1: bytes=32 time=141ms TTL=254

Reply from 66.171.234.1: bytes=32 time=77ms TTL=254

Reply from 66.171.234.1: bytes=32 time=49ms TTL=254

Reply from 66.171.234.1: bytes=32 time=146ms TTL=254

Reply from 66.171.234.1: bytes=32 time=155ms TTL=254

Reply from 66.171.234.1: bytes=32 time=209ms TTL=254

Reply from 66.171.234.1: bytes=32 time=85ms TTL=254

Reply from 66.171.234.1: bytes=32 time=44ms TTL=254

Reply from 66.171.234.1: bytes=32 time=173ms TTL=254

Reply from 66.171.234.1: bytes=32 time=23ms TTL=254

Reply from 66.171.234.1: bytes=32 time=235ms TTL=254

Reply from 66.171.234.1: bytes=32 time=271ms TTL=254

Reply from 66.171.234.1: bytes=32 time=190ms TTL=254

Reply from 66.171.234.1: bytes=32 time=19ms TTL=254

Reply from 66.171.234.1: bytes=32 time=193ms TTL=254

Reply from 66.171.234.1: bytes=32 time=113ms TTL=254

Reply from 66.171.234.1: bytes=32 time=103ms TTL=254

Reply from 66.171.234.1: bytes=32 time=209ms TTL=254

Reply from 66.171.234.1: bytes=32 time=296ms TTL=254

Reply from 66.171.234.1: bytes=32 time=64ms TTL=254

Reply from 66.171.234.1: bytes=32 time=191ms TTL=254

Reply from 66.171.234.1: bytes=32 time=30ms TTL=254

Reply from 66.171.234.1: bytes=32 time=54ms TTL=254

Reply from 66.171.234.1: bytes=32 time=33ms TTL=254

Reply from 66.171.234.1: bytes=32 time=154ms TTL=254

Reply from 66.171.234.1: bytes=32 time=411ms TTL=254

Reply from 66.171.234.1: bytes=32 time=36ms TTL=254

Reply from 66.171.234.1: bytes=32 time=155ms TTL=254

Reply from 66.171.234.1: bytes=32 time=168ms TTL=254

Reply from 66.171.234.1: bytes=32 time=56ms TTL=254

Reply from 66.171.234.1: bytes=32 time=214ms TTL=254

Reply from 66.171.234.1: bytes=32 time=217ms TTL=254

Reply from 66.171.234.1: bytes=32 time=111ms TTL=254

Reply from 66.171.234.1: bytes=32 time=88ms TTL=254

Reply from 66.171.234.1: bytes=32 time=233ms TTL=254

Reply from 66.171.234.1: bytes=32 time=223ms TTL=254

Reply from 66.171.234.1: bytes=32 time=67ms TTL=254

Reply from 66.171.234.1: bytes=32 time=1002ms TTL=254

Reply from 66.171.234.1: bytes=32 time=172ms TTL=254

Reply from 66.171.234.1: bytes=32 time=202ms TTL=254

Reply from 66.171.234.1: bytes=32 time=60ms TTL=254

Reply from 66.171.234.1: bytes=32 time=332ms TTL=254

Reply from 66.171.234.1: bytes=32 time=85ms TTL=254

Reply from 66.171.234.1: bytes=32 time=53ms TTL=254

Reply from 66.171.234.1: bytes=32 time=174ms TTL=254

Reply from 66.171.234.1: bytes=32 time=79ms TTL=254

Reply from 66.171.234.1: bytes=32 time=293ms TTL=254

Reply from 66.171.234.1: bytes=32 time=21ms TTL=254

Reply from 66.171.234.1: bytes=32 time=154ms TTL=254

Reply from 66.171.234.1: bytes=32 time=62ms TTL=254

Reply from 66.171.234.1: bytes=32 time=112ms TTL=254

Reply from 66.171.234.1: bytes=32 time=232ms TTL=254

Reply from 66.171.234.1: bytes=32 time=65ms TTL=254

Reply from 66.171.234.1: bytes=32 time=419ms TTL=254

Reply from 66.171.234.1: bytes=32 time=422ms TTL=254

Reply from 66.171.234.1: bytes=32 time=185ms TTL=254

Reply from 66.171.234.1: bytes=32 time=197ms TTL=254

Reply from 66.171.234.1: bytes=32 time=86ms TTL=254

Reply from 66.171.234.1: bytes=32 time=313ms TTL=254

Reply from 66.171.234.1: bytes=32 time=44ms TTL=254

Reply from 66.171.234.1: bytes=32 time=263ms TTL=254

Reply from 66.171.234.1: bytes=32 time=291ms TTL=254

Reply from 66.171.234.1: bytes=32 time=276ms TTL=254

Reply from 66.171.234.1: bytes=32 time=19ms TTL=254

Reply from 66.171.234.1: bytes=32 time=61ms TTL=254

Reply from 66.171.234.1: bytes=32 time=185ms TTL=254

Reply from 66.171.234.1: bytes=32 time=264ms TTL=254

Reply from 66.171.234.1: bytes=32 time=64ms TTL=254

Reply from 66.171.234.1: bytes=32 time=143ms TTL=254

Reply from 66.171.234.1: bytes=32 time=268ms TTL=254

Reply from 66.171.234.1: bytes=32 time=62ms TTL=254

Reply from 66.171.234.1: bytes=32 time=139ms TTL=254

Reply from 66.171.234.1: bytes=32 time=53ms TTL=254

Reply from 66.171.234.1: bytes=32 time=126ms TTL=254

Reply from 66.171.234.1: bytes=32 time=595ms TTL=254



Ping statistics for 66.171.234.1:

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

Approximate round trip times in milli-seconds:

Minimum = 7ms, Maximum = 1002ms, Average = 184ms

Ping from Hop3:

Pinging 66.171.117.1 with 32 bytes of data:



Reply from 66.171.117.1: bytes=32 time=369ms TTL=253

Reply from 66.171.117.1: bytes=32 time=218ms TTL=253

Reply from 66.171.117.1: bytes=32 time=131ms TTL=253

Reply from 66.171.117.1: bytes=32 time=19ms TTL=253

Reply from 66.171.117.1: bytes=32 time=202ms TTL=253

Reply from 66.171.117.1: bytes=32 time=173ms TTL=253

Reply from 66.171.117.1: bytes=32 time=160ms TTL=253

Reply from 66.171.117.1: bytes=32 time=245ms TTL=253

Reply from 66.171.117.1: bytes=32 time=131ms TTL=253

Reply from 66.171.117.1: bytes=32 time=159ms TTL=253

Reply from 66.171.117.1: bytes=32 time=110ms TTL=253

Reply from 66.171.117.1: bytes=32 time=170ms TTL=253

Reply from 66.171.117.1: bytes=32 time=35ms TTL=253

Reply from 66.171.117.1: bytes=32 time=30ms TTL=253

Reply from 66.171.117.1: bytes=32 time=401ms TTL=253

Reply from 66.171.117.1: bytes=32 time=133ms TTL=253

Reply from 66.171.117.1: bytes=32 time=87ms TTL=253

Reply from 66.171.117.1: bytes=32 time=227ms TTL=253

Reply from 66.171.117.1: bytes=32 time=23ms TTL=253

Reply from 66.171.117.1: bytes=32 time=26ms TTL=253

Reply from 66.171.117.1: bytes=32 time=266ms TTL=253

Reply from 66.171.117.1: bytes=32 time=132ms TTL=253

Reply from 66.171.117.1: bytes=32 time=97ms TTL=253

Reply from 66.171.117.1: bytes=32 time=187ms TTL=253

Reply from 66.171.117.1: bytes=32 time=257ms TTL=253

Reply from 66.171.117.1: bytes=32 time=105ms TTL=253

Reply from 66.171.117.1: bytes=32 time=770ms TTL=253

Reply from 66.171.117.1: bytes=32 time=298ms TTL=253

Reply from 66.171.117.1: bytes=32 time=224ms TTL=253

Reply from 66.171.117.1: bytes=32 time=47ms TTL=253

Reply from 66.171.117.1: bytes=32 time=143ms TTL=253

Reply from 66.171.117.1: bytes=32 time=120ms TTL=253

Reply from 66.171.117.1: bytes=32 time=91ms TTL=253

Reply from 66.171.117.1: bytes=32 time=112ms TTL=253

Reply from 66.171.117.1: bytes=32 time=195ms TTL=253

Reply from 66.171.117.1: bytes=32 time=144ms TTL=253

Reply from 66.171.117.1: bytes=32 time=97ms TTL=253

Reply from 66.171.117.1: bytes=32 time=117ms TTL=253

Reply from 66.171.117.1: bytes=32 time=19ms TTL=253

Reply from 66.171.117.1: bytes=32 time=21ms TTL=253

Reply from 66.171.117.1: bytes=32 time=214ms TTL=253

Reply from 66.171.117.1: bytes=32 time=27ms TTL=253

Reply from 66.171.117.1: bytes=32 time=403ms TTL=253

Reply from 66.171.117.1: bytes=32 time=544ms TTL=253

Reply from 66.171.117.1: bytes=32 time=162ms TTL=253

Reply from 66.171.117.1: bytes=32 time=164ms TTL=253

Reply from 66.171.117.1: bytes=32 time=72ms TTL=253

Reply from 66.171.117.1: bytes=32 time=253ms TTL=253

Reply from 66.171.117.1: bytes=32 time=30ms TTL=253

Reply from 66.171.117.1: bytes=32 time=173ms TTL=253

Reply from 66.171.117.1: bytes=32 time=233ms TTL=253

Reply from 66.171.117.1: bytes=32 time=86ms TTL=253

Reply from 66.171.117.1: bytes=32 time=48ms TTL=253

Reply from 66.171.117.1: bytes=32 time=18ms TTL=253

Reply from 66.171.117.1: bytes=32 time=26ms TTL=253

Reply from 66.171.117.1: bytes=32 time=267ms TTL=253

Reply from 66.171.117.1: bytes=32 time=196ms TTL=253

Reply from 66.171.117.1: bytes=32 time=241ms TTL=253

Reply from 66.171.117.1: bytes=32 time=314ms TTL=253

Reply from 66.171.117.1: bytes=32 time=64ms TTL=253

Reply from 66.171.117.1: bytes=32 time=207ms TTL=253

Reply from 66.171.117.1: bytes=32 time=76ms TTL=253

Reply from 66.171.117.1: bytes=32 time=91ms TTL=253

Reply from 66.171.117.1: bytes=32 time=313ms TTL=253

Reply from 66.171.117.1: bytes=32 time=113ms TTL=253

Reply from 66.171.117.1: bytes=32 time=117ms TTL=253

Reply from 66.171.117.1: bytes=32 time=68ms TTL=253

Reply from 66.171.117.1: bytes=32 time=96ms TTL=253

Reply from 66.171.117.1: bytes=32 time=273ms TTL=253

Reply from 66.171.117.1: bytes=32 time=248ms TTL=253

Reply from 66.171.117.1: bytes=32 time=570ms TTL=253

Reply from 66.171.117.1: bytes=32 time=647ms TTL=253



Ping statistics for 66.171.117.1:

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

Approximate round trip times in milli-seconds:

Minimum = 18ms, Maximum = 770ms, Average = 178ms

 

[Exige]

No packets lost =/

 

[dark_15]

No packets lost =/

While that is true, that second hop is definitely an issue:

Ping statistics for 66.171.234.1:
Packets: Sent = 105, Received = 105, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 1002ms, Average = 184ms

That indicates a problem either with the line or the router at the end of that hop. You should be having response times in the 7-10ms range consistently, and definitely not the max ping of 1 second. Since we're not seeing packet loss, I am going to guess that the line is not at fault here.

Have you tried bypassing the router, and trying the same ping to the second hop? If not, do that and let's see the result.

 

[Exige]

While that is true, that second hop is definitely an issue:

Ping statistics for 66.171.234.1:
Packets: Sent = 105, Received = 105, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 1002ms, Average = 184ms

That indicates a problem either with the line or the router at the end of that hop. You should be having response times in the 7-10ms range consistently, and definitely not the max ping of 1 second. Since we're not seeing packet loss, I am going to guess that the line is not at fault here.

Have you tried bypassing the router, and trying the same ping to the second hop? If not, do that and let's see the result.

So I tried plugging in directly to the modem, but couldn't get a connection. I fiddled around with the network settings, even set up a new connection. I went over to the modem and the ethernet light didn't light up. So, I unplugged it, and plugged the router back in, it lit up. I unplugged it, and plugged my computer back in directly. No such luck, I've never had this issue before, I've always just been able to connect almost instantly, sometimes I had to change the network settings. Any suggestions?

 

[dark_15]

So I tried plugging in directly to the modem, but couldn't get a connection. I fiddled around with the network settings, even set up a new connection. I went over to the modem and the ethernet light didn't light up. So, I unplugged it, and plugged the router back in, it lit up. I unplugged it, and plugged my computer back in directly. No such luck, I've never had this issue before, I've always just been able to connect almost instantly, sometimes I had to change the network settings. Any suggestions?

Connect your PC in directly, set it to DHCP, and then reboot the modem. See if you can get an address and get out to the internet.

EDIT: Also try a different cable as well.

 

[Exige]

Connect your PC in directly, set it to DHCP, and then reboot the modem. See if you can get an address and get out to the internet.

EDIT: Also try a different cable as well.

Tracing route to us.logon.worldofwarcraft.com [12.129.232.114]

over a maximum of 30 hops:


1 486 ms 1038 ms 808 ms 1.234.171.66.subscriber.vzavenue.net [66.171.234.1]

2 29 ms 48 ms 19 ms 1.117.171.66.subscriber.vzavenue.net [66.171.117.1]

3 11 ms 12 ms 9 ms POS5-2.GW5.SJC1.ALTER.NET [63.65.131.209]

4 2331 ms 1291 ms 1049 ms 515.ATM2-0.XR2.SJC1.ALTER.NET [152.63.54.22]

5 1076 ms 2540 ms 847 ms 0.so-3-0-0.XL1.SJC7.ALTER.NET [152.63.15.190]

6 161 ms 54 ms 88 ms 0.so-7-0-0.BR1.SJC7.ALTER.NET [152.63.48.253]

7 448 ms 1085 ms 1587 ms ggr2-p3133.sffca.ip.att.net [192.205.33.197]

8 423 ms 266 ms 1868 ms tbr2.sffca.ip.att.net [12.123.13.186]

9 1266 ms 299 ms 113 ms cr1.sffca.ip.att.net [12.122.19.89]

10 615 ms 2282 ms 838 ms cr1.la2ca.ip.att.net [12.122.3.122]

11 1425 ms 876 ms 1327 ms tbr1.la2ca.ip.att.net [12.122.19.138]

12 1862 ms 348 ms 1495 ms 12.127.3.185

13 2746 ms 755 ms 57 ms 12.122.255.74

14 1168 ms 545 ms 119 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.





Trace complete.

 

[dark_15]

OK, that rules out the WRT as well. On another note when I ping that next hop on the traceroute, here is my results:

--- 66.171.234.1 ping statistics ---
21 packets transmitted, 21 packets received, 0% packet loss
round-trip min/avg/max/stddev = 91.204/96.512/106.566/3.575 ms

Notice the difference? I'm about 15 hops away, and my latency is still very low. I don't think it's the next hop; rather it's your modem, the phone line it is connected to, or the link between your home and the DSLAM.

If you really want to investigate it further, you could go out and connect directly to your demarc with the modem and a laptop to test further. Have you noticed any static in your phone calls?

If not, call up your ISP (I'm assuming it's verizon), and tell them that you connected a PC directly to the modem, and the default gateway (66.171.234.1) has extremely high latency of about 1000 ms. Ask them to check that router, and to perform intrusive testing on your line. See if they can set a monitor on your line as well to check for errors.