Reply
Contributor
everon
Posts: 44
Registered: ‎09-04-2012
0

Guild Wars 2 Connection issues.

Hi guys.

 

I seem to be having some problems while trying to play Guild Wars 2 since today (11/09/12)

 

The game runs fine yet sometimes it seems to lose packets whilst playing causing the game to pause or become non-responsive. I have read up on a few sites and came across the way to do a diagnotic trace to NCSofts servers using the -diag command from the games shortcut which supplies the following information: (ive cut out my IP)


==============================================================================
= Checking server connectivity
==============================================================================
Section completed in 0.00 seconds

Diag.ArenaNetworks.com
   206.127.158.31:80 - connect succeeded
 206.127.158.31:6112 - connect succeeded
      64.25.39.21:80 - connect succeeded
    64.25.39.21:6112 - connect succeeded

Section completed in 0.28 seconds

AssetCDN.101.ArenaNetworks.com
  217.156.169.210:80 - connect succeeded
  217.156.169.194:80 - connect succeeded

Section completed in 0.08 seconds

Auth1.101.ArenaNetworks.com
   64.25.38.171:6112 - connect succeeded
   64.25.38.172:6112 - connect succeeded
    64.25.38.54:6112 - connect succeeded
    64.25.38.51:6112 - connect succeeded
    64.25.38.72:6112 - connect succeeded

Section completed in 0.41 seconds

Auth2.101.ArenaNetworks.com
206.127.159.108:6112 - connect succeeded
206.127.159.109:6112 - connect succeeded
 206.127.146.73:6112 - connect succeeded
 206.127.146.74:6112 - connect succeeded
 206.127.159.77:6112 - connect succeeded
206.127.159.107:6112 - connect succeeded

Section completed in 0.36 seconds

CliGate.101.NCPlatform.net
   64.25.40.118:6600 - connect succeeded
    64.25.40.41:6600 - connect succeeded
    64.25.40.33:6600 - connect succeeded
    64.25.40.45:6600 - connect succeeded
    64.25.40.27:6600 - connect succeeded
   64.25.40.122:6600 - connect succeeded
    64.25.40.31:6600 - connect succeeded
   64.25.40.117:6600 - connect succeeded
   64.25.40.120:6600 - connect succeeded
   64.25.40.116:6600 - connect succeeded
   64.25.40.121:6600 - connect succeeded
    64.25.40.47:6600 - connect succeeded
    64.25.40.34:6600 - connect succeeded
    64.25.40.48:6600 - connect succeeded
   64.25.40.119:6600 - connect succeeded

Section completed in 0.53 seconds


==============================================================================
= Tracing network paths
==============================================================================
*--> pathping -w 500 -q 3 -4 64.25.39.1 <--*

Tracing route to 64.25.39.1 over a maximum of 30 hops

  0  TitanSS [*********]
  1  BTHomeHub.home [********]
  2  217.32.146.70
  3  217.32.146.110
  4  213.120.156.66
  5  217.41.168.51
  6  217.41.168.107
  7  acc1-10GigE-0-2-0-4.l-far.21cn-ipp.bt.net [109.159.249.97]
  8  core1-te0-0-0-7.faraday.ukcore.bt.net [109.159.249.5]
  9  62.172.103.9
 10  transit2-xe-3-1-0.ilford.ukcore.bt.net [62.172.103.163]
 11     *     t2c4-xe-10-2-0.uk-ilf.eu.bt.net [166.49.168.105]
 12  195.50.124.69
 13  vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
 14     *     ae-59-224.ebr2.London1.Level3.net [4.69.153.141]
 15  ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
 16  ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
 17  ae-1-100.ebr1.Washington12.Level3.net [4.69.143.213]
 18  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
 19  ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]
 20     *     ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
 21  ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
 22     *     ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
 23  4.59.197.34
 24     *     64.25.32.9
 25  64.25.32.26
 26  64.25.39.1

