cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Ping in World of Warcraft starts low and then climbs. Appears to be linked to Blocks in hub's log

Kritya
Dabbler
Posts: 15
Thanks: 4
Registered: ‎12-10-2016

Ping in World of Warcraft starts low and then climbs. Appears to be linked to Blocks in hub's log

‎19-11-2016 1:46 PM

I started playing WoW again today, assumed there wouldn't be any issues as I played it fine on this connection just over a month ago. But I've run into a snag where my ping starts low (15) and jumps up every so often until the game becomes almost impossible to play, got up to 840 at one point. Restarting the game brings it back down to 15 for a short time.

13:38:33, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [105.225.110.224]:22180 ppp3 NAPT)
13:38:21, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [86.27.25.200]:17973 ppp3 NAPT)
13:37:59, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [69.253.151.97]:19141 ppp3 NAPT)
13:37:58, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [217.208.135.87]:27168 ppp3 NAPT)
13:37:34, 19 Nov.	IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 88.109.109.150-​>46.208.18.60 on ppp3)
13:37:32, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [72.94.24.209]:11422 ppp3 NAPT)
13:37:28, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [116.44.75.93]:28454 ppp3 NAPT)
13:37:26, 19 Nov.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.64]:54540-​>[40.127.129.109]:443 on ppp3)
13:37:25, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [62.199.162.18]:57661 ppp3 NAPT)
13:37:16, 19 Nov.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.64]:36421-​>[132.245.213.50]:443 on ppp3)
13:36:41, 19 Nov.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.64]:54540-​>[40.127.129.109]:443 on ppp3)
13:36:41, 19 Nov.	OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.64]:54540-​>[40.127.129.109]:443 on ppp3)
13:36:33, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [105.225.110.224]:22180 ppp3 NAPT)
13:36:21, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [86.27.25.200]:17973 ppp3 NAPT)
13:35:59, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [69.253.151.97]:19141 ppp3 NAPT)
13:35:58, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [217.208.135.87]:27168 ppp3 NAPT)
13:35:32, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [72.94.24.209]:11422 ppp3 NAPT)
13:35:28, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [116.44.75.93]:28454 ppp3 NAPT)
13:35:25, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [62.199.162.18]:57661 ppp3 NAPT)
13:35:11, 19 Nov.	IN: BLOCK [16] Remote administration (TCP [199.217.118.45]:59010-​>[46.208.18.60]:22 on ppp3)
13:34:56, 19 Nov.	IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 71.185.255.208-​>46.208.18.60 on ppp3)
13:33:09, 19 Nov.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [217.208.135.87]:55574 ppp3 NAPT)
13:33:00, 19 Nov.	IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 2.31.141.30-​>46.208.18.60 on ppp3)
13:31:09, 19 Nov.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.67]:46696 <-​-​> [46.208.18.60]:46696 -​ -​ -​ [217.208.135.87]:55574 ppp3 NAPT)

Above is the log from launching the game and leaving it open for just under 10 minutes. Every time the ping jumped up I refreshed the error log and there was a new block right at the top, so the 2 seem connected.

Any help as to figuring out what's causing the blocks, and in turn, the instability of my connection to the game server?

Message 1 of 6
(1,115 Views)
0 Thanks
5 REPLIES 5
Kritya
Dabbler
Posts: 15
Thanks: 4
Registered: ‎12-10-2016

Re: Ping in World of Warcraft starts low and then climbs. Appears to be linked to Blocks in hub's lo

‎19-11-2016 5:29 PM

Well my internet is now 5 down and 0.5 up, instead of 40 and 2 respectively. so I'll just have to assume you're having some technical issues today.

Message 2 of 6
(1,085 Views)
0 Thanks
Kritya
Dabbler
Posts: 15
Thanks: 4
Registered: ‎12-10-2016

Re: Ping in World of Warcraft starts low and then climbs. Appears to be linked to Blocks in hub's lo

‎19-11-2016 8:59 PM

After some testing, this isn't only happening in WoW. It happens in league of legends and smite too. Twitch streams constantly buffer for tiny amounts of time.

Normally I am directly wired, tried wireless and it's even worse.

Any chance of getting some help with this?

Message 3 of 6
(1,060 Views)
0 Thanks
Kritya
Dabbler
Posts: 15
Thanks: 4
Registered: ‎12-10-2016

Re: Ping in World of Warcraft starts low and then climbs. Appears to be linked to Blocks in hub's lo

‎20-11-2016 1:43 PM - edited ‎20-11-2016 2:05 PM

http://n2.netalyzr.icsi.berkeley.edu/summary/id=36a470be-5130-730c350d-12ca-4564-87de#burstloss

This test shows something different to what it normally shows,

12 transient outages instead of 0. Suggesting intermittent connection loss.

Well, this post is being completely ignored despite having logs and test results, which leads me to believe there's an issue on PlusNet's end that they aren't wanting to admit to. 10/10 customer support here folks.

Message 4 of 6
(1,028 Views)
0 Thanks
Kritya
Dabbler
Posts: 15
Thanks: 4
Registered: ‎12-10-2016

Re: Ping in World of Warcraft starts low and then climbs. Appears to be linked to Blocks in hub's lo

‎20-11-2016 4:17 PM

So it turns out this is a widespread issue relating to SouthBank, and PlusNet aren't responding to any topics on the matter it seems.

So for those who, like me, are unfortunate enough to be stuck on the SouthBank gateway (yes I've tried restarting multiple times, it won't route elsewhere). Then you will experience fairly nasty packet loss for the foreseeable future. No idea when/if it will be fixed.

Check your gateway here: http://usertools.plus.net/@gateway/

Message 5 of 6
(992 Views)
0 Thanks
matias
Newbie
Posts: 1
Registered: ‎20-11-2016

Re: Ping in World of Warcraft starts low and then climbs. Appears to be linked to Blocks in hub's lo

‎20-11-2016 9:11 PM

I have the same problem in the League of legends and Cs GO.
Earlier it was good but for two days it is impossible to play.
I was doing a test on the router and the packet loss

 

PING www.google.com (216.58.213.68): 56 data bytes
64 bytes from 216.58.213.68: seq=0 ttl=55 time=16.962 ms
64 bytes from 216.58.213.68: seq=2 ttl=55 time=39.189 ms
64 bytes from 216.58.213.68: seq=3 ttl=55 time=17.171 ms
64 bytes from 216.58.213.68: seq=4 ttl=55 time=17.204 ms
64 bytes from 216.58.213.68: seq=6 ttl=55 time=17.141 ms
64 bytes from 216.58.213.68: seq=8 ttl=55 time=16.962 ms

--- www.google.com ping statistics ---
9 packets transmitted, 6 packets received, 33% packet loss
round-trip min/avg/max = 16.962/20.771/39.189 ms

Message 6 of 6
(946 Views)
0 Thanks