Jump to content
  • Sign Up

Very high ping


Recommended Posts

  • 2 weeks later...

I'm having unbearable ping as well, it's very frustrating. Trying to farm dragonite today, I was unable to get credit for several world bosses because no skills would activate. I can see everybody else fighting and killing the boss, but I personally cannot contribute. This happens all the time lately on world bosses especially, but also to a lesser extent in group content.

Oddly, sometimes I have no lag whatsoever but OTHER people around will be complaining that they can't do anything. It's like they have to ration their server priority, and sometimes I get it but sometimes I don't.

Link to comment
Share on other sites

  • 3 months later...

Since Friday 12/20 I started having a ping of 4,000 and NEVER had that issue before. My connection is awesome, My other games are fine, its only GW2 and it started Friday. This is unplayable and horrible. sometimes it will go back down to a ping of 69 then spikes back up immediately. Is this because of Wintersday??????

Link to comment
Share on other sites

Game's been extremely hard to play for me since the move to Amazon's servers.Like, a warrior vengeanced and Bull's Charged me the moment I happened to drop packets/spike/whatever you wanna call it and by the time I saw the animation it was already way too late. Extremely frustrating to die to after winning the fight (and not being someone who would die to the vengeance if I was able to actually see it happen).

All my packet loss comes right at the end on the last jump to the AWS servers but it's really inconsistent. My ping's higher to this game than just about anything else, even when they're located in the same region.

Open world's even worse but it's PvE and it doesn't matter so it's mostly ignorable.

Link to comment
Share on other sites

Same here Shagie. after 6+ years playing Guild Wars 2 this is the frist time since December 17, Wintersday patch i ever had very high ping. It was so high at one time it went to 4,000. DO NOT,, REPEAT DO NOT uninstall the game the way I did thinking it would be fixed because YOU CANNOT launch the game past 35% downloading. Just hope and pray when Wintersday is over Jan 7 that it goes back to normal. Until now I feel your pain but I also cannot get on the game lol.

Link to comment
Share on other sites

  • 3 months later...

I'm having a hard time with Ping for the past few months. Looking at the options menu, I was startled by unimaginable 3,780 pings! It was impossible to play WxW, which is my favorite part of GW2. I have already looked for solutions, but I see that it is best to stay away from the game for a while. Abandoning it entirely becomes impossible, as I bought both expansions and won the original game. I sincerely hope that Arenanet solves this problem. I speak from Brazil and connect to the US server. :s

Link to comment
Share on other sites

I've had this problem for months now and it has recently started getting extreme again.

Between traceroute, pingplotter, and whois three names consistently come up for where my connection dies: Century Link, AT&T, and Amazon.

More often than not it's a Century Link owned hop.

I'm willing to bet that Anet is aware of the problem but it's very likely that we're too tiny of a minority to have them address the problem. And even if they did acknowledge it the problem spots (for me at least) are big American corporations so it's beyond their ability to deal with.

Link to comment
Share on other sites

@"thepenmonster.3621" I too am on CL, and doing a Visual Traceroute to the IP address listed for WvW, I get lots of packet loss within the Amazon owned AWS. In addition to this, I also have a spike of 50ms going from the West Coast to Kansas City (where CL HQ is located). CLs cer-edge-19 router adds that extra 50ms. While I normally would chalk this up as distance, this is within their own network, and going even to Level 3 Networks in Seattle (another CL owned company), I do not get these large spikes up.

When I have done the traceroutes, I normally use UDP and TCP, not ICMP (ICMP is what is normally used when using tracert). With both of those, have been doing this off and on the past few days, I normally get packet loss starting in the AWS, not within CL's network. For myself, the packet loss starts with the IP 150.222.240.61, and gets worse (up to 80%+ packet loss) at 52.93.129.130, 150.222.243.201, & 52.93.28.116. This is after 10 traces with 3 tests per hop, and a total of 32 hops using "Whatsup Visual Traceroute"with the latest version of WinPCap so I can use the TCP/UDP traceroute features. All are free (will need to sign up for crap email from ipswitch.

If you want to get results, tell CL that you are trying to telecommute using RDP, and that the lag is horrid.

