Frontier Communications and Lag Spikes

90 Undead Warlock
5405
Recently came back to WoW after a 4 month break. I'm on the same computer that I used to play WoW prior to MoP launch 2010 27" IMac quad core . Everything was fine until about a month ago. I am getting very random lag spikes, screen freezes for anywhere from 1-3 seconds. When the lag spike stops everything that has occurred while I was frozen happens at once. I contact my ISP (Frontier Communications) ran a traceroute for them and they said there appeared to be a problem with my router. The new router arrived, I get everything hooked up and log in to WoW. Same problem keeps happening. I call Frontier and tell them about the problem and talk to them about the pathping results which show a 13% loss at my router then another 16-50 loss at

hop 11 vlan56.icore1.sqn-sanjose.as6453.net.

They tell me to go to path forward and open a ticket for someone at Blizzard because it's on Blizzards end. It doesn't appear to be on Blizzards end but that's what Frontier says. Any help would be much appreciated. I have done everything possible (shut down comp and unplugged then restarted, unhooked the battery for the FiOS box then restarted, reset the router etc etc) none of this has worked. Here is the most recent pathping report. The loss ALWAYS occurs at my router and at hop 11 vlan56.icore1.sqn-sanjose.as6453.net I have seen anywhere from 16% to 50% loss at this hop. Any help would be greatly appreciated.