Computing statistics for 19 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           TitanSS [*********]
                                0/   3 =  0%   |
  1    0ms     0/   3 =  0%     0/   3 =  0%  BTHomeHub.home [********]
                                0/   3 =  0%   |
  2   14ms     0/   3 =  0%     0/   3 =  0%  217.32.146.70
                                0/   3 =  0%   |
  3   19ms     0/   3 =  0%     0/   3 =  0%  217.32.146.110
                                0/   3 =  0%   |
  4   20ms     0/   3 =  0%     0/   3 =  0%  213.120.156.66
                                0/   3 =  0%   |
  5   14ms     0/   3 =  0%     0/   3 =  0%  217.41.168.51
                                0/   3 =  0%   |
  6   15ms     0/   3 =  0%     0/   3 =  0%  217.41.168.107
                                0/   3 =  0%   |
  7  ---       3/   3 =100%     3/   3 =100%  acc1-10GigE-0-2-0-4.l-far.21cn-ipp.bt.net [109.159.249.97]
                                0/   3 =  0%   |
  8  ---       3/   3 =100%     3/   3 =100%  core1-te0-0-0-7.faraday.ukcore.bt.net [109.159.249.5]
                                0/   3 =  0%   |
  9  ---       3/   3 =100%     3/   3 =100%  62.172.103.9
                                0/   3 =  0%   |
 10  ---       3/   3 =100%     3/   3 =100%  transit2-xe-3-1-0.ilford.ukcore.bt.net [62.172.103.163]
                                0/   3 =  0%   |
 11   30ms     1/   3 = 33%     1/   3 = 33%  t2c4-xe-10-2-0.uk-ilf.eu.bt.net [166.49.168.105]
                                0/   3 =  0%   |
 12   21ms     0/   3 =  0%     0/   3 =  0%  195.50.124.69
                                0/   3 =  0%   |
 13   23ms     0/   3 =  0%     0/   3 =  0%  vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
                                0/   3 =  0%   |
 14   22ms     0/   3 =  0%     0/   3 =  0%  ae-59-224.ebr2.London1.Level3.net [4.69.153.141]
                                0/   3 =  0%   |
 15   89ms     0/   3 =  0%     0/   3 =  0%  ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
                                0/   3 =  0%   |
 16  100ms     1/   3 = 33%     1/   3 = 33%  ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
                                0/   3 =  0%   |
 17   97ms     1/   3 = 33%     1/   3 = 33%  ae-1-100.ebr1.Washington12.Level3.net [4.69.143.213]
                                0/   3 =  0%   |
 18  118ms     1/   3 = 33%     1/   3 = 33%  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
                                0/   3 =  0%   |
 19  101ms     1/   3 = 33%     1/   3 = 33%  ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]
                                0/   3 =  0%   |
 20  127ms     0/   3 =  0%     0/   3 =  0%  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
                                0/   3 =  0%   |
 21  125ms     1/   3 = 33%     1/   3 = 33%  ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
                                0/   3 =  0%   |
 22  126ms     0/   3 =  0%     0/   3 =  0%  ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
                                0/   3 =  0%   |
 23  120ms     1/   3 = 33%     1/   3 = 33%  4.59.197.34
                                0/   3 =  0%   |
 24  125ms     0/   3 =  0%     0/   3 =  0%  64.25.32.9
                                1/   3 = 33%   |
 25  ---       3/   3 =100%     2/   3 = 66%  64.25.32.26
                                0/   3 =  0%   |
 26  123ms     1/   3 = 33%     0/   3 =  0%  64.25.39.1

Trace complete.
*--> pathping -w 500 -q 3 -4 206.127.158.1 <--*