http://garou1674.com/images/VisualTraceRt20200409.PNG

Link to comment
Share on other sites

@rooney.7968 , while I do agree with you when it comes to it being a ANet problem, as this is mainly within AWS, ANet does have a Service Level Agreement (SLA) with AWS. That SLA does allow ANet certain lee-ways to have AWS improve their network performance, otherwise a lawyer somewhere is not doing their job. The SLA should have stipulations on network reliability. If ANets customers are notifying them of a network problem, then ANet needs to contact AWS about the problem to have them fix the problem per the SLA.

Right now, after this last week, WvW has gotten better, as the server was changed out. I am not sure why this would be, as I have not done a trace on the new IP address. Something tells me there may still be packet loss within AWS.

Link to comment
Share on other sites

  • 1 month later...

Came to the forums, and glad to see I'm not the only one seeing issues. My ping would randomly jump over 1k or 4k many times throughout the session, even with a hard line and 945mbps speeds and plenty of bandwidth. EVERY other game on my PC run has low ping when playing online, but only GW2 runs into severe issues.

Link to comment
Share on other sites

  • 8 months later...
  • 6 months later...

File verification results

Spoiler

2021-08-24T01:01:46Z
Client build is 118898 (101)
Manifest build is 118898
Verifying contents of archive...
Duration: 531 seconds
Examined 582339 of 582339 files.
Deleted 0 bad files.
Skipped 0 files (local files, different versions, etc).

 

Diag results

Spoiler

ArenaNet diagnostic utility [118898]

Windows version: 6.2
Build 9200


Section completed in 0.00 seconds

==============================================================================
= Detecting network connections
==============================================================================
*--> netstat -n <--*

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:4843         127.0.0.1:58662        ESTABLISHED
  TCP    127.0.0.1:58662        127.0.0.1:4843         ESTABLISHED
  TCP    192.168.200.37:49731   192.168.200.1:445      ESTABLISHED
  TCP    192.168.200.37:52344   23.206.181.66:443      ESTABLISHED
  TCP    192.168.200.37:52683   199.232.192.134:443    ESTABLISHED
  TCP    192.168.200.37:52718   204.79.197.219:443     ESTABLISHED
  TCP    192.168.200.37:53153   151.101.248.193:443    ESTABLISHED
  TCP    192.168.200.37:53376   104.16.51.111:443      ESTABLISHED
  TCP    192.168.200.37:53525   40.91.72.120:443       SYN_SENT
  TCP    192.168.200.37:53608   199.232.194.49:443     ESTABLISHED
  TCP    192.168.200.37:54333   52.226.139.180:443     ESTABLISHED
  TCP    192.168.200.37:54789   162.159.133.234:443    ESTABLISHED
  TCP    192.168.200.37:55488   20.42.73.27:443        ESTABLISHED
  TCP    192.168.200.37:55739   104.18.70.113:443      ESTABLISHED
  TCP    192.168.200.37:55980   162.159.129.233:443    ESTABLISHED
  TCP    192.168.200.37:55981   162.159.129.233:443    TIME_WAIT
  TCP    192.168.200.37:57159   162.254.192.108:27023  ESTABLISHED
  TCP    192.168.200.37:59260   52.31.167.171:443      ESTABLISHED
  TCP    192.168.200.37:59578   23.196.33.60:443       CLOSE_WAIT
  TCP    192.168.200.37:59743   199.232.192.64:443     ESTABLISHED
  TCP    192.168.200.37:61771   104.21.62.111:443      ESTABLISHED
  TCP    192.168.200.37:62898   151.101.128.134:443    ESTABLISHED
  TCP    192.168.200.37:63679   199.232.192.134:443    ESTABLISHED
  TCP    192.168.200.37:64278   52.186.166.218:443     CLOSE_WAIT
  TCP    192.168.200.37:64499   34.196.0.198:443       ESTABLISHED
  TCP    192.168.200.37:64605   104.244.42.72:443      ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:50174  [2600:1901:0:47fc::]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:51326  [2606:2800:220:1410:489:141e:20bb:12f6]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:51552  [2607:f8b0:4004:c0b::54]:443  TIME_WAIT
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:52250  [2603:1036:302:403c::2]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:52306  [2603:1036:302:5059::2]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:52308  [2603:1036:302:5059::2]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:52608  [2600:9000:2073:6200:11:3feb:8080:93a1]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:53161  [2001:4860:4860::8888]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:53523  [2603:1036:302:860::2]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:54000  [2606:4700:3036::6815:4be1]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:54499  [2607:f8b0:4004:829::200e]:443  TIME_WAIT
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:59216  [2606:4700:3034::6815:14eb]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:59262  [2603:1036:302:874::2]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:59639  [2001:4860:4860::8888]:443  TIME_WAIT
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:61724  [2600:9000:2073:6200:11:3feb:8080:93a1]:443  TIME_WAIT
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:61830  [2600:9000:2073:ac00:1e:ebe7:1480:93a1]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:62950  [2603:1036:302:505e::2]:443  ESTABLISHED
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:63544  [2600:9000:20e2:d600:6:8656:f5c0:93a1]:443  TIME_WAIT
  TCP    [2601:5c8:4400:edc:59db:732c:a95e:7d86]:64524  [2607:f8b0:4004:836::2003]:443  TIME_WAIT
