Webafrica high latency at night

D

diesel

Expert Member
Joined
Mar 4, 2007
Messages
2,797
Hi

Is anyone else experiencing higher latency at night time on their webafrica accounts? , for some reason my latency at night fluctuates , normally i get around 190 - 195ms but at night this number goes up to 230 - 290ms.

I have cancelled my webafrica account and now looking for a replacement , priority for me is low latency for gaming, i only need a 200gb capped account. any recommendations?.

cheers
 
WebAfrica Helper

WebAfrica Helper

Web Africa representative
Joined
Apr 2, 2012
Messages
2,175
Hi

Please DM us your contact details so we may investigate and help with this asap .

Thank you for your time.

Rafeeqah
 
P

Pada

Executive Member
Joined
Feb 18, 2009
Messages
8,189
I had the same thing in my CS:GO game on a local server, where instead of a 20-40ms ping, mine was ranging between 140-230ms.

Another played from Cape Town region on a Crystal Web account had the exact same high ping as me throughout our whole game.

The strange thing was that ICMP ping/traceroute showed no abnormalities:
Code: 
Tracing route to 155.133.238.162 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.11.1
  2     *        *        *     Request timed out.
  3    32 ms   129 ms    57 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
  4    24 ms    24 ms    23 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    24 ms    24 ms    24 ms  196.35.115.136
  6    24 ms    25 ms    24 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
  7    24 ms    24 ms    25 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
  8    41 ms    41 ms    42 ms  168.209.100.101
  9    41 ms    42 ms    41 ms  168.209.1.140
 10    42 ms    41 ms    42 ms  197.97.118.82
 11    43 ms    41 ms    43 ms  xe-0-0-0-0.er-02-jnb.za.seacomnet.com [105.16.28.10]
 12    42 ms    42 ms    43 ms  105.22.42.58
 13    43 ms    44 ms    42 ms  192.168.210.49
 14    42 ms    42 ms    42 ms  155.133.238.162

I'm currently using a "Home: 150GB + 1000GB Pro" account.
 
C

chuck606

Active Member
Joined
Nov 21, 2012
Messages
48
Very high ping tonight.... Trace route also seems fine...
It started like half hour ago, any one else having problems tonight?
 
Johnatan56

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,957
Pada said:
I had the same thing in my CS:GO game on a local server, where instead of a 20-40ms ping, mine was ranging between 140-230ms.

Another played from Cape Town region on a Crystal Web account had the exact same high ping as me throughout our whole game.

The strange thing was that ICMP ping/traceroute showed no abnormalities:
Code: 
Tracing route to 155.133.238.162 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.11.1
  2     *        *        *     Request timed out.
  3    32 ms   129 ms    57 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
  4    24 ms    24 ms    23 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    24 ms    24 ms    24 ms  196.35.115.136
  6    24 ms    25 ms    24 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
  7    24 ms    24 ms    25 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
  8    41 ms    41 ms    42 ms  168.209.100.101
  9    41 ms    42 ms    41 ms  168.209.1.140
 10    42 ms    41 ms    42 ms  197.97.118.82
 11    43 ms    41 ms    43 ms  xe-0-0-0-0.er-02-jnb.za.seacomnet.com [105.16.28.10]
 12    42 ms    42 ms    43 ms  105.22.42.58
 13    43 ms    44 ms    42 ms  192.168.210.49
 14    42 ms    42 ms    42 ms  155.133.238.162

I'm currently using a "Home: 150GB + 1000GB Pro" account.
Click to expand...
That third hop is bad, are you suffering from packet loss? Could you also ping exchange.crystalweb.co.za (155.239.255.250) for 20 seconds?
Code: 
 ping exchange.crystalweb.co.za -t 120
Ping that at the same time/while you're having the ping spike.
 
P

Pada

Executive Member
Joined
Feb 18, 2009
Messages
8,189
Johnatan56 said:
That third hop is bad, are you suffering from packet loss? Could you also ping exchange.crystalweb.co.za (155.239.255.250) for 20 seconds?
Code: 
 ping exchange.crystalweb.co.za -t 120
Ping that at the same time/while you're having the ping spike.
Click to expand...
@Johnatan56: There is definitely the possibility of congestion in my area too.

I'll ping that address from my WebAfrica account next time that I'm having a high ping in CS:GO. It would most likely remain low while my CS:GO ping is high. I'll also try ping with a large packet size. eg.
Code: 
ping exchange.crystalweb.co.za -l 1000
 
EasyUp Web Hosting

EasyUp Web Hosting