Tracing route to p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]
over a maximum of 30 hops:
  0  TitanSS [*******]
  1  BTHomeHub.home [*********]
  2  217.32.146.70
  3  217.32.146.94
  4  213.120.156.90
  5  217.41.168.51
  6  217.41.168.107
  7  109.159.249.108
  8  core1-te0-0-0-7.faraday.ukcore.bt.net [109.159.249.5]
  9  host213-121-193-8.ukcore.bt.net [213.121.193.8]
 10  transit1-pos9-0.telehouse.ukcore.bt.net [62.6.201.118]
 11  t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
 12  166-49-211-38.eu.bt.net [166.49.211.38]
 13  xe-4-0-0.fra60.ip4.tinet.net [89.149.182.74]
 14  cdnetworks-gw.ip4.tinet.net [77.67.71.122]
 15  206-127-157-94.plaync.com [206.127.157.94]
 16  p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Computing statistics for 12 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           TitanSS [********]
                                0/   3 =  0%   |
  1    0ms     0/   3 =  0%     0/   3 =  0%  BTHomeHub.home [********]
                                0/   3 =  0%   |
  2   14ms     1/   3 = 33%     1/   3 = 33%  217.32.146.70
                                0/   3 =  0%   |
  3   19ms     0/   3 =  0%     0/   3 =  0%  217.32.146.94
                                0/   3 =  0%   |
  4   20ms     0/   3 =  0%     0/   3 =  0%  213.120.156.90
                                0/   3 =  0%   |
  5   20ms     0/   3 =  0%     0/   3 =  0%  217.41.168.51
                                0/   3 =  0%   |
  6   19ms     0/   3 =  0%     0/   3 =  0%  217.41.168.107
                                0/   3 =  0%   |
  7  ---       3/   3 =100%     3/   3 =100%  109.159.249.108
                                0/   3 =  0%   |
  8  ---       3/   3 =100%     3/   3 =100%  core1-te0-0-0-7.faraday.ukcore.bt.net [109.159.249.5]
                                0/   3 =  0%   |
  9   31ms     0/   3 =  0%     0/   3 =  0%  host213-121-193-8.ukcore.bt.net [213.121.193.8]
                                0/   3 =  0%   |
 10  ---       3/   3 =100%     3/   3 =100%  transit1-pos9-0.telehouse.ukcore.bt.net [62.6.201.118]
                                0/   3 =  0%   |
 11   21ms     0/   3 =  0%     0/   3 =  0%  t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
                                0/   3 =  0%   |
 12   23ms     0/   3 =  0%     0/   3 =  0%  166-49-211-38.eu.bt.net [166.49.211.38]
                                0/   3 =  0%   |
 13  ---       3/   3 =100%     3/   3 =100%  xe-4-0-0.fra60.ip4.tinet.net [89.149.182.74]
                                0/   3 =  0%   |
 14   34ms     0/   3 =  0%     0/   3 =  0%  cdnetworks-gw.ip4.tinet.net [77.67.71.122]
                                0/   3 =  0%   |
 15  ---       3/   3 =100%     3/   3 =100%  206-127-157-94.plaync.com [206.127.157.94]
                                0/   3 =  0%   |
 16   33ms     0/   3 =  0%     0/   3 =  0%  p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.
Section completed in 175.36 seconds

 


As you can probably see the connection seems to be losing 33% or upto 100% on some of the trace lines. I also cannot seem to get to NcSoft.com which is NCSofts main hub (the page times out)

 

My download speeds are fine as are upload and are stable (27mb down with 6mb up) with pings of around 30ms to most speed check sites including BT's.

 

The problem only seems to have happened today as for the last 2 weeks since game launch it has been stable. Done all the usual things, reset eveything, flushed dns etc yet the problem remains. I am wondering if this is a BT routing issue on their side of the network?

 

Can anyone offer any help?

 

Jay.

Community Manager
StephanieG
Posts: 2,830
Registered: ‎27-01-2010
0

Re: Guild Wars 2 Connection issues.

Hi Jay,

If this is still happening, have you noticed if other games are affected or just Guild Wars 2 for you?

Stephanie
BTCare Community Manager

If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post. If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.
Contributor
everon
Posts: 44
Registered: ‎09-04-2012
0

Re: Guild Wars 2 Connection issues.

[ Edited ]

Thanks for replying back Steph.

 

I am periodically getting some websites timing out such as Vodafone uk. Overall i would say that although my speeds (up and down) seem perfect the net browsing just "feel" more slugish.

 

With that being said it is still reporting problems with the tracerts from Guild Wars 2:

 

==============================================================================
= Tracing network paths
==============================================================================
*--> pathping -w 500 -q 3 -4 206.127.158.1 <--*

