Connection issues 1/20/2018

Technical Support
01/21/2018 10:32 AMPosted by MissCheetah
01/21/2018 10:11 AMPosted by Duckypoo
Verizon Fios is a bunch of clowns. This crap happens at least 1 time every year.


I want to try to be fair here. Verizon FIOS is not the direct cause of the issue I don't think. If it is the same as last night it is Level3 Communications who provide backbone services. Your ISP pays them to carry data so your ISP is responsible for making Level3 fix stuff.


They absolutely are the direct cause. THEY are the ones who chose them. If a manager at work has someone under their authority fail, it is ultimately the managers fault. Verizon is 100% at fault and to blame.
01/20/2018 05:25 PMPosted by heyitscarloc
I'm glad its not just me. I'm also in washington DC and i'm having huge latency problems


Same issue here
01/20/2018 07:43 PMPosted by BattlePants
I never thought that playing a game online would require, at some point, the need to contact my ISP, provide traceroute, pathping, and/or winMTRs, while explaining that while it isn't their fault, I need them to submit a report to the backbone provider and try to leverage their business deals to get it fixed.

Sadly, the regular reps at Fios are going to ask me to reboot my router and such before they even listen to me try to explain that "it looks like DC Peering points are no longer accepting traffic."

I do really appreciate the detailed responses from Blizzard and the community. I just wish I could play my favorite game on my day off.


This is what ending Net Neutrality starts to look like
Seems like it's good now, thank you!
01/21/2018 12:27 PMPosted by MissCheetah
As of a few mins ago Blizzard was able to work with Level3 and Level3 rerouted things so you should start seeing improvement.
Can confirm. No issues now. Thanks blizz!
01/21/2018 12:27 PMPosted by MissCheetah
As of a few mins ago Blizzard was able to work with Level3 and Level3 rerouted things so you should start seeing improvement.


Good now. thanks!
Much better I'm happy!
01/21/2018 12:27 PMPosted by MissCheetah
As of a few mins ago Blizzard was able to work with Level3 and Level3 rerouted things so you should start seeing improvement.


I also can confirm that things are working much better. Thank You! And I also want to Thank You for advocating for this issue. As it pertains to business relationships, I understand what you are saying. Unfortunately when it comes to organizations as large as Verizon, individual consumers are many times granted "best effort" service and that is all. Moreover when the issue really sits in a different organization's network, regardless of the relationship between all the parties involved, it becomes that much more difficult to get to a resolution. I fear what would have happened, or put more accurately, what would not have happened had Blizzard not taken the initiative and chosen to contact Level3 Networks on a Sunday. I sincerely mean it when I say Thank You!
01/21/2018 12:27 PMPosted by MissCheetah
As of a few mins ago Blizzard was able to work with Level3 and Level3 rerouted things so you should start seeing improvement.


cough cough ;)

In all seriousness though, thanks for being communicative.
just attempted to play Diablo 3 and lost connection :(

here are my test results

Tracing route to 24.105.30.129 over a maximum of 30 hops

0 SDOneAlpha [10.118.143.105]
1 Travis [10.118.143.169]
2 100.102.36.1
3 10.102.240.113
4 10.102.241.142
5 10.102.243.153
6 10.102.243.41
7 ae0-806.cr3-sea2.ip4.gtt.net [69.174.1.197]
8 xe-11-2-1.cr2-sea2.ip4.gtt.net [89.149.181.214]
9 ip4.gtt.net [69.174.5.10]
10 ae1-br01-eqse2.blizzardonline.net [137.221.73.33]
11 xe-0-0-0-1-br01-eqsv5.blizzardonline.net [137.221.65.40]
12 xe-0-0-36-1-br02-eqla1.blizzardonline.net [137.221.65.6]
13 be2-pe02-eqla1.blizzardonline.net [137.221.68.73]
14 lax-eqla1-ia-bons-03.blizzardonline.net [137.221.66.7]
15 24.105.30.129

Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SDOneAlpha [10.118.143.105]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Travis [10.118.143.169]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 100.102.36.1
0/ 100 = 0% |
3 34ms 0/ 100 = 0% 0/ 100 = 0% 10.102.240.113
0/ 100 = 0% |
4 33ms 0/ 100 = 0% 0/ 100 = 0% 10.102.241.142
0/ 100 = 0% |
5 34ms 0/ 100 = 0% 0/ 100 = 0% 10.102.243.153
0/ 100 = 0% |
6 50ms 0/ 100 = 0% 0/ 100 = 0% 10.102.243.41
0/ 100 = 0% |
7 53ms 0/ 100 = 0% 0/ 100 = 0% ae0-806.cr3-sea2.ip4.gtt.net [69.174.1.197]
0/ 100 = 0% |
8 64ms 0/ 100 = 0% 0/ 100 = 0% xe-11-2-1.cr2-sea2.ip4.gtt.net [89.149.181.214]
0/ 100 = 0% |
9 59ms 1/ 100 = 1% 1/ 100 = 1% ip4.gtt.net [69.174.5.10]
0/ 100 = 0% |
10 58ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqse2.blizzardonline.net [137.221.73.33]
1/ 100 = 1% |
11 --- 100/ 100 =100% 99/ 100 = 99% xe-0-0-0-1-br01-eqsv5.blizzardonline.net [137.221.65.40]
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% xe-0-0-36-1-br02-eqla1.blizzardonline.net [137.221.65.6]
0/ 100 = 0% |
13 76ms 1/ 100 = 1% 0/ 100 = 0% be2-pe02-eqla1.blizzardonline.net [137.221.68.73]
30/ 100 = 30% |
14 --- 100/ 100 =100% 69/ 100 = 69% lax-eqla1-ia-bons-03.blizzardonline.net [137.221.66.7]
0/ 100 = 0% |
15 82ms 31/ 100 = 31% 0/ 100 = 0% 24.105.30.129

MTR:
Start: Mon Jan 22 19:51:22 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.30.2 0.0% 10 0.5 2.2 0.4 11.8 3.6
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.0 0.0% 10 1.2 1.3 1.1 1.4 0.0
4.|-- 137.221.68.70 0.0% 10 1.3 1.3 1.2 1.5 0.0
5.|-- 137.221.65.7 0.0% 10 8.5 9.2 8.3 12.1 1.2
6.|-- 137.221.65.41 0.0% 10 25.6 33.3 25.6 102.6 24.4
7.|-- 137.221.73.32 0.0% 10 25.4 25.6 25.4 26.0 0.0
8.|-- ip4.gtt.net 0.0% 10 25.3 25.3 25.2 25.4 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 76-8-12-129.cpe.safelink.net 70.0% 10 61.2 68.7 61.2 73.7 6.6

22/01/2018 19:51:21 UTC
--------------------
01/20/2018 05:37 PMPosted by MissCheetah
For issues today 1.20.18 are you on Verizon Fios? There is currently an issue impacting Blizzard games from that ISP. Not sure yet if it is regional.


I'm in Kansas and i do have Verizon. However I have my Internet through my cable company. All it keeps doing is attempting to load my account. Can't get past that screen.
can not connect to diablo so I can play last play 18-01-2018 then nothing
tombstone4
Hey all,

Looking over everything that's been posted the last few days and our internal metrics on this issue, it seems that the issue with users connecting through the level 3 backbone has been resolved.

The tests we've seen in this thread recently seem to mostly be related to local area network connections, or inconclusive. If you're still having issues, let's have you create your own thread so the problem can be looked into.

Join the Conversation

Return to Forum