High Ping/Lag Los Angeles

Technical Support
Prev 1 10 11 12 16 Next
It just getting worse. Is there any way to reroute the last 3 hops? That would be 6-8.

tracert -h 9 12.129.222.10 Ran At 10/08/2015 12:00pm

Tracing route to 12.129.222.10 over a maximum of 9 hops

1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 1 ms 1 ms 1 ms L100.LSANCA-VFTTP-131.verizon-gni.net [71.118.203.1]
3 7 ms 7 ms 7 ms G1-2-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.170.92]
4 * * * Request timed out.
5 5 ms 5 ms 5 ms 0.ae5.BR3.LAX15.ALTER.NET [140.222.225.139]
6 * * 83 ms 192.205.35.161
7 * * * Request timed out.
8 * * 78 ms 12.123.249.73
9 * * * Request timed out.

Trace complete.
10/07/2015 08:48 PMPosted by sariabod
Location: Temecula, CA (FIOS)

1 Wireless_Broadband_Router.home (192.168.1.1) 0.265 ms 0.272 ms 0.266 ms
2 lo0-100.LSANCA-VFTTP-310.verizon-gni.net (71.104.60.1) 7.746 ms 9.862 ms 9.878 ms
3 T1-11-0-8.LSANCA-LCR-22.verizon-gni.net (100.41.3.110) 14.805 ms T1-14-0-8.LSANCA-LCR-22.verizon-gni.net (100.41.3.114) 12.046 ms 12.037 ms
4 ae2-0.LAX01-BB-RTR2.verizon-gni.net (130.81.22.238) 11.994 ms ae9-0.LAX01-BB-RTR1.verizon-gni.net (130.81.163.240) 17.426 ms *
5 * 0.ae6.BR3.LAX15.ALTER.NET (140.222.225.141) 17.400 ms 17.392 ms
6 0.ae6.BR3.LAX15.ALTER.NET (140.222.225.141) 17.382 ms 0.ae5.BR3.LAX15.ALTER.NET (140.222.225.139) 11.158 ms 12.067 ms
7 cr1.la2ca.ip.att.net (12.123.132.138) 94.263 ms 192.205.35.161 (192.205.35.161) 94.239 ms 96.981 ms
8 12.122.90.29 (12.122.90.29) 94.181 ms * 94.174 ms
9 12.122.90.29 (12.122.90.29) 91.946 ms 91.922 ms *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


Yea Im in Temecula too and have had major issues until I used a VPN.
After breaking through the front line of defense of customer service at Verizon I was able to speak to a tech. She called me and requested my tracert with blizzard. She said she was going to forward it on so they can look into it. I relayed the message that hundreds of FiOS users are having the same issue. She said they'd be in touch with me when they've identified the problem. Here's to hoping they can help!
Blizzard, can you please move us to another Ip address or reroute the hops, until this has been resolved?

I'm loosing Rift Keys and can't even level up, because of this ongoing issue, that you seem unable to resolve, or you're just not doing anything about.

Tracing route to 12.129.222.10 over a maximum of 9 hops

1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 2 ms 1 ms 2 ms L100.LSANCA-VFTTP-131.verizon-gni.net [71.118.203.1]
3 6 ms 7 ms 7 ms G1-2-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.170.92]
4 * * * Request timed out.
5 5 ms 5 ms 5 ms 0.ae5.BR3.LAX15.ALTER.NET [140.222.225.139]
6 78 ms 79 ms * 192.205.35.161
7 85 ms 82 ms 82 ms cr2.la2ca.ip.att.net [12.122.129.234]
8 79 ms 80 ms 79 ms 12.123.249.73
9 * * * Request timed out.

Trace complete.

Tracing route to 12.129.222.10 over a maximum of 9 hops

1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 1 ms 1 ms 1 ms L100.LSANCA-VFTTP-131.verizon-gni.net [71.118.203.1]
3 7 ms 6 ms 7 ms G1-2-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.170.92]
4 * * * Request timed out.
5 5 ms 6 ms 6 ms 0.ae5.BR3.LAX15.ALTER.NET [140.222.225.139]
6 83 ms 84 ms 108 ms 192.205.35.161
7 79 ms * 82 ms cr2.la2ca.ip.att.net [12.122.129.234]
8 81 ms 80 ms 80 ms 12.123.249.73
9 * * * Request timed out.

Trace complete.