Section completed in 0.05 seconds


==============================================================================
= Discovering external address
==============================================================================
Current IP Address: 71.57.207.127

Section completed in 65.23 seconds


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

Diag.ArenaNetworks.com
    34.194.154.37:80 - connect succeeded
     34.237.20.65:80 - connect succeeded
   34.225.225.173:80 - connect succeeded
   34.235.245.105:80 - connect succeeded
  34.194.154.37:6112 - connect succeeded
 34.225.225.173:6112 - connect succeeded
 34.235.245.105:6112 - connect succeeded
   34.237.20.65:6112 - connect succeeded
    34.236.133.94:80 - connect succeeded
  34.236.133.94:6112 - connect succeeded

Section completed in 0.05 seconds

assetcdn.101.ArenaNetworks.com.
    52.85.150.218:80 - connect succeeded
    52.85.150.156:80 - connect succeeded
     52.85.150.69:80 - connect succeeded
    52.85.150.130:80 - connect succeeded

Section completed in 0.05 seconds

auth1.101.ArenaNetworks.com.
  34.194.154.37:6112 - connect succeeded
 34.225.225.173:6112 - connect succeeded
   34.237.20.65:6112 - connect succeeded
 34.235.245.105:6112 - connect succeeded
  34.236.133.94:6112 - connect succeeded

Section completed in 0.05 seconds

auth2.101.ArenaNetworks.com.
 35.157.208.241:6112 - connect succeeded
   52.59.151.62:6112 - connect succeeded
  18.194.203.41:6112 - connect succeeded
  35.158.82.209:6112 - connect succeeded
  35.158.175.20:6112 - connect succeeded

Section completed in 0.13 seconds

cligate.101.NCPlatform.net.
   54.209.50.30:6112 - connect succeeded
  35.172.60.203:6112 - connect succeeded
  18.211.211.76:6112 - connect succeeded
   34.206.145.8:6112 - connect succeeded
  18.205.118.62:6112 - connect succeeded
  34.205.96.208:6112 - connect succeeded
 18.233.194.228:6112 - connect succeeded

Section completed in 0.05 seconds


==============================================================================
= Tracing network paths (about 10 mins)
==============================================================================
*--> pathping -w 500 -q 50 -4 205.251.198.219 <--*

Tracing route to ns-1755.awsdns-27.co.uk [205.251.198.219]
over a maximum of 30 hops:
  0  -DESKTOP.hsd1.va.comcast.net [192.168.200.37] 
  1  BagEnd [192.168.200.1] 
  2  96.120.18.153 
  3  24.124.163.93 
  4  96.108.140.141 
  5  ae-73-ar02.charlvilleco.va.richmond.comcast.net [96.108.140.129] 
  6  be-31512-cs01.ashburn.va.ibone.comcast.net [96.110.42.129] 
  7  be-1113-cr13.ashburn.va.ibone.comcast.net [96.110.34.146] 
  8  be-302-cr12.newark.nj.ibone.comcast.net [96.110.36.118] 
  9  be-1412-cs04.newark.nj.ibone.comcast.net [96.110.35.93] 
 10  be-2402-pe02.newark.nj.ibone.comcast.net [96.110.37.62] 
 11  50.248.117.242 
 12     *        *        *     
