- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same issue. Why has FiOS not responded yet?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem here. It was a little bit better earlier this moring (1/21/18) but still much higher ping times than normal. Here is the Looking Glass tool output:
TRACEROUTE:
traceroute to 96.244.253.133 (96.244.253.133), 15 hops max, 60 byte packets
1 24.105.30.3 (24.105.30.3) 0.889 ms 0.870 ms 0.888 ms
2 * * *
3 137.221.66.2 (137.221.66.2) 1.316 ms 1.372 ms 1.435 ms
4 137.221.68.66 (137.221.68.66) 1.112 ms 1.210 ms 1.235 ms
5 137.221.68.32 (137.221.68.32) 0.946 ms 0.957 ms 0.967 ms
6 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 0.776 ms 0.798 ms 0.778 ms
7 * * *
8 Verizon-level3-50G.LosAngeles1.Level3.net (4.68.63.246) 0.842 ms 0.869 ms 0.874 ms
9 ae204-0.BLTMMD-VFTTP-321.verizon-gni.net (100.41.219.23) 170.017 ms * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
21/01/2018 16:25:09 UTC
--------------------
MTR:
Start: Sun Jan 21 16:25:09 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.30.3 0.0% 10 0.8 1.2 0.5 5.5 1.5
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.2 0.0% 10 1.2 1.2 1.2 1.3 0.0
4.|-- 137.221.68.66 0.0% 10 1.4 1.3 1.2 1.4 0.0
5.|-- 137.221.68.32 0.0% 10 1.0 1.0 0.9 1.1 0.0
6.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 1.6 1.1 0.8 1.6 0.0
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- Verizon-level3-50G.LosAngeles1.Level3.net 0.0% 10 0.9 2.8 0.9 19.5 5.8
9.|-- ae204-0.BLTMMD-VFTTP-321.verizon-gni.net 20.0% 10 169.5 171.1 169.5 175.1 1.5
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21/01/2018 16:25:09 UTC
--------------------
Is someone trying to hold up Blizzard for more money now that Net Neutrality is dead?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Blizzard is saying that the problem is with Verizon's backbone providers:
https://us.battle.net/forums/en/wow/topic/20760937159?page=15#post-296
Here is my Traceroute:
C:\Users\Brian>tracert 137.221.105.2
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 3 ms 3 ms lo0-100.PITBPA-VFTTP-313.verizon-gni.net [72.77.36.1]
3 8 ms 6 ms 6 ms B3313.PITBPA-LCR-22.verizon-gni.net [100.41.0.184]
4 * * * Request timed out.
5 * * * Request timed out.
6 17 ms 15 ms 15 ms 0.et-7-3-0.BR1.IAD8.ALTER.NET [140.222.239.83]
7 * * 19 ms ae16.edge1.washingtondc12.level3.net [4.68.62.133]
8 * * * Request timed out.
9 128 ms 128 ms 128 ms BLIZZARD-EN.ear3.Washington1.Level3.net [4.16.70.182]
10 128 ms 128 ms 128 ms ae1-br01-eqdc2.blizzardonline.net [137.221.72.33]
11 134 ms 138 ms 138 ms xe-0-0-36-1-br01-eqat2.blizzardonline.net [137.221.65.45]
12 * * * Request timed out.
13 * * * Request timed out.
14 174 ms 176 ms * 137.221.105.2
15 * 176 ms 177 ms 137.221.105.2
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This has been going on for 24-hours now since 1/20/2018 at about 2pm EST. Steps taken personally to resolve it include::
- Computer Reboot
- Recycling the Router
- Calling customer support and having them recycle our box (Notes on my file for what they did)
- Contacting Blizzard Customer Service
MTR Data
MTR:
Start: Sun Jan 21 18:18:18 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.56.100.81 0.0% 10 0.3 0.3 0.2 0.8 0.0
2.|-- 37.244.22.131 0.0% 10 0.5 0.5 0.4 0.8 0.0
3.|-- 24.105.30.162 0.0% 10 0.9 1.1 0.8 2.2 0.0
4.|-- 137.221.66.6 0.0% 10 1.5 1.6 1.4 1.8 0.0
5.|-- 137.221.68.68 0.0% 10 1.5 1.6 1.4 1.8 0.0
6.|-- 137.221.68.32 0.0% 10 1.2 1.6 1.2 3.8 0.6
7.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 1.4 1.1 1.0 1.4 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- Verizon-level3-50G.LosAngeles1.Level3.net 0.0% 10 1.1 1.7 1.1 6.6 1.7
10.|-- ae203-0.NRFLVA-VFTTP-303.verizon-gni.net 40.0% 10 176.3 177.0 176.3 178.8 0.8
11.|-- pool-71-120-216-189.nrflva.fios.verizon.net 40.0% 10 185.5 184.7 182.9 186.2 1.1
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This problem is affecting all Blizzard games. I've hardly been able to play World of Warcraft at all. Information from Blizzard's forums (blue post):
"We've found that the source of these problems seems to be a backbone provider between your individual internet service provider and our servers. None of the looking glass traces we've received for these showed issues between our peers and the Level 3 backbone. The winMTRs and traceroutes we received, however, show that there is a problem after your ISP hands data off to this backbone provider.
What this means is that the source of this problem isn't really your ISP or us, most likely. There are quite a few routers in between your ISP and our servers having issues. In situations like this where the backbone is the culprit, it's really up to your ISP to submit a report to them and try to leverage their business deals with the backbone provider to get it fixed. It's quite possible that this is already happening because of how many people the issue is happening to, but you can always help them with their investigation."
So, Verizon, how can we help you solve this problem, which is apparently with L3?
Tracert results:
Tracing route to 137.221.105.2 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.0.1 2 1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1] 3 5 ms 3 ms 4 ms lo0-100.CLPPVA-VFTTP-304.verizon-gni.net [72.86.37.1] 4 8 ms 10 ms 7 ms B3304.CLPPVA-LCR-21.verizon-gni.net [130.81.221.132] 5 * * * Request timed out. 6 8 ms 8 ms 6 ms 0.et-5-3-0.BR1.IAD8.ALTER.NET [140.222.239.79] 7 * 15 ms * ae16.edge1.washingtondc12.level3.net [4.68.62.133] 8 * * * Request timed out. 9 123 ms 123 ms * BLIZZARD-EN.ear3.Washington1.Level3.net [4.16.70.182] 10 * 124 ms 124 ms ae1-br01-eqdc2.blizzardonline.net [137.221.72.33] 11 134 ms * * xe-0-0-36-1-br01-eqat2.blizzardonline.net [137.221.65.45] 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 * *
Here's an MTR:
MTR: Start: Sun Jan 21 18:50:31 2018 HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1.|-- 24.105.30.2 0.0% 10 4.9 3.1 0.5 13.8 4.4 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3.|-- 137.221.66.4 0.0% 10 1.3 1.3 1.1 1.4 0.0 4.|-- 137.221.68.68 0.0% 10 1.4 1.3 1.2 1.4 0.0 5.|-- 137.221.68.32 0.0% 10 1.0 4.3 0.9 33.7 10.3 6.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 0.8 0.9 0.8 1.0 0.0 7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 8.|-- Verizon-level3-50G.LosAngeles1.Level3.net 0.0% 10 1.0 1.0 0.9 1.5 0.0 9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 10.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net 30.0% 10 172.1 171.6 171.0 172.1 0.0 11.|-- pool-72-73-26-252.clppva.fios.verizon.net 40.0% 10 178.3 178.9 177.0 180.6 1.3
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also located in Buffalo, NY. My GF and myself are having the same issues anytime we connect to a blizzard game, specifically WoW. The game has become completely unplayable.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue began January 20 at approximately 2pm EST and continues today January 21st as of 2pm. Is there an ackowledgemtn that something is wrong and a fix is being worked on or is Verizon not ackowledging this probelm at all?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 0 | 618 | 618 | 0 | 0 | 5 | 0 |
|lo0-100.PITBPA-VFTTP-313.verizon-gni.net - 0 | 618 | 618 | 2 | 5 | 46 | 4 |
| B3313.PITBPA-LCR-21.verizon-gni.net - 0 | 618 | 618 | 3 | 6 | 14 | 6 |
| No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
| 0.et-5-3-0.BR1.IAD8.ALTER.NET - 0 | 618 | 618 | 13 | 15 | 52 | 15 |
| No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.Washington1.Level3.net - 30 | 284 | 200 | 0 | 130 | 154 | 132 |
| ae1-br01-eqdc2.blizzardonline.net - 28 | 297 | 216 | 126 | 129 | 137 | 134 |
| No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
| be1-pe02-eqch2.blizzardonline.net - 26 | 308 | 230 | 132 | 134 | 144 | 135 |
| No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
| 24.105.62.129 - 32 | 276 | 190 | 0 | 135 | 142 | 136 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ive been dealing with this for 24hrs now. Is anyone going to fix this problem?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ok, first time in two months work has given me off, i decide to play a game "world of warcraft" come to find out there is high latency, im talking 3000+ when ive played for years with 23ms home/world. Im finding out its the backbone provider and Fios needs to get on this or atleast answer us on this!