1 wireless_broadband_router (192.168.1.1) 0.563 ms 0.337 ms 0.208 ms 0.206 ms 0.201 ms 0.206 ms * 0.436 ms 0.257 ms 0.198 ms 0.194 ms 0.192 ms * 0.473 ms 0.327 ms 0.266 ms 0.269 ms 0.200 ms * 0.310 ms 0.283 ms 0.288 ms 0.301 ms 0.289 ms * 0.442 ms 0.238 ms 0.219 ms 0.213 ms 0.217 ms (13% loss)
2 static-50-46-224-1.evrt.wa.frontiernet.net (50.46.224.1) 4.935 ms 4.659 ms 4.370 ms 4.682 ms 4.083 ms 4.591 ms 4.231 ms 4.304 ms 4.667 ms 4.308 ms 4.459 ms 4.355 ms 4.795 ms 4.159 ms 4.559 ms 4.348 ms 4.107 ms 5.447 ms 4.251 ms 4.588 ms 4.316 ms 4.788 ms 4.116 ms 4.668 ms 4.137 ms 4.362 ms 3.933 ms 4.244 ms 4.566 ms 4.444 ms (0% loss)
3 50.34.2.149 (50.34.2.149) 5.319 ms 5.634 ms 4.800 ms 5.257 ms 5.811 ms 5.422 ms 5.597 ms 5.951 ms 5.125 ms 5.321 ms 5.281 ms 5.624 ms 5.592 ms 5.573 ms 5.285 ms 5.743 ms 5.992 ms 6.034 ms 4.942 ms 5.418 ms 5.628 ms 5.311 ms 4.863 ms 5.499 ms 4.941 ms 5.352 ms 5.702 ms 5.399 ms 4.962 ms 5.910 ms (0% loss)
4 ae3---0.cor01.sttl.wa.frontiernet.net (74.40.1.153) 7.012 ms 6.439 ms 6.765 ms 6.635 ms 6.479 ms 6.793 ms 6.651 ms 6.460 ms 6.837 ms 6.619 ms 6.574 ms 6.845 ms 7.305 ms 6.441 ms 6.826 ms 6.717 ms 6.504 ms 6.049 ms 24.427 ms 6.384 ms 29.067 ms 6.636 ms 6.318 ms 7.025 ms 6.524 ms 6.497 ms 6.940 ms 6.486 ms 6.478 ms 6.791 ms (0% loss)
5 ae0---0.cbr01.sttl.wa.frontiernet.net (74.40.5.122) 5.973 ms 6.364 ms 6.555 ms 6.256 ms 6.412 ms 6.536 ms 6.840 ms 6.568 ms 6.540 ms 7.031 ms 6.359 ms 6.591 ms 6.780 ms 6.406 ms 6.690 ms 6.819 ms 6.576 ms 6.485 ms 6.861 ms 6.462 ms 6.692 ms 6.838 ms 6.380 ms 6.706 ms 6.848 ms 6.507 ms 6.589 ms 6.856 ms 6.432 ms 6.624 ms (0% loss)
6 if-9-0-0.core1.00s-seattle.as6453.net (207.45.206.29) 6.959 ms 5.992 ms 6.411 ms 6.125 ms 6.654 ms 6.429 ms 6.881 ms 6.117 ms 6.290 ms 6.800 ms 6.073 ms 6.259 ms 6.183 ms 6.767 ms 6.431 ms 6.248 ms 6.317 ms 6.715 ms 5.953 ms 6.311 ms 6.911 ms 5.997 ms 6.376 ms 6.742 ms 6.838 ms 6.357 ms 6.808 ms 6.715 ms 6.420 ms 6.734 ms (0% loss)
7 if-0-1-0-2.tcore1.00s-seattle.as6453.net (64.86.123.1) 27.004 ms 26.399 ms 26.128 ms 26.174 ms 26.320 ms 34.879 ms 27.461 ms 26.396 ms 26.722 ms 26.788 ms 26.498 ms 26.762 ms 26.770 ms 26.480 ms 25.899 ms 26.218 ms 42.699 ms 28.921 ms 26.238 ms 29.868 ms 26.614 ms 26.901 ms 26.245 ms 25.919 ms 26.346 ms 26.233 ms 26.617 ms 27.107 ms 31.521 ms 26.267 ms (0% loss)
8 if-14-2.tcore1.pdi-paloalto.as6453.net (64.86.123.22) 26.976 ms 27.973 ms 26.850 ms 28.887 ms 32.612 ms 27.233 ms 26.428 ms 28.310 ms 33.036 ms 26.870 ms 30.239 ms 26.996 ms 27.198 ms 26.659 ms 56.131 ms 27.675 ms 58.033 ms 45.335 ms 27.306 ms 27.270 ms 27.510 ms 27.337 ms 26.813 ms 26.464 ms 27.363 ms 26.834 ms 27.150 ms 26.034 ms 26.689 ms 26.490 ms (0% loss)
9 if-2-2.tcore2.pdi-paloalto.as6453.net (66.198.127.2) 32.018 ms 26.736 ms 27.278 ms 26.612 ms 26.746 ms 26.527 ms 30.095 ms 27.611 ms 26.735 ms 26.940 ms 26.226 ms 26.579 ms 26.366 ms 26.908 ms 26.584 ms 26.559 ms 31.405 ms 26.261 ms 26.346 ms 26.371 ms 26.587 ms 26.956 ms 26.215 ms 50.244 ms 28.931 ms 26.658 ms 26.151 ms 26.433 ms 26.615 ms 26.988 ms (0% loss)
10 if-14-0-0-3261.core3.sqn-sanjose.as6453.net (66.198.144.50) 26.370 ms
if-2-0-0.core3.sqn-sanjose.as6453.net (66.198.144.46) 26.928 ms
if-10-0-0-3256.core3.sqn-sanjose.as6453.net (66.198.144.18) 26.117 ms
if-13-0-0-3255.core3.sqn-sanjose.as6453.net (66.198.144.14) 26.803 ms
if-14-0-0-3261.core3.sqn-sanjose.as6453.net (66.198.144.50) 26.234 ms
if-13-0-0-3255.core3.sqn-sanjose.as6453.net (66.198.144.14) 27.209 ms 26.030 ms
if-10-0-0-3256.core3.sqn-sanjose.as6453.net (66.198.144.18) 27.529 ms
if-2-0-0.core3.sqn-sanjose.as6453.net (66.198.144.46) 26.810 ms
if-14-0-0-3261.core3.sqn-sanjose.as6453.net (66.198.144.50) 25.772 ms
if-10-0-0-3256.core3.sqn-sanjose.as6453.net (66.198.144.18) 26.074 ms
if-2-0-0.core3.sqn-sanjose.as6453.net (66.198.144.46) 26.905 ms 26.227 ms
if-10-0-0-3256.core3.sqn-sanjose.as6453.net (66.198.144.18) 26.755 ms 26.832 ms
if-14-0-0-3261.core3.sqn-sanjose.as6453.net (66.198.144.50) 25.621 ms 25.441 ms 25.052 ms
if-2-0-0.core3.sqn-sanjose.as6453.net (66.198.144.46) 27.331 ms
if-13-0-0-3255.core3.sqn-sanjose.as6453.net (66.198.144.14) 26.838 ms
if-10-0-0-3256.core3.sqn-sanjose.as6453.net (66.198.144.18) 26.920 ms 25.796 ms
if-13-0-0-3255.core3.sqn-sanjose.as6453.net (66.198.144.14) 27.510 ms 26.303 ms
if-10-0-0-3256.core3.sqn-sanjose.as6453.net (66.198.144.18) 26.917 ms
if-13-0-0-3255.core3.sqn-sanjose.as6453.net (66.198.144.14) 27.756 ms
if-2-0-0.core3.sqn-sanjose.as6453.net (66.198.144.46) 26.541 ms 26.840 ms
if-10-0-0-3256.core3.sqn-sanjose.as6453.net (66.198.144.18) 28.137 ms
if-14-0-0-3261.core3.sqn-sanjose.as6453.net (66.198.144.50) 25.496 ms (0% loss)
11 vlan56.icore1.sqn-sanjose.as6453.net (209.58.116.49) 34.454 ms 27.710 ms 30.915 ms 36.400 ms 36.596 ms 35.240 ms 35.634 ms * 39.114 ms 35.976 ms * 38.850 ms 36.306 ms 35.481 ms * * * 27.143 ms 35.679 ms * 39.679 ms 35.388 ms 35.638 ms 35.975 ms 35.755 ms 36.477 ms 35.350 ms 36.357 ms * * (26% loss)
12 192.205.37.65 (192.205.37.65) 30.298 ms 29.370 ms 29.384 ms 29.811 ms 29.385 ms 30.543 ms 31.528 ms 29.111 ms 29.559 ms 28.891 ms 30.192 ms 28.712 ms 28.838 ms 29.478 ms 28.308 ms 30.387 ms 28.825 ms 28.104 ms 28.296 ms 30.304 ms 28.916 ms 28.963 ms 29.126 ms 29.162 ms 28.569 ms 30.451 ms 28.802 ms 28.326 ms 29.552 ms 28.986 ms (0% loss)
13 cr1.sffca.ip.att.net (12.122.86.198) 50.262 ms 62.686 ms 48.083 ms 49.737 ms 51.700 ms 50.351 ms 48.160 ms 52.850 ms 47.146 ms 49.680 ms 50.896 ms 48.997 ms 50.998 ms 49.005 ms 50.911 ms 47.556 ms 47.377 ms 48.297 ms 46.447 ms 49.474 ms 47.574 ms 50.899 ms 50.602 ms 48.612 ms 47.593 ms 51.015 ms 51.067 ms 48.114 ms 49.743 ms 50.168 ms (0% loss)
14 cr1.la2ca.ip.att.net (12.122.3.122) 49.037 ms 51.124 ms 47.885 ms 47.516 ms 48.124 ms 48.308 ms 48.009 ms 47.852 ms 47.591 ms 48.220 ms 47.416 ms 47.809 ms 47.396 ms 48.330 ms 48.010 ms 48.345 ms 47.125 ms 48.144 ms 48.243 ms 48.140 ms 48.139 ms 47.985 ms 47.177 ms 48.339 ms 48.199 ms 48.128 ms 51.692 ms 48.275 ms 47.948 ms 47.207 ms (0% loss)
15 cr2.phmaz.ip.att.net (12.122.31.190) 50.437 ms 49.015 ms 47.651 ms 48.348 ms 52.306 ms 51.403 ms 47.860 ms 52.068 ms 51.901 ms 47.987 ms 47.858 ms 52.761 ms 47.929 ms 47.638 ms 51.534 ms 48.328 ms 62.072 ms 48.946 ms 51.898 ms 47.847 ms 52.152 ms 51.836 ms 51.741 ms 48.226 ms 51.838 ms 48.034 ms 48.094 ms 47.960 ms 48.240 ms 48.053 ms (0% loss)
16 12.123.206.225 (12.123.206.225) 55.686 ms 45.772 ms 46.026 ms 46.390 ms 45.874 ms 46.227 ms 46.326 ms 46.813 ms 45.486 ms 47.072 ms 45.213 ms 46.172 ms 46.191 ms 45.962 ms 45.629 ms 45.448 ms 44.990 ms 46.029 ms 45.590 ms 58.588 ms 46.925 ms 46.684 ms 45.611 ms 46.062 ms 45.782 ms 45.885 ms 46.807 ms 45.664 ms 45.902 ms 45.001 ms (0% loss)
17 12-122-254-50.attens.net (12.122.254.50) 47.775 ms 47.465 ms 47.337 ms 47.557 ms 48.021 ms 47.210 ms 48.322 ms 47.909 ms 46.986 ms 46.966 ms 48.155 ms 47.681 ms 47.255 ms 47.745 ms 47.552 ms 46.688 ms 47.660 ms 47.702 ms 47.487 ms 47.487 ms 47.450 ms 47.900 ms 46.725 ms 48.207 ms 47.446 ms 48.239 ms 47.744 ms 48.166 ms 46.822 ms 47.472 ms (0% loss)
18 mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 47.111 ms 46.153 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 46.845 ms 45.924 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 46.167 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 45.791 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 46.833 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 46.247 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 45.736 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 45.970 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 46.322 ms 45.891 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 46.660 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 46.318 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 45.163 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 47.280 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 46.356 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 47.226 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 45.898 ms 45.732 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 47.367 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 46.945 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 47.212 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 47.098 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 47.554 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 45.745 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 46.147 ms 46.304 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 46.364 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 46.988 ms (0% loss)
19 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
20 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
21 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
22 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
23 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
24 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
25 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
26 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
27 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
28 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
29 * * * * * * * * * *