Computing statistics for 137 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           -DESKTOP.hsd1.va.comcast.net [192.168.200.37] 
                                0/  50 =  0%   |
  1    0ms     0/  50 =  0%     0/  50 =  0%  BagEnd [192.168.200.1] 
                                0/  50 =  0%   |
  2    8ms     0/  50 =  0%     0/  50 =  0%  96.120.18.153 
                                0/  50 =  0%   |
  3    7ms     0/  50 =  0%     0/  50 =  0%  24.124.163.93 
                                0/  50 =  0%   |
  4    7ms     0/  50 =  0%     0/  50 =  0%  96.108.140.141 
                                0/  50 =  0%   |
  5   15ms     1/  50 =  2%     1/  50 =  2%  ae-73-ar02.charlvilleco.va.richmond.comcast.net [96.108.140.129] 
                                0/  50 =  0%   |
  6   16ms     4/  50 =  8%     4/  50 =  8%  be-31512-cs01.ashburn.va.ibone.comcast.net [96.110.42.129] 
                                0/  50 =  0%   |
  7   16ms     2/  50 =  4%     2/  50 =  4%  be-1113-cr13.ashburn.va.ibone.comcast.net [96.110.34.146] 
                                0/  50 =  0%   |
  8   21ms     0/  50 =  0%     0/  50 =  0%  be-302-cr12.newark.nj.ibone.comcast.net [96.110.36.118] 
                                0/  50 =  0%   |
  9   21ms     2/  50 =  4%     2/  50 =  4%  be-1412-cs04.newark.nj.ibone.comcast.net [96.110.35.93] 
                                0/  50 =  0%   |
 10   21ms     0/  50 =  0%     0/  50 =  0%  be-2402-pe02.newark.nj.ibone.comcast.net [96.110.37.62] 
                                2/  50 =  4%   |
 11   22ms     2/  50 =  4%     0/  50 =  0%  50.248.117.242 

Trace complete.
*--> pathping -w 500 -q 50 -4 205.251.193.91 <--*

Tracing route to ns-347.awsdns-43.com [205.251.193.91]
over a maximum of 30 hops:
  0  -DESKTOP.hsd1.va.comcast.net [192.168.200.37] 
  1  BagEnd [192.168.200.1] 
  2  96.120.18.153 
  3  24.124.163.93 
  4  96.108.140.141 
  5  ae-73-ar02.charlvilleco.va.richmond.comcast.net [96.108.140.129] 
  6  be-31542-cs04.ashburn.va.ibone.comcast.net [96.110.42.141] 
  7  be-1413-cr13.ashburn.va.ibone.comcast.net [96.110.34.158] 
  8  be-302-cr12.newark.nj.ibone.comcast.net [96.110.36.118] 
  9  be-1312-cs03.newark.nj.ibone.comcast.net [96.110.35.89] 
 10  be-3311-pe11.philadelphia.pa.ibone.comcast.net [96.110.36.138] 
 11  50.242.150.106 
 12  52.93.60.231 
 13     *        *        *     