Tracing route to p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]
over a maximum of 30 hops:
  0  TitanSS [********]
  1  BTHomeHub.home [********]
  2  217.32.146.70
  3  217.32.146.94
  4  213.120.156.138
  5  217.41.168.67
  6  217.41.168.107
  7  acc1-10GigE-0-0-0-6.l-far.21cn-ipp.bt.net [109.159.249.90]
  8     *     core1-te0-7-0-4.faraday.ukcore.bt.net [109.159.249.33]
  9  host213-121-193-18.ukcore.bt.net [213.121.193.18]
 10  transit1-pos9-0.telehouse.ukcore.bt.net [62.6.201.118]
 11  166-49-211-157.eu.bt.net [166.49.211.157]
 12  166-49-211-38.eu.bt.net [166.49.211.38]
 13  xe-4-0-0.fra60.ip4.tinet.net [89.149.182.74]
 14  cdnetworks-gw.ip4.tinet.net [77.67.71.122]
 15  206-127-157-94.plaync.com [206.127.157.94]
 16     *     p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Computing statistics for 12 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           TitanSS [*********]
                                0/   3 =  0%   |
  1    0ms     0/   3 =  0%     0/   3 =  0%  BTHomeHub.home [********]
                                0/   3 =  0%   |
  2   19ms     0/   3 =  0%     0/   3 =  0%  217.32.146.70
                                0/   3 =  0%   |
  3   21ms     0/   3 =  0%     0/   3 =  0%  217.32.146.94
                                0/   3 =  0%   |
  4   20ms     0/   3 =  0%     0/   3 =  0%  213.120.156.138
                                0/   3 =  0%   |
  5   20ms     0/   3 =  0%     0/   3 =  0%  217.41.168.67
                                0/   3 =  0%   |
  6   21ms     0/   3 =  0%     0/   3 =  0%  217.41.168.107
                                0/   3 =  0%   |
  7  ---       3/   3 =100%     3/   3 =100%  acc1-10GigE-0-0-0-6.l-far.21cn-ipp.bt.net [109.159.249.90]
                                0/   3 =  0%   |
  8  ---       3/   3 =100%     3/   3 =100%  core1-te0-7-0-4.faraday.ukcore.bt.net [109.159.249.33]
                                0/   3 =  0%   |
  9   48ms     0/   3 =  0%     0/   3 =  0%  host213-121-193-18.ukcore.bt.net [213.121.193.18]
                                0/   3 =  0%   |
 10  ---       3/   3 =100%     3/   3 =100%  transit1-pos9-0.telehouse.ukcore.bt.net [62.6.201.118]
                                0/   3 =  0%   |
 11   21ms     0/   3 =  0%     0/   3 =  0%  166-49-211-157.eu.bt.net [166.49.211.157]
                                0/   3 =  0%   |
 12   21ms     0/   3 =  0%     0/   3 =  0%  166-49-211-38.eu.bt.net [166.49.211.38]
                                0/   3 =  0%   |
 13  ---       3/   3 =100%     3/   3 =100%  xe-4-0-0.fra60.ip4.tinet.net [89.149.182.74]
                                0/   3 =  0%   |
 14   36ms     0/   3 =  0%     0/   3 =  0%  cdnetworks-gw.ip4.tinet.net [77.67.71.122]
                                0/   3 =  0%   |
 15  ---       3/   3 =100%     3/   3 =100%  206-127-157-94.plaync.com [206.127.157.94]
                                0/   3 =  0%   |
 16   27ms     0/   3 =  0%     0/   3 =  0%  p4-23-c0-ncdc-pub.plaync.net [206.127.158.1]

Trace complete.
*--> pathping -w 500 -q 3 -4 64.25.39.1 <--*

Tracing route to 64.25.39.1 over a maximum of 30 hops

  0  TitanSS [*********]
  1  BTHomeHub.home [**********]
  2  217.32.146.70
  3  217.32.146.110
  4  213.120.156.138
  5  217.41.168.67
  6  217.41.168.107
  7     *     109.159.249.116
  8  109.159.249.21
  9  62.172.103.17
 10  transit2-xe-11-1-0.ilford.ukcore.bt.net [194.72.20.154]
 11  t2c4-xe-10-0-0.uk-ilf.eu.bt.net [166.49.168.97]
 12     *     195.50.124.69
 13  vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
 14  ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
 15  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
 16  ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
 17  ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41]
 18     *     ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
 19  ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]
 20     *     ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
 21  4.59.197.34
 22  64.25.32.9
 23  64.25.32.26
 24  64.25.39.1

