Child Item

Site Totals

61434 Questions Answered 270 Categories

Getting terrible lag while playing an online game

I play a game called World of Warcraft (WoW for short) and have been getting terrible, high ping lag lately. Here is some information you might need:

INFO

OS: Windows 7
Firewall: Windows Firewall
Anti-virus: MSE (Microsoft Security Essentials
Verizon DSL; Actiontec model: GT784WNV
Wired DSL

Trace

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1]
2 31 ms 31 ms * L100.LSANCA-DSL-21.verizon-gni.net [71.108.225.1]
3 34 ms 35 ms * P0-2-2-6.LSANCA-LCR-22.verizon-gni.net [130.81.33.132]
4 112 ms 54 ms * so-5-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.151.238]
5 33 ms 32 ms 33 ms 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
6 32 ms 33 ms 33 ms 192.205.35.161
7 46 ms * 47 ms cr1.la2ca.ip.att.net [12.122.82.246]
8 44 ms 47 ms * cr2.phmaz.ip.att.net [12.122.31.190]
9 * * 43 ms 12.122.108.105
10 44 ms 43 ms 44 ms 12-122-254-218.attens.net [12.122.254.218]
11 43 ms 44 ms 44 ms mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Pathing

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Braincandy-PC.Home [192.168.1.2]
1 Broadcom.Home [192.168.1.1]
2 L100.LSANCA-DSL-21.verizon-gni.net [71.108.225.1]
3 P0-2-2-6.LSANCA-LCR-22.verizon-gni.net [130.81.33.132]
4 so-5-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.151.238]
5 * 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
6 192.205.35.161
7 cr1.la2ca.ip.att.net [12.122.82.246]
8 cr2.phmaz.ip.att.net [12.122.31.190]
9 12.122.108.105
10 12-122-254-218.attens.net [12.122.254.218]
11 mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Poyzo-PC.Home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Broadcom.Home [192.168.1.1]
9/ 100 = 9% |
2 77ms 13/ 100 = 13% 4/ 100 = 4% L100.LSANCA-DSL-21.verizon-gni.net [71.108.225.1]
0/ 100 = 0% |
3 71ms 14/ 100 = 14% 5/ 100 = 5% P0-2-2-6.LSANCA-LCR-22.verizon-gni.net [130.81.33.132]
0/ 100 = 0% |
4 75ms 14/ 100 = 14% 5/ 100 = 5% so-5-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.151.238]
0/ 100 = 0% |
5 73ms 9/ 100 = 9% 0/ 100 = 0% 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
8/ 100 = 8% |
6 72ms 17/ 100 = 17% 0/ 100 = 0% 192.205.35.161
83/ 100 = 83% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.82.246]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.phmaz.ip.att.net [12.122.31.190]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.122.108.105
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-218.attens.net [12.122.254.218]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]

Trace complete.

I got a response on the Blizzard forums from an user and it was as followed:

As this shows
2 31 ms 31 ms * L100.LSANCA-DSL-21.verizon-gni.net [71.108.225.1]
You have packet loss on the traceroute, and it shows up aswell on the pathping.
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Broadcom.Home [192.168.1.1]
9/ 100 = 9% |
2 77ms 13/ 100 = 13% 4/ 100 = 4% L100.LSANCA-DSL-21.verizon-gni.net [71.108.225.1]

Call your ISP and give them this information, or the entire pathping and traceroute if you want. But you're having issues starting there. Ask them if you have any dropped packets, signal drops, or if there's an issue with the node you're hitting. Either way, you have 9% loss on your 2nd hop which means it's starting on your end. Well, technically it's your ISP's end, but you get what I mean. 🙂

Comments

stormlashx

Same game as me, idk for how long you been having this issue. In addition, i did look up "Latency" and you can find others talking about this...

Here is my link:

http://forums.verizon.com/t5/FiOS-Internet/Bad-Latency-Online-Gaming/m-p/643935/highlight/true#M42485

I hope they answer to us! GL

dslr595148

Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up. It might shown up as the final hop (bottom-most line of the trace) might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.

For example this what I saw when I was using Verizon

news.giganews.com

traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 13 ms 13 ms 13 ms
2 ash-bb1-link.telia.net (213.248.70.241) 39 ms 7 ms 7 ms
3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 4 ms
4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.20.137) 6 ms 6 ms 6 ms
5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (130.81.13.170) 6 ms 6 ms 6 ms
6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms

Step two: Can you provide the Transceiver Statistics from your modem?

#3 If you don't know how to get that info based upon your modem..

Visit http://192.168.1.1/ . You will be prompted for a username and password. Try the following if you have not changed the password:

admin/password

admin/admin

admin/admin1

admin/password1

admin/verizon

admin/verizon1

Once in the modem, go to Status -> WAN

and then post the info from the Broadband Status area

#4 If you have a RJ-45 WAN port router connected to the modem: What is the brand and model of the RJ-45 WAN port router?

Auditory

traceroute to 71.1******** (71.10.******), 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 ash-bb1-link.telia.net (213.248.70.241) 5 ms 5 ms 31 ms
3 ash-b2-link.telia.net (213.155.130.91) 0 ms 0 ms ash-b2-link.se.telia.net (80.91.245.223) 0 ms
4 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 5 ms 5 ms 5 ms
5 B200.LSANCA-LCR-22.verizon-gni.net (130.81.22.239) 68 ms P1-0-0-0.LSANCA-LCR-22.verizon-gni.net (130.81.199.41) 69 ms B100.LSANCA-LCR-22.verizon-gni.net (130.81.22.247) 68 ms
6 P9-0.LSANCA-DSL-21.verizon-gni.net (130.81.35.39) 68 ms P10-0.LSANCA-DSL-21.verizon-gni.net (130.81.33.133) 68 ms P9-0.LSANCA-DSL-21.verizon-gni.net (130.81.35.39) 68 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * Max number of unresponsive hops reached (firewall or filter?)