Computing statistics for 150 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           -DESKTOP.hsd1.va.comcast.net [192.168.200.37] 
                                0/  50 =  0%   |
  1    0ms     0/  50 =  0%     0/  50 =  0%  BagEnd [192.168.200.1] 
                                0/  50 =  0%   |
  2    7ms     0/  50 =  0%     0/  50 =  0%  96.120.18.153 
                                0/  50 =  0%   |
  3    8ms     0/  50 =  0%     0/  50 =  0%  24.124.163.93 
                                0/  50 =  0%   |
  4    7ms     0/  50 =  0%     0/  50 =  0%  96.108.140.141 
                                0/  50 =  0%   |
  5   15ms     0/  50 =  0%     0/  50 =  0%  ae-73-ar02.charlvilleco.va.richmond.comcast.net [96.108.140.129] 
                                0/  50 =  0%   |
  6   16ms     2/  50 =  4%     2/  50 =  4%  be-31542-cs04.ashburn.va.ibone.comcast.net [96.110.42.141] 
                                0/  50 =  0%   |
  7   16ms     2/  50 =  4%     2/  50 =  4%  be-1413-cr13.ashburn.va.ibone.comcast.net [96.110.34.158] 
                                0/  50 =  0%   |
  8   21ms     0/  50 =  0%     0/  50 =  0%  be-302-cr12.newark.nj.ibone.comcast.net [96.110.36.118] 
                                1/  50 =  2%   |
  9   21ms     1/  50 =  2%     0/  50 =  0%  be-1312-cs03.newark.nj.ibone.comcast.net [96.110.35.89] 
                                0/  50 =  0%   |
 10   23ms     1/  50 =  2%     0/  50 =  0%  be-3311-pe11.philadelphia.pa.ibone.comcast.net [96.110.36.138] 
                                0/  50 =  0%   |
 11   24ms     1/  50 =  2%     0/  50 =  0%  50.242.150.106 
                               49/  50 = 98%   |
 12  ---      50/  50 =100%     0/  50 =  0%  52.93.60.231 

Trace complete.
*--> pathping -w 500 -q 50 -4 99.84.221.59 <--*

Tracing route to server-99-84-221-59.iad79.r.cloudfront.net [99.84.221.59]
over a maximum of 30 hops:
  0  -DESKTOP.hsd1.va.comcast.net [192.168.200.37] 
  1  BagEnd [192.168.200.1] 
  2  96.120.18.153 
  3  24.124.163.93 
  4  96.108.140.141 
  5  ae-73-ar02.charlvilleco.va.richmond.comcast.net [96.108.140.129] 
  6  be-31532-cs03.ashburn.va.ibone.comcast.net [96.110.42.137] 
  7  be-2301-pe01.ashburn.va.ibone.comcast.net [96.110.37.122] 
  8  75.149.229.2 
  9     *        *        *     
Computing statistics for 100 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           -DESKTOP.hsd1.va.comcast.net [192.168.200.37] 
                                0/  50 =  0%   |
  1    0ms     0/  50 =  0%     0/  50 =  0%  BagEnd [192.168.200.1] 
                                0/  50 =  0%   |
  2    8ms     0/  50 =  0%     0/  50 =  0%  96.120.18.153 
                                0/  50 =  0%   |
  3    8ms     0/  50 =  0%     0/  50 =  0%  24.124.163.93 
                                0/  50 =  0%   |
  4    8ms     0/  50 =  0%     0/  50 =  0%  96.108.140.141 
                                0/  50 =  0%   |
  5   14ms     0/  50 =  0%     0/  50 =  0%  ae-73-ar02.charlvilleco.va.richmond.comcast.net [96.108.140.129] 
                                0/  50 =  0%   |
  6   16ms     5/  50 = 10%     5/  50 = 10%  be-31532-cs03.ashburn.va.ibone.comcast.net [96.110.42.137] 
                                0/  50 =  0%   |
  7   16ms     0/  50 =  0%     0/  50 =  0%  be-2301-pe01.ashburn.va.ibone.comcast.net [96.110.37.122] 
                                0/  50 =  0%   |
  8   18ms     0/  50 =  0%     0/  50 =  0%  75.149.229.2 

Trace complete.
Section completed in 343.11 seconds


==============================================================================
= Running DirectX diagnostic
==============================================================================
--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER1 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Gw2-64.exe
P2: 1.0.0.1
P3: 61201b9b
P4: 078a
P5: 134217728
P6: 
P7: 
P8: 
P9: 
P10: 

Section completed in 12.89 seconds


==============================================================================
= Result
==============================================================================
Test complete
<EOF>

 

Link to comment
Share on other sites

1 hour ago, Orimidu.9604 said:

Bump, is this a problem for anyone else since the beta update last week? Exact same symptoms for me.

Ever since the update last Tuesday, my game has been lagging and crashing.. It's almost a week now, when will it be playable again..

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...