World of Warcraft and FiOS, incredibly frustrating and I am so desperate for help!

[blue_angel1122]

Hey,

We recently got FiOS, and about 4 days after getting it, I have not been able to play World of Warcraft very well at all.  Also VOIP clients like Skype and voipcheap.com have not worked at all.  Regarding WoW, I have done everything they suggest, I have opened ports on my router for all of the aforementioned applications and I am still reading latency values in WoW of 500-8000ms.  I know this is possibly a problem for Blizzard/WoW, but they have been useless with their support!

I have done a tracert, it was done a couple of weeks ago but the problem has not changed since it was performed:

Tracing route to host-1.wow-europe.com [80.239.179.1]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]

2 8 ms 7 ms 11 ms L100.LSANCA-VFTTP-03.verizon-gni.net [72.67.218.1]

3 7 ms 6 ms 7 ms P9-1.LSANCA-LCR-03.verizon-gni.net [130.81.32.154]

4 8 ms 7 ms 9 ms so-6-1-2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.28.225]

5 9 ms 10 ms 9 ms 0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]

6 93 ms 92 ms 91 ms 0.so-1-0-0.XL3.NYC4.ALTER.NET [152.63.0.5]

7 93 ms 92 ms 91 ms teliasonera-test.alter.net [157.130.255.206]

8 92 ms 92 ms 94 ms nyk-bb2-link.telia.net [80.91.248.157]

9 166 ms 177 ms 165 ms prs-bb2-link.telia.net [80.91.253.125]

10 165 ms 164 ms 164 ms prs-b1-link.telia.net [80.91.250.249]

11 167 ms 167 ms 167 ms prs-tc-i1-link-telia.net [80.91.250.30]

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

It looks like a telia problem, but any input here would be appreciated, because Blizzard customer service is messing me around.

The weird thing is, this is a European server but I never had problems prior to this, and there are others in the UK on the same server suffering with latency like this.  However some people are lucky and get no latency.

But yeah, any assistance with this would be incredibly useful, thank you in advance to any help offered!

[Techman28]

I'm just curious as I'm also an Avid player of the game. Is this a Tracert to the server? What is the Server name so I can run a tracert as well

See if you can find your server Here

Message Edited by Techman28 on 05-14-2009 07:39 PM

[blue_angel1122]

Hey,

My realm is not on that list, because it is an EU Realm.

I know the IP address is right, it is the Doomhammer-EU realm.

Thank you by the way for the quick response!  As I stated, it looks like the WoW EU telia servers are acting up for a lot of people, but then for others it is fine.

WoW support has been useless!  

Thanks again!

edit: Could it be a problem with my internet connection?  My boyfriend who I speak with on Skype and VOIPCheap software has reported that I have been cutting out lots.  Would a pathping to the Doomhammer-EU WoW realm be beneficial to you also?

Message Edited by blue_angel1122 on 05-16-2009 07:37 AM

[CharlesH]

Yeah, looks like issues with http://www.telia.se/ at their routers. Not a whole lot FiOS is going to be able to do...uhhh learn to speak swedish and call them?  I don't know...

Message Edited by CharlesH on 05-16-2009 10:43 AM

[blue_angel1122]

Yup, just what I thought.

Suppose I have to pay now to contact their phone numbers in Europe!

Because telia is who WoW use for their routing and servers, I have to go through them.  Perhaps their lack of response in this week's latency thread on the WoW forum is because they have no solution to it.

Simple solution is for them to get better hardware and a new provider!

Perhaps you guys could expand into Europe to give us EU realm players better realm usages!!!!!!!!

Thanks very much for your help

[KenAF]

If you want low latency on WoW servers, you have to use the U.S. realms.  There is no solution at this time.

[Techman28]

Blue Angel don't contact Telia. Contact Blizzard and advise them of their response break when connecting to their server that way you don't have to pay to contact Telia

[blue_angel1122]

@Ken: Thanks for your input, but not entirely helpful.  I had low latency with WoW Europe up til about 3 weeks ago, and then all of a sudden it goes wrong.

If it helps, I have a tracert and pathping that I did earlier today:

 Tracing route to host-1.wow-europe.com [80.239.179.1]over a maximum of 30 hops:  

1     1 ms     1 ms     1 ms  myrouter.home [192.168.1.1]   
2     9 ms     9 ms     7 ms  L100.LSANCA-VFTTP-03.verizon-gni.net [72.67.218.1]   
3     7 ms     7 ms     7 ms  P9-1.LSANCA-LCR-03.verizon-gni.net [130.81.32.154]   
4    11 ms     7 ms     6 ms  so-6-1-2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.28.225]   
5    12 ms    12 ms    10 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]   
6   116 ms    94 ms    94 ms  0.so-1-0-0.XL3.NYC4.ALTER.NET [152.63.0.5]   
7    92 ms    93 ms    95 ms  teliasonera-test.alter.net [157.130.255.206]   
8    93 ms    94 ms    94 ms  nyk-bb2-link.telia.net [80.91.248.157]   
9   165 ms   165 ms   166 ms  prs-bb2-link.telia.net [80.91.253.125]  
10   165 ms   167 ms   168 ms  prs-b1-link.telia.net [80.91.250.249]  
11   168 ms   167 ms   169 ms  prs-tc-i1-link-telia.net [80.91.250.30]  
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.