EasyUp Web Hosting
Company Rep
Joined
Mar 18, 2008
Messages
8,517
I had the same problem last night, but ignored it, because I thought the SEACOM repairs aren't done yet. Will check tonight and then test with a CW account...

Edit: Was playing PUBG, so international. Ping was around 260 to amazonaws.com...
 
C

COBUSNEL

Member
Joined
Feb 25, 2014
Messages
10
I have the same problem. I have been talking to webafrica support for over a week now. They also provided me with a test account, which caused the same problems. They sent Telkom out today to come and investigate the problem. The technician from telkom found no fault and told me the line is now stable.

I think it is time to move on away from Webafrica.
 
P

Pada

Executive Member
Joined
Feb 18, 2009
Messages
8,189
So I again had a high ping tonight at around 20:30 - 21:00, both on Afrihost and WebAfrica. It was much worse on Afrihost.

And yet again the ICMP ping was perfect on WebAfrica to the CS:GO server:
Code: 
C:\Users\Chris>tracert 155.133.238.162

Tracing route to 155.133.238.162 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.11.1
  2     *        *        *     Request timed out.
  3    23 ms    24 ms    24 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
  4    24 ms    23 ms    24 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    24 ms    23 ms    23 ms  196.35.115.136
  6    25 ms    24 ms    24 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
  7    24 ms    23 ms    27 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
  8    40 ms    39 ms    39 ms  168.209.100.101
  9    40 ms    40 ms    40 ms  196.26.0.61
 10    41 ms    45 ms    40 ms  197.97.118.82
 11    40 ms    41 ms    40 ms  xe-1-0-0-0.er-02-jnb.za.seacomnet.com [105.16.29.10]
 12    40 ms    40 ms    39 ms  105.22.42.58
 13    45 ms    44 ms    42 ms  192.168.210.49
 14    41 ms    39 ms    41 ms  155.133.238.162

Trace complete.

... and also the ping to exchange.crystalweb:
Code: 
ping exchange.crystalweb.co.za -l 1000 -n 20

Pinging exchange.crystalweb.co.za [155.239.255.250] with 1000 bytes of data:
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 32ms, Average = 31ms
 
M

moedawood

Senior Member
Joined
Apr 20, 2016
Messages
910
Pada said:
So I again had a high ping tonight at around 20:30 - 21:00, both on Afrihost and WebAfrica. It was much worse on Afrihost.

And yet again the ICMP ping was perfect on WebAfrica to the CS:GO server:
Code: 
C:\Users\Chris>tracert 155.133.238.162

Tracing route to 155.133.238.162 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.11.1
  2     *        *        *     Request timed out.
  3    23 ms    24 ms    24 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
  4    24 ms    23 ms    24 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    24 ms    23 ms    23 ms  196.35.115.136
  6    25 ms    24 ms    24 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
  7    24 ms    23 ms    27 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
  8    40 ms    39 ms    39 ms  168.209.100.101
  9    40 ms    40 ms    40 ms  196.26.0.61
 10    41 ms    45 ms    40 ms  197.97.118.82
 11    40 ms    41 ms    40 ms  xe-1-0-0-0.er-02-jnb.za.seacomnet.com [105.16.29.10]
 12    40 ms    40 ms    39 ms  105.22.42.58
 13    45 ms    44 ms    42 ms  192.168.210.49
 14    41 ms    39 ms    41 ms  155.133.238.162

Trace complete.

... and also the ping to exchange.crystalweb:
Code: 
ping exchange.crystalweb.co.za -l 1000 -n 20

Pinging exchange.crystalweb.co.za [155.239.255.250] with 1000 bytes of data:
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 32ms, Average = 31ms
Click to expand...

Wanted to do a comparison from a Telkom account.

Code: 
traceroute to 155.133.238.162 (155.133.238.162), 30 hops max, 40 byte packets
 1  * * *
 2  105.187.252.70 (105.187.252.70)  14.875 ms  15.941 ms  15.191 ms
 3  105.229.0.13 (105.229.0.13)  14.675 ms  14.565 ms  15.125 ms
 4  105.187.249.6 (105.187.249.6)  25.027 ms  26.057 ms  25.483 ms
 5  105.187.249.6 (105.187.249.6)  25.9 ms 105.187.249.242 (105.187.249.242)  25.989 ms 105.187.249.6 (105.187.249.6)  24.892 ms
 6  196-60-9-22.ixp.joburg (196.60.9.22)  27.946 ms  28.344 ms  26.963 ms
 7  192.168.210.49 (192.168.210.49)  27.23 ms  29.007 ms  29.899 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *

Getting this unfortunately.

Code: 
PING 155.239.255.250 (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=64 time=15.0 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=64 time=15.1 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=64 time=14.7 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=64 time=14.5 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=64 time=15.5 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=64 time=15.0 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=64 time=14.7 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=64 time=14.5 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=64 time=15.5 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=64 time=15.2 ms

--- 155.239.255.250 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 14.5/14.9/15.5 ms
 
K

KittyBot

New Member
Joined
May 26, 2017
Messages
2
Hi guys, I have the terrible instability in my ping also. The concept of congestion in my area is not possible as my neighbor on axxess has a clean and stable 4 ms at all times...

1 2 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 246 ms 195 ms 119 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134]
4 39 ms 7 ms 5 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
5 56 ms 6 ms 7 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 28 ms 9 ms 10 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 60 ms 7 ms 7 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 47 ms 8 ms 33 ms cloudflare.ixp.joburg [196.60.8.198]
9 5 ms 8 ms 10 ms 104.20.58.32

1 3 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 6 ms 7 ms cdsl1-rba-vl2253-ipc.ip.isnet.net [196.38.73.182]
4 12 ms 6 ms 6 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
5 5 ms 6 ms 3 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 74 ms 10 ms 11 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 68 ms 7 ms 6 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 59 ms 8 ms 11 ms cloudflare.ixp.joburg [196.60.8.198]
9 6 ms 12 ms 10 ms 104.20.57.32

C:\Users\KittyBot>ping mweb.co.za -l 1000 -n 20

Pinging mweb.co.za [196.2.63.110] with 1000 bytes of data:
Reply from 196.2.63.110: bytes=1000 time=107ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=110ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=94ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=108ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=101ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=88ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=27ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=28ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=28ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=24ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=23ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=25ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=22ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=25ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=25ms TTL=239

Ping statistics for 196.2.63.110:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 110ms, Average = 48ms

Not to mention Webafrica have the absolute worst tech support I have ever seen with a min waiting time of 30 minutes just for them to answer your call. In the day time i have a stable 4 ms but the moment it becomes night I get this ridiculous ping instability making my old adsl line look far better then fiber but then again as i said my neighbors ping never exceeds 4 on a different ISP. For the record I have a 20mbps 300gb capped line.
 
Johnatan56

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,957
Pada said:
So I again had a high ping tonight at around 20:30 - 21:00, both on Afrihost and WebAfrica. It was much worse on Afrihost.

And yet again the ICMP ping was perfect on WebAfrica to the CS:GO server:
Code: 
C:\Users\Chris>tracert 155.133.238.162

Tracing route to 155.133.238.162 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.11.1
  2     *        *        *     Request timed out.
  3    23 ms    24 ms    24 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
  4    24 ms    23 ms    24 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    24 ms    23 ms    23 ms  196.35.115.136
  6    25 ms    24 ms    24 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
  7    24 ms    23 ms    27 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
  8    40 ms    39 ms    39 ms  168.209.100.101
  9    40 ms    40 ms    40 ms  196.26.0.61
 10    41 ms    45 ms    40 ms  197.97.118.82
 11    40 ms    41 ms    40 ms  xe-1-0-0-0.er-02-jnb.za.seacomnet.com [105.16.29.10]
 12    40 ms    40 ms    39 ms  105.22.42.58
 13    45 ms    44 ms    42 ms  192.168.210.49
 14    41 ms    39 ms    41 ms  155.133.238.162

Trace complete.

... and also the ping to exchange.crystalweb:
Code: 
ping exchange.crystalweb.co.za -l 1000 -n 20

Pinging exchange.crystalweb.co.za [155.239.255.250] with 1000 bytes of data:
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=32ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63
Reply from 155.239.255.250: bytes=1000 time=31ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 32ms, Average = 31ms
Click to expand...
Maybe an incorrect shaping profile is targeting your CS:GO packets?
KittyBot said:
Hi guys, I have the terrible instability in my ping also. The concept of congestion in my area is not possible as my neighbor on axxess has a clean and stable 4 ms at all times...

1 2 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 246 ms 195 ms 119 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134]
4 39 ms 7 ms 5 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
5 56 ms 6 ms 7 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 28 ms 9 ms 10 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 60 ms 7 ms 7 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 47 ms 8 ms 33 ms cloudflare.ixp.joburg [196.60.8.198]
9 5 ms 8 ms 10 ms 104.20.58.32