Thanks.
Reply Quote
MVP - Technical Support
100 Draenei Mage
7170
hop 11 vlan56.icore1.sqn-sanjose.as6453.net

They tell me to go to path forward and open a ticket for someone at Blizzard because it's on Blizzards end. It doesn't appear to be on Blizzards end but that's what Frontier says.


Sounds like you were speaking to someone from their Tier 1 support team and not their higher tiers. Someone who continues to believe that communication over the internet is strictly A -> B

It is not A -> B and in fact hasn't been A -> B since back in the 60's/70's when they got the first routers going. Your ISP and Blizzard don't own all the internet so at some point it does get routed through other company's servers.

Which is what appears to be happening here. If you go to :

http://as6453.net/

You can see that vlan56.icore1.sqn-sanjose.as6453.net is a peering server run by Tata Communications. Naming sequence suggests one in San Jose.

Since it's an issue at a peering partner for your ISP you need to go back to your ISP and get them to escalate it to either a Tier 3 or Tier 4 tech support rep. IIRC Tier 2 reps are the supervisors for Tier 1 usually so past them. You need to get it to a team that deals with peer partner relationships.

Also if you can try to get MTR for OS X installed somehow and run one of those when you have the elevated latency that would be good too.
Reply Quote
90 Undead Warlock
5405
Thanks a lot Blu. Sounds like another hour long conversation with Frontier :)
Reply Quote
90 Undead Warlock
5405
Frontier Communications claims that they don't work with Tata Communications. Guess I should call Blizz.
Reply Quote
MVP - Technical Support
100 Draenei Mage
7170
01/31/2013 04:06 PMPosted by Alcolol
Frontier Communications claims that they don't work with Tata Communications. Guess I should call Blizz.


Did you get it escalated ?

Did you get ask to open a ticket with their peer partner(s) ?
Reply Quote
90 Undead Warlock
5405
Opened a ticktet with Frontier this morning to have the issue looked at by a Tier 3 or Tier 4 tech support person. Thanks a lot for the help Blu. If I hadn't known to escalate the issue to a Tier 3 or Tier 4 tech support then I would have just accepted the "It's not us it's them" theory.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]