Computing statistics for 18 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           TitanSS ********]
                                0/   3 =  0%   |
  1    0ms     0/   3 =  0%     0/   3 =  0%  BTHomeHub.home [********]
                                0/   3 =  0%   |
  2   14ms     0/   3 =  0%     0/   3 =  0%  217.32.146.70
                                0/   3 =  0%   |
  3   25ms     0/   3 =  0%     0/   3 =  0%  217.32.146.110
                                0/   3 =  0%   |
  4   15ms     0/   3 =  0%     0/   3 =  0%  213.120.156.138
                                0/   3 =  0%   |
  5   15ms     0/   3 =  0%     0/   3 =  0%  217.41.168.67
                                0/   3 =  0%   |
  6   15ms     0/   3 =  0%     0/   3 =  0%  217.41.168.107
                                0/   3 =  0%   |
  7  ---       3/   3 =100%     3/   3 =100%  109.159.249.116
                                0/   3 =  0%   |
  8  ---       3/   3 =100%     3/   3 =100%  109.159.249.21
                                0/   3 =  0%   |
  9  ---       3/   3 =100%     3/   3 =100%  62.172.103.17
                                0/   3 =  0%   |
 10   16ms     2/   3 = 66%     2/   3 = 66%  transit2-xe-11-1-0.ilford.ukcore.bt.net [194.72.20.154]
                                0/   3 =  0%   |
 11   24ms     1/   3 = 33%     1/   3 = 33%  t2c4-xe-10-0-0.uk-ilf.eu.bt.net [166.49.168.97]
                                0/   3 =  0%   |
 12   21ms     0/   3 =  0%     0/   3 =  0%  195.50.124.69
                                0/   3 =  0%   |
 13   26ms     0/   3 =  0%     0/   3 =  0%  vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
                                0/   3 =  0%   |
 14   21ms     0/   3 =  0%     0/   3 =  0%  ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
                                0/   3 =  0%   |
 15   90ms     0/   3 =  0%     0/   3 =  0%  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
                                0/   3 =  0%   |
 16  110ms     0/   3 =  0%     0/   3 =  0%  ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
                                0/   3 =  0%   |
 17   90ms     0/   3 =  0%     0/   3 =  0%  ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41]
                                0/   3 =  0%   |
 18  124ms     0/   3 =  0%     0/   3 =  0%  ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
                                0/   3 =  0%   |
 19  124ms     0/   3 =  0%     0/   3 =  0%  ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]
                                0/   3 =  0%   |
 20  133ms     0/   3 =  0%     0/   3 =  0%  ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
                                0/   3 =  0%   |
 21  126ms     0/   3 =  0%     0/   3 =  0%  4.59.197.34
                                0/   3 =  0%   |
 22  126ms     0/   3 =  0%     0/   3 =  0%  64.25.32.9
                                0/   3 =  0%   |
 23  ---       3/   3 =100%     3/   3 =100%  64.25.32.26
                                0/   3 =  0%   |
 24  120ms     0/   3 =  0%     0/   3 =  0%  64.25.39.1

Trace complete.
Section completed in 189.73 seconds


This was done today (14/09@ 15:48) so its offpeak yet some nodes on the tracert are still dropping large amounts or all of the packets and mostly within the BT parts of the trace which is clearly visible in those tracerts.

 

Finding this very annoying as it is ruining the playability of this game using Infinity. Curiously if i connect to my Virgin 30mb broadband the problems do not happen.

 

Thanks for your help, Jay

 

 

Newbie
gaimz
Posts: 2
Registered: ‎08-10-2012
0

Re: Guild Wars 2 Connection issues.

Hey. I'm having the same issue. I'd be very happy if someone could post a solution.
Aspiring Contributor
NorthernAurora
Posts: 34
Registered: ‎08-05-2012
0

Re: Guild Wars 2 Connection issues.

I get issues all the time with BT Inifinty which has probably be the worst service I have used. It doesn't go down but there is always something wrong with the network they use. Tonight its battlelog.battlefield.com which loads up to slow preventing me from playing Battlefield 3 and soon MOH warfighter on PC because it requires the web based battlelog service to operate so I can't play tonight. This happens every now and again, before BT Inifinity I had no issues.

 

Aspiring Contributor
NorthernAurora
Posts: 34
Registered: ‎08-05-2012
0

Re: Guild Wars 2 Connection issues.

I also forever tracking routes and finding issues with hubs along the way. Fibre provides nice speeds but the network is **bleep**!

Guru
ryant704
Posts: 2,805
Registered: ‎02-08-2012
0

Re: Guild Wars 2 Connection issues.

Note to Mod, I'm getting this on a wide variety of games and internet browsing. Cod4, Heroes of newerth, etc

If this helped you please click the Star beside my name.

If this answered your question please click "Mark as Accepted Solution" below.
Newbie
gaimz
Posts: 2
Registered: ‎08-10-2012
0

Re: Guild Wars 2 Connection issues.

It would be really helpful if a moderator could follow up on this issue since it does seem to be affecting several people. 

Guru
ryant704
Posts: 2,805
Registered: ‎02-08-2012
0

Re: Guild Wars 2 Connection issues.


gaimz wrote:

It would be really helpful if a moderator could follow up on this issue since it does seem to be affecting several people. 


 

It's been raised to BT and they're aware of the problem, it's a probl with a 3rd party company who they're helping to assist to get the problem fixed ASAP!

If this helped you please click the Star beside my name.

If this answered your question please click "Mark as Accepted Solution" below.
Newbie
MancandGrime
Posts: 8
Registered: ‎08-10-2012
0

Re: Guild Wars 2 Connection issues.

There's a huge thread regarding the same kind of issues using EA servers and other games. There's a known issue, and stated above. It's currently being worked on. We're just left in te dark of an update from time to time, but things are starting to look up at the moment

The problem has been there for around 5 days for some people. Problem was first noticed back on the 5th for me personally. Haven't been able to connect to any games since that date, and have been patiently waiting for a response until today.