1 3 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 6 ms 7 ms cdsl1-rba-vl2253-ipc.ip.isnet.net [196.38.73.182]
4 12 ms 6 ms 6 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
5 5 ms 6 ms 3 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 74 ms 10 ms 11 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 68 ms 7 ms 6 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 59 ms 8 ms 11 ms cloudflare.ixp.joburg [196.60.8.198]
9 6 ms 12 ms 10 ms 104.20.57.32

C:\Users\KittyBot>ping mweb.co.za -l 1000 -n 20

Pinging mweb.co.za [196.2.63.110] with 1000 bytes of data:
Reply from 196.2.63.110: bytes=1000 time=107ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=110ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=94ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=108ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=101ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=88ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=27ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=28ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=28ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=24ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=23ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=25ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=22ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=25ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=26ms TTL=239
Reply from 196.2.63.110: bytes=1000 time=25ms TTL=239

Ping statistics for 196.2.63.110:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 110ms, Average = 48ms

Not to mention Webafrica have the absolute worst tech support I have ever seen with a min waiting time of 30 minutes just for them to answer your call. In the day time i have a stable 4 ms but the moment it becomes night I get this ridiculous ping instability making my old adsl line look far better then fiber but then again as i said my neighbors ping never exceeds 4 on a different ISP. For the record I have a 20mbps 300gb capped line.
Click to expand...
Are you on WiFi or Ethernet?
 
H

HavocXphere

Honorary Master
Joined
Oct 19, 2007
Messages
33,155
Pada said:
...
Click to expand...
Didn't realise you're still around. That's a pleasant surprise.

Pada said:
@Johnatan56: There is definitely the possibility of congestion in my area too.
Click to expand...
nah then the ICMP would be screwed too. This is something different/new.

The fact that it happens at peak hours seems to suggest some kind of capacity constraint though.

What happens if you ping with a larger packet size & no fragmentation?

Pity DJ isn't around...he probably knows the answer.
 
K

KittyBot

New Member
Joined
May 26, 2017
Messages
2
Ethernet. I have never used wifi.

Heres the more weird part I get moments where my ping will skyrocket to 1k as if I had packet loss but net-graphs state zero packet loss. So in a game like overwatch i will be pushed around the same spot for 3 seconds and in dota my inputs stop registering for 3 seconds, just replaced the router so only the line can be at fault yet telkom finds no issues so only Webafricas rerouting can be at fault.

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\KittyBot>tracert webafrica.co.za

Tracing route to webafrica.co.za [104.20.58.32]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 81 ms 7 ms 7 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134]
4 59 ms 7 ms 6 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
5 44 ms 7 ms 7 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 55 ms 9 ms 11 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 49 ms 5 ms 5 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 71 ms 5 ms 7 ms cloudflare.ixp.joburg [196.60.8.198]
9 7 ms 7 ms 6 ms 104.20.58.32

Trace complete.

C:\Users\KittyBot>tracert webafrica.co.za

Tracing route to webafrica.co.za [104.20.58.32]
over a maximum of 30 hops:

1 2 ms 3 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 201 ms 206 ms 206 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134]
4 9 ms 7 ms 6 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
5 43 ms 6 ms 7 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 67 ms 14 ms 7 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 21 ms 6 ms 6 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 41 ms 7 ms 6 ms cloudflare.ixp.joburg [196.60.8.198]
9 5 ms 6 ms 6 ms 104.20.58.32

Trace complete.

C:\Users\KittyBot>tracert webafrica.co.za

Tracing route to webafrica.co.za [104.20.58.32]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 39 ms 6 ms 6 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134]
4 40 ms 6 ms 6 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
5 39 ms 4 ms 5 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 27 ms 8 ms 10 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 76 ms 4 ms 5 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
8 45 ms 6 ms 7 ms cloudflare.ixp.joburg [196.60.8.198]
9 6 ms 7 ms 7 ms 104.20.58.32

Trace complete.

C:\Users\KittyBot>time
The current time is: 19:43:47,50
Enter the new time:
 
Last edited:
WebAfrica Helper

WebAfrica Helper

Web Africa representative
Joined
Apr 2, 2012
Messages
2,175
Hi

Please DM us your contact details so we may investigate and help with this asap .

Thank you for your time.

Rafeeqah
 
WebAfrica Helper

WebAfrica Helper

Web Africa representative
Joined
Apr 2, 2012
Messages
2,175
Hi

Please DM us your contact details so we may investigate and help with this asap .

Thank you for your time.

Rafeeqah
 
T

TTLKaOs

New Member
Joined
Aug 9, 2014
Messages
2
Similar issue for the last couple of months already. Only happens with Overwatch you get stuck in the map and cannot move. So over this already no issues on Axxess though so it's not the server.
 
You must log in or register to reply here.
Top