That was the tracert, here is the pathping:

Tracing route to host-1.wow-europe.com [80.239.179.1]

over a maximum of 30 hops:

  0  kagome.home [192.168.1.11]

  1  myrouter.home [192.168.1.1]

  2  L100.LSANCA-VFTTP-03.verizon-gni.net [72.67.218.1]

  3  P9-1.LSANCA-LCR-03.verizon-gni.net [130.81.32.154]

  4  so-6-1-2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.28.225]

  5  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]

  6  0.so-1-0-0.XL3.NYC4.ALTER.NET [152.63.0.5]

  7  teliasonera-test.alter.net [157.130.255.206]

  8  nyk-bb2-link.telia.net [80.91.248.157]

  9  prs-bb2-link.telia.net [80.91.253.125]

 10  prs-b1-link.telia.net [80.91.250.249]

 11  prs-tc-i1-link-telia.net [80.91.250.30]

 12     *        *        *     

Computing statistics for 300 seconds...

            Source to Here   This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                           kagome.home [192.168.1.11]

                                0/ 100 =  0%   |

  1   74ms     2/ 100 =  2%     2/ 100 =  2%  myrouter.home [192.168.1.1]

                                0/ 100 =  0%   |

  2   69ms     0/ 100 =  0%     0/ 100 =  0%  L100.LSANCA-VFTTP-03.verizon-gni.net [72.67.218.1]

                                0/ 100 =  0%   |

  3   55ms     0/ 100 =  0%     0/ 100 =  0%  P9-1.LSANCA-LCR-03.verizon-gni.net [130.81.32.154]

                                0/ 100 =  0%   |

  4   48ms     0/ 100 =  0%     0/ 100 =  0%  so-6-1-2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.28.225]

                                0/ 100 =  0%   |

  5   34ms     0/ 100 =  0%     0/ 100 =  0%  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]

                                0/ 100 =  0%   |

  6  102ms     0/ 100 =  0%     0/ 100 =  0%  0.so-1-0-0.XL3.NYC4.ALTER.NET [152.63.0.5]

                                0/ 100 =  0%   |

  7   97ms     1/ 100 =  1%     1/ 100 =  1%  teliasonera-test.alter.net [157.130.255.206]

                                0/ 100 =  0%   |

  8   97ms     0/ 100 =  0%     0/ 100 =  0%  nyk-bb2-link.telia.net [80.91.248.157]

                                0/ 100 =  0%   |

  9  167ms     0/ 100 =  0%     0/ 100 =  0%  prs-bb2-link.telia.net [80.91.253.125]

                                0/ 100 =  0%   |

 10  165ms     0/ 100 =  0%     0/ 100 =  0%  prs-b1-link.telia.net [80.91.250.249]

                                0/ 100 =  0%   |

 11  178ms     0/ 100 =  0%     0/ 100 =  0%  prs-tc-i1-link-telia.net [80.91.250.30]

                              100/ 100 =100%   |

 12  ---     100/ 100 =100%     0/ 100 =  0%  kagome [0.0.0.0]

Trace complete.

If the problem is with Verizon, please just admit it and fix it, I will not be **bleep** if it is a Verizon problem, as long as it gets fixed!  Otherwise, would a call to your customer support be better, as I think that if it is a problem with WoW specifically, more people would be effected.  However, I have 2 others in my guild from the USA, and they have latency no more than 300ms.

Whatever, your help is appreciated even if I can't get on WoW to play with my fiance!  

Thanks again

[spacedebris]

from the looks of the trace route. the problem is in the transition from the NYC backbone to the Atlantic crossing. Several things could be an issue and unfortunately there is really nothing that you can really do about any of it.

1. it could be a new routing table between the NYC backbone to a new crossing

2. could be a new routing table from the crossing to the European network

3. could simply be a bad router (hop) that someone hasnt caught and replaced yet

4. could be more traffic being routed through those hops

None of which you can really do anything about other than shake your fist at it.

BTW the verizon portion of your route ends at hop 4 that up to that point verizon would have been able to help. but hop 5 and beyond are out on the internet and outside the ability for verizon to do anything about

Message Edited by spacedebrismark on 05-17-2009 03:12 PM

[prisaz]

Seems like the connection is lost here, which has nothing to do with Verizon.

11  prs-tc-i1-link-telia.net [80.91.250.30]

Perhaps our friends at the NSA do not play WoW.

Message Edited by prisaz on 05-18-2009 08:30 PM