Part 3 --

Broadband Status

Broadband Parameter Status

VPI:	0
VCI:	35
Broadband Mode Setting:	ADSL2+
Broadband Negotiated Mode:	ADSL2+
Connection Status:	CONNECTED
Downstream Speed:	2944 Kbps
Upstream Speed:	860 Kbps
Retrains:	0
Retrain Timer:	0 Days, 6H:17M:2S
ATM QoS class:	UBR
Near End CRC Errors Interleave:	6
Near End CRC Errors Fastpath :	N/A
Far End CRC Errors Interleave :	0
Far End CRC Errors Fastpath :	N/A
30 Minute Near End CRC Interleave :	60
30 Minute Near End CRC Fastpath :	N/A
30 Minute Far End CRC Interleave :	0
30 Minute Far End CRC Fastpath :	N/A
Near End RS FEC Interleave :	0
Near End RS FEC Fastpath :	N/A
Far End RS FEC Interleave :	0
Far End RS FEC Fastpath :	N/A
30 Minute Near End FEC Interleave :	33021758
30 Minute Near End FEC Fastpath :	N/A
30 Minute Far End FEC Interleave :	401
30 Minute Far End FEC Fastpath :	N/A
30 Minute Discarded Packets Downstream :	0
30 Minute Discarded Packets Upstream :	0
SNR Downstream :	9 dB
SNR Upstream :	11 dB
Attenuation Downstream :	55 dB
Attenuation Upstream :	27 dB
Power Downstream	17.7 dBm
Power Upstream	12.3 dBm

I don't know what any of this means, but I deleted my IP. Is there anyways I can delete my IP from my first post? It won't let me do it (no edit).

It seems that I've only had the massive lag problem on World of Warcraft, I see to be getting pretty good download speeds when I go to YouTube and browse News sites.

Thanks for the help, I gave you kudos (whatever those are).

Auditory

Still having problems. I went to Blizzard's forums and re-did the trace for them. This is what I got:

Windows Version: Windows 7
Firewall: Microsoft Security Essentials
Driver: 13.1 AMD
DSL: Verizon GT784WN
Is the connection wired or wireless: Wired

Trace Route:

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Broadcom.Home [19*.***.*.*]
2 32 ms 32 ms * L100.LSANCA-DSL-21.verizon-gni.net [7*.***.***]
3 36 ms 35 ms 33 ms P0-1-2-6.LSANCA-LCR-22.verizon-gni.net [130.81.35.38]
4 33 ms 33 ms 33 ms so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.126]
5 33 ms 33 ms 33 ms 0.xe-8-1-0.BR3.LAX15.ALTER.NET [152.63.115.69]
6 33 ms 33 ms 62 ms 192.205.35.161
7 44 ms 47 ms 45 ms cr1.la2ca.ip.att.net [12.122.82.246]
8 49 ms 47 ms * cr2.phmaz.ip.att.net [12.122.31.190]
9 43 ms 44 ms 43 ms 12.122.108.105
10 44 ms 45 ms 44 ms 12-122-254-218.attens.net [12.122.254.218]
11 44 ms 44 ms 44 ms mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Path Ping:

Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bazo-PC.Home [19*.***.*.*]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Broadcom.Home [19*.***.*.*]
9/ 100 = 9% |
2 76ms 17/ 100 = 17% 8/ 100 = 8% L100.LSANCA-DSL-21.verizon-gni.net [71.1**.***]
0/ 100 = 0% |
3 77ms 16/ 100 = 16% 7/ 100 = 7% P0-1-2-6.LSANCA-LCR-22.verizon-gni.net [130.81.35.38]
0/ 100 = 0% |
4 81ms 11/ 100 = 11% 2/ 100 = 2% so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.126]
0/ 100 = 0% |
5 81ms 9/ 100 = 9% 0/ 100 = 0% 0.xe-8-1-0.BR3.LAX15.ALTER.NET [152.63.115.69]
1/ 100 = 1% |
6 86ms 10/ 100 = 10% 0/ 100 = 0% 192.205.35.161
90/ 100 = 90% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.82.246]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.phmaz.ip.att.net [12.122.31.190]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.122.108.105
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-218.attens.net [12.122.254.218]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]

Trace complete.

The response from a Blizzard mod was this:

1 0ms 0/ 100 = 0% 0/ 100 = 0% Broadcom.Home [19*.***.*.*]
9/ 100 = 9% |
2 76ms 17/ 100 = 17% 8/ 100 = 8% L100.LSANCA-DSL-21.verizon-gni.net [71.1**.***]

Your trace route is showing 9% data loss as your router is connecting to your ISP. It's hard to say which end the issue is happening on but the first step I'd recommend is just to reset your modem and router.

If the issue persists, you may need to contact your ISP and ask them about the issue. It's possible they will want to replace the modem.

----------------------

Do I need to replace the modem?

Auditory

Bump!

Blizzard said I am getting a 9% packet loss. How do I fix this? Do I need a new modem?

Child Item