Note: Yesterday, I spent 1 1/2hrs on the phone with Verizon Tech Support, and they were able to confirm that the issue's coming from Hops 6-8. Hope this little bit of info helps, but please do something to help the players out.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.186.0.254 - 0 | 20 | 20 | 0 | 0 | 1 | 0 |
| 125.206.17.37 - 0 | 20 | 20 | 3 | 3 | 6 | 3 |
| 125.206.17.62 - 0 | 20 | 20 | 2 | 3 | 6 | 4 |
| 118.21.174.85 - 0 | 20 | 20 | 4 | 4 | 6 | 4 |
| i118-21-197-93.s99.a049.ap.plala.or.jp - 0 | 20 | 20 | 4 | 4 | 7 | 4 |
| i118-21-178-6.s99.a049.ap.plala.or.jp - 0 | 20 | 20 | 4 | 4 | 5 | 4 |
| 218.43.251.37 - 0 | 20 | 20 | 4 | 9 | 58 | 4 |
| 210.190.162.5 - 0 | 20 | 20 | 4 | 5 | 7 | 4 |
| 118.23.168.91 - 0 | 20 | 20 | 3 | 5 | 13 | 13 |
| ae-11.r21.tokyjp05.jp.bb.gin.ntt.net - 0 | 20 | 20 | 4 | 5 | 8 | 6 |
| ae-4.r31.tokyjp05.jp.bb.gin.ntt.net - 0 | 20 | 20 | 4 | 5 | 10 | 5 |
| ae-9.r20.tokyjp05.jp.bb.gin.ntt.net - 0 | 20 | 20 | 4 | 6 | 12 | 6 |
| ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 0 | 20 | 20 | 90 | 95 | 126 | 91 |
| ae-1.r04.sttlwa01.us.bb.gin.ntt.net - 0 | 20 | 20 | 93 | 94 | 97 | 94 |
| 192.205.34.117 - 7 | 16 | 15 | 120 | 122 | 127 | 124 |
| cr83.st0wa.ip.att.net - 0 | 20 | 20 | 142 | 143 | 148 | 142 |
| cr2.ptdor.ip.att.net - 0 | 20 | 20 | 141 | 144 | 147 | 144 |
| cr2.sffca.ip.att.net - 7 | 16 | 15 | 137 | 141 | 143 | 142 |
| cr2.la2ca.ip.att.net - 0 | 20 | 20 | 146 | 148 | 153 | 150 |
| 12.123.249.77 - 0 | 20 | 20 | 144 | 145 | 150 | 144 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Regardless of how this issue is actually being handled, it feels insulting that this issue isn't a sticky with the rest of the ongoing issues.

Give people a list of phone numbers to pester Verizon at, and a clear, detailed explanation of what is going on with their ISP, and why there is nothing Blizzard can do about it. Please.
Seeing that Blizzard is so weak and futile against the same cable company it's own employees use, what chance do we have? Here comes another weekend (week, month, year?) of lag.
I am having the same issues, but I am not from LA.
the latency spikes from 350 to 1k+ and it's unplayable, no matter what time it is..
guess I just bought the game and can't even play it lol.

I have even contacted blizzard support and did everthing they told me to but the problem persists :(
In every other game it's fine, regular ping but only in Diablo III the latency is horrible.
Fairly large thread on the WoW forums as well http://us.battle.net/wow/en/forum/topic/19021912784
10/08/2015 10:54 PMPosted by Uee
I am having the same issues, but I am not from LA.
the latency spikes from 350 to 1k+ and it's unplayable, no matter what time it is..
guess I just bought the game and can't even play it lol.

I have even contacted blizzard support and did everthing they told me to but the problem persists :(
In every other game it's fine, regular ping but only in Diablo III the latency is horrible.


Check out my thread. You might run into the same problems if your packets are being routed through the problem area in LA.
Indeed, my packets are being routed through area in LA. Can you link me to your thread please?
10/08/2015 10:54 PMPosted by Uee
I am having the same issues, but I am not from LA.
the latency spikes from 350 to 1k+ and it's unplayable, no matter what time it is..
guess I just bought the game and can't even play it lol.

I have even contacted blizzard support and did everthing they told me to but the problem persists :(
In every other game it's fine, regular ping but only in Diablo III the latency is horrible.


Yeah it seems not to be only LA but any FIOS user.

I am pretty sure both are waiting for the other to fix this.
10/08/2015 11:20 PMPosted by Uee
Indeed, my packets are being routed through area in LA. Can you link me to your thread please?


Silly me, I forgot to paste the link.

http://us.battle.net/d3/en/forum/topic/19136205107
In North Cal atm, keep getting dropped from Diablo for no damn reason.
i was reading other thread and blizz said "consider using a VPN"

so blizz, can u buy VPN for all your clients?
cause is your obligations to keep this game without lag and make your clients satisfie with the product that he bought from u!!! maybe i'll consider getting my money back if don't know how to keep a server without lag!!
10/08/2015 11:10 PMPosted by Katrasle
Fairly large thread on the WoW forums as well http://us.battle.net/wow/en/forum/topic/19021912784


Thank you for this, at least the tech support in WOW was kind enough to provide them with an update/explanation.

Unfortunately, there is nothing Blizzard can do about this -- it is a problem that originates with our ISP.

The weird thing is, most of us did not experience this problem prior to ~09/18 and they keep comparing/making the analogy of the internet (in certain places) still being a "single lane freeway, where most of the freeways have been upgraded to 6 lane highways" but we didn't have the congestion a month ago.

It's as if magically, out of nowhere, the servers can't handle it now but they could for months prior (when I'm sure there were more people using those same "roads").

Oh well, guess I'll just have to wait (possibly indefinitely) while they fix this issue.

I have purchased every single blizzard game ever released, LOTV will probably be the first that I do not purchase because playing it with the lag that I have would be impossibly frustrating.

Since some blizzard tech's in the wow forum want to make silly paralells. Buying LOTV (or future blizzard releases) is like buying a new car where you could never drive said car on the freeway.
FIOS in SoCAL. Same issue expressed in this thread.

I followed this thread and connected to the Australia server (http://us.battle.net/d3/en/forum/topic/12372787193 - "OnlineService.Matchmaking.ServerPool=AU1").

The login region is still using America, but the actual game creation is on the AU server. My latency is about 100ms more than it should be (currently averaging 225ms), but at least it's stable and I am no longer disconnecting every few minutes.
Fios user in Socal as well. I have an 80/80 connection, speed test confirmed, and i'm experiencing constant lag and rubber banding. The game is pretty much unplayable. Its been this way for about 2 weeks.
Ongoing nonsense just keeps getting worse, can't keep up with a group let alone deal damage. 1200 ping on 75/75.
I'm just going to start leaving negative feedback everywhere about this game and every blizzard game. No customer care at all. Nearly 3 weeks with the same issue and the only update they give is use a VPN at your own risk.

Join the Conversation

Return to Forum