My ping is normally pretty good, hovers around 40-70. but for the last 2 weeks it has been terrible, strange thing is it seems restricted on a map by map basis.
In a good map, it’s still 40-70, bad maps are constantly over 300 with spikes up to 4k! I can play foefire and barely be able to move then load in to temple and all is completely normal. Same on pve maps.
This is only ping/lag, FPS is totally fine. It can happen any time of the day, not just peak.
I ran a diagnostic as described on the support page, but unfortunately I don’t have a clue what it means, anyone know how to read it, or having similar problems?
================
= Checking server connectivity
================
Section completed in 0.00 seconds
Diag.ArenaNetworks.com
64.25.39.21:6112 – connect succeeded
64.25.39.21:80 – connect succeeded
206.127.158.31:80 – connect failed
206.127.158.31:6112 – connect failed
Section completed in 10.08 seconds
assetcdn.101.ArenaNetworks.com.
151.249.94.68:80 – connect succeeded
151.249.94.69:80 – connect succeeded
Section completed in 0.08 seconds
auth1.101.ArenaNetworks.com.
64.25.38.51:6112 – connect succeeded
64.25.38.172:6112 – connect succeeded
64.25.38.72:6112 – connect succeeded
64.25.38.54:6112 – connect succeeded
64.25.38.171:6112 – connect succeeded
Section completed in 0.19 seconds
auth2.101.ArenaNetworks.com.
206.127.146.74:6112 – connect succeeded
206.127.159.108:6112 – connect succeeded
206.127.146.73:6112 – connect succeeded
206.127.159.107:6112 – connect succeeded
206.127.159.109:6112 – connect succeeded
206.127.159.77:6112 – connect succeeded
Section completed in 0.09 seconds
cligate.101.NCPlatform.net.
64.25.47.122:6112 – connect succeeded
64.25.47.121:6112 – connect succeeded
64.25.47.118:6112 – connect succeeded
64.25.47.117:6112 – connect succeeded
64.25.47.119:6112 – connect succeeded
64.25.47.120:6112 – connect succeeded
64.25.47.116:6112 – connect succeeded
Section completed in 3.10 seconds
================
= Tracing network paths (about 10 mins)
================
—> pathping -w 500 -q 50 -4 206.127.158.1 <--
Tracing route to 206-127-158-1.ncsoft.com [206.127.158.1]
over a maximum of 30 hops:
0 Baroness.home [192.168.1.66]
1 BThomehub.home [192.168.1.254]
2 * * *
Computing statistics for 12 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Baroness.home [192.168.1.66]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% BThomehub.home [192.168.1.254]
Trace complete.
—> pathping -w 500 -q 50 -4 64.25.39.1 <--
Tracing route to 64.25.33-1.ncsoft.com [64.25.39.1]
over a maximum of 30 hops:
0 Baroness.home [192.168.1.66]
1 BThomehub.home [192.168.1.254]
2 * * *
Computing statistics for 12 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Baroness.home [192.168.1.66]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% BThomehub.home [192.168.1.254]
Trace complete.
—> pathping -w 500 -q 50 -4 151.249.94.69 <--
Tracing route to 151.249.94.69 over a maximum of 30 hops
0 Baroness.home [192.168.1.66]
1 BThomehub.home [192.168.1.254]
2 * * *
Computing statistics for 12 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Baroness.home [192.168.1.66]
0/ 50 = 0% |
1 0ms 0/ 50 = 0% 0/ 50 = 0% BThomehub.home [192.168.1.254]
Trace complete.
Section completed in 34.24 seconds