20Mbps Webafrica Uncapped Fiber is UNUSABLE for Gaming (Overwatch)

Lope

Well-Known Member
Joined
Apr 19, 2007
Messages
467
#1
My 20Mbps Webafrica Uncapped Fiber is idle at the moment (I'm the only one connected and not doing any uploads/downloads)
here's some ping results of eu.battle.net
Code:
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=65 ttl=52 time=373 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=66 ttl=52 time=325 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=67 ttl=52 time=561 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=68 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=69 ttl=52 time=153 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=70 ttl=52 time=1016 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=71 ttl=52 time=476 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=73 ttl=52 time=510 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=75 ttl=52 time=1026 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=76 ttl=52 time=1005 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=77 ttl=52 time=584 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=79 ttl=52 time=513 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=80 ttl=52 time=205 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=81 ttl=52 time=652 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=82 ttl=52 time=677 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=83 ttl=52 time=732 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=84 ttl=52 time=216 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=85 ttl=52 time=268 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=86 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=87 ttl=52 time=199 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=88 ttl=52 time=266 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=89 ttl=52 time=387 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=90 ttl=52 time=308 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=91 ttl=52 time=390 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=92 ttl=52 time=396 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=93 ttl=52 time=1034 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=94 ttl=52 time=821 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=95 ttl=52 time=434 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=96 ttl=52 time=486 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=97 ttl=52 time=482 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=98 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=99 ttl=52 time=434 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=100 ttl=52 time=490 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=101 ttl=52 time=153 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=102 ttl=52 time=1027 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=103 ttl=52 time=603 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=104 ttl=52 time=1016 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=105 ttl=52 time=1003 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=106 ttl=52 time=1001 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=108 ttl=52 time=154 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=109 ttl=52 time=270 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=110 ttl=52 time=207 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=111 ttl=52 time=204 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=112 ttl=52 time=836 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=113 ttl=52 time=302 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=114 ttl=52 time=374 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=115 ttl=52 time=860 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=116 ttl=52 time=915 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=117 ttl=52 time=909 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=118 ttl=52 time=372 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=119 ttl=52 time=175 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=120 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=121 ttl=52 time=944 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=122 ttl=52 time=511 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=123 ttl=52 time=1025 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=124 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=125 ttl=52 time=1003 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=126 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=127 ttl=52 time=373 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=129 ttl=52 time=152 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=130 ttl=52 time=312 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=131 ttl=52 time=170 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=132 ttl=52 time=612 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=133 ttl=52 time=268 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=134 ttl=52 time=242 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=135 ttl=52 time=308 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=136 ttl=52 time=802 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=137 ttl=52 time=1016 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=138 ttl=52 time=841 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=139 ttl=52 time=293 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=140 ttl=52 time=528 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=141 ttl=52 time=156 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=142 ttl=52 time=1021 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=143 ttl=52 time=1001 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=144 ttl=52 time=475 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=145 ttl=52 time=206 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=146 ttl=52 time=481 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=147 ttl=52 time=1028 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=148 ttl=52 time=509 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=149 ttl=52 time=476 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=150 ttl=52 time=579 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=151 ttl=52 time=506 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=153 ttl=52 time=637 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=154 ttl=52 time=816 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=155 ttl=52 time=1008 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=156 ttl=52 time=1002 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=157 ttl=52 time=182 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=158 ttl=52 time=202 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=159 ttl=52 time=1029 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=160 ttl=52 time=898 ms
64 bytes from 185.60.115.40 (185.60.115.40): icmp_seq=161 ttl=52 time=269 ms
It has been like this all morning.
Ping to my router is low and stable.

I see they are having Fiber outages at the moment, but my area is not listed as having any problem.
https://www.webafrica.co.za/networkstatus/

On their product page they list their 20Mbps Uncapped Fiber as being able to handle 2 Devices for gaming. It can't even handle a ping. It can't even handle 1 device for gaming.
 
Last edited:

Flamer283

Well-Known Member
Joined
Aug 28, 2014
Messages
221
#2
I'm in the exact same boat as you. I've noticed these high pings in overwatch for months now. Who is your fibre provider?
 

Aardvark

Well-Known Member
Joined
Nov 19, 2005
Messages
349
#3
Hi
Here is my pings:

Pinging 185.60.115.40 with 32 bytes of data:
Reply from 185.60.115.40: bytes=32 time=158ms TTL=51
Reply from 185.60.115.40: bytes=32 time=157ms TTL=51
Reply from 185.60.115.40: bytes=32 time=154ms TTL=51
Reply from 185.60.115.40: bytes=32 time=159ms TTL=51

This is webafrica with vumatel.
 

Lope

Well-Known Member
Joined
Apr 19, 2007
Messages
467
#4
My traceroute looks like this (on windows it's called tracert)
Code:
$ traceroute 185.60.115.40
traceroute to 185.60.115.40 (185.60.115.40), 30 hops max, 60 byte packets
1  _gateway (192.168.x.y)  1.521 ms  1.496 ms  2.242 ms
2  196-214-1-1.broadband.is (196.214.1.1)  7.270 ms  7.337 ms *
3  196.38.77.99 (196.38.77.99)  7.347 ms  7.400 ms  7.495 ms
4  196.38.77.98 (196.38.77.98)  14.654 ms  14.736 ms  14.783 ms
5  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12)  17.775 ms  17.835 ms  17.945 ms
6  mi-za-cpt-p7-te0-0-0-0.ip.isnet.net (168.209.6.12)  15.771 ms 168.209.201.28 (168.209.201.28)  151.457 ms core1b-dock-ten-0-4-0-0sub8.ip.isnet.net (168.209.246.65)  152.318 ms
7  168.209.201.28 (168.209.201.28)  149.494 ms  149.966 ms *
8  * * *
9  * * *
If I run `mtr 185.60.115.40` mtr_185.60.115.40.png
Then packet loss and ping goes up sharply at 195.66.226.234 which is in JHB owned by DimensionData
https://www.ip2location.com/168.209.201.28

The next jump is 195.66.226.234 which is in UK.
 

Lope

Well-Known Member
Joined
Apr 19, 2007
Messages
467
#5
Wow Aardvark, some very nice pings there.

The issue is definitely Webafrica 20mbps fibre.
When I ping from Vodacom LTE I get a stable 195-202ms ping.

Interestingly 10Mbps Webafrica business ADSL is stable also
Code:
# ping eu.battle.net
PING eu.battle.net (185.60.115.40) 56(84) bytes of data.
64 bytes from 185.60.115.40: icmp_seq=1 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=2 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=3 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=4 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=5 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=6 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=7 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=8 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=9 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=10 ttl=52 time=215 ms
64 bytes from 185.60.115.40: icmp_seq=11 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=12 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=13 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=14 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=15 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=16 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=17 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=18 ttl=52 time=182 ms
64 bytes from 185.60.115.40: icmp_seq=19 ttl=52 time=182 ms
@Aardvark @Flamer283 I don't know which fiber network it is. How can I tell?
 
Last edited:

cantankerous

Active Member
Joined
Oct 23, 2018
Messages
35
#6
My traceroute looks like this (on windows it's called tracert)
Code:
$ traceroute 185.60.115.40
traceroute to 185.60.115.40 (185.60.115.40), 30 hops max, 60 byte packets
1  _gateway (192.168.x.y)  1.521 ms  1.496 ms  2.242 ms
2  196-214-1-1.broadband.is (196.214.1.1)  7.270 ms  7.337 ms *
3  196.38.77.99 (196.38.77.99)  7.347 ms  7.400 ms  7.495 ms
4  196.38.77.98 (196.38.77.98)  14.654 ms  14.736 ms  14.783 ms
5  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12)  17.775 ms  17.835 ms  17.945 ms
6  mi-za-cpt-p7-te0-0-0-0.ip.isnet.net (168.209.6.12)  15.771 ms 168.209.201.28 (168.209.201.28)  151.457 ms core1b-dock-ten-0-4-0-0sub8.ip.isnet.net (168.209.246.65)  152.318 ms
7  168.209.201.28 (168.209.201.28)  149.494 ms  149.966 ms *
8  * * *
9  * * *
If I run `mtr 185.60.115.40` View attachment 654796
Then packet loss and ping goes up sharply at 195.66.226.234 which is in JHB owned by DimensionData
https://www.ip2location.com/168.209.201.28

The next jump is 195.66.226.234 which is in UK.
You're getting 5.5% loss to your own gateway. Was this test using a LAN cable? You definitely have a local issue.
 

Lope

Well-Known Member
Joined
Apr 19, 2007
Messages
467
#7
You're getting 5.5% loss to your own gateway. Was this test using a LAN cable? You definitely have a local issue.
Unfortunately I have to use Wifi in my current location.
Connection strength varies by time of day.
The wifi is actually good enough to game on. I much prefer a LAN cable, of course.


Code:
PING 192.168.x.y (192.168.x.y) 56(84) bytes of data.
64 bytes from 192.168.x.y: icmp_seq=1 ttl=64 time=8.59 ms
64 bytes from 192.168.x.y: icmp_seq=2 ttl=64 time=22.8 ms
64 bytes from 192.168.x.y: icmp_seq=3 ttl=64 time=x.y5 ms
64 bytes from 192.168.x.y: icmp_seq=4 ttl=64 time=x.y6 ms
64 bytes from 192.168.x.y: icmp_seq=5 ttl=64 time=3.82 ms
64 bytes from 192.168.x.y: icmp_seq=6 ttl=64 time=12.3 ms
64 bytes from 192.168.x.y: icmp_seq=7 ttl=64 time=6.96 ms
64 bytes from 192.168.x.y: icmp_seq=8 ttl=64 time=1.25 ms
64 bytes from 192.168.x.y: icmp_seq=9 ttl=64 time=1.21 ms
64 bytes from 192.168.x.y: icmp_seq=10 ttl=64 time=35.5 ms
64 bytes from 192.168.x.y: icmp_seq=11 ttl=64 time=57.1 ms
64 bytes from 192.168.x.y: icmp_seq=12 ttl=64 time=39.9 ms
64 bytes from 192.168.x.y: icmp_seq=13 ttl=64 time=x.y8 ms
64 bytes from 192.168.x.y: icmp_seq=14 ttl=64 time=x.y2 ms
64 bytes from 192.168.x.y: icmp_seq=15 ttl=64 time=1.00 ms
64 bytes from 192.168.x.y: icmp_seq=16 ttl=64 time=1.44 ms
64 bytes from 192.168.x.y: icmp_seq=17 ttl=64 time=18.5 ms
64 bytes from 192.168.x.y: icmp_seq=18 ttl=64 time=13.0 ms
64 bytes from 192.168.x.y: icmp_seq=19 ttl=64 time=27.9 ms
64 bytes from 192.168.x.y: icmp_seq=20 ttl=64 time=23.0 ms
64 bytes from 192.168.x.y: icmp_seq=21 ttl=64 time=29.7 ms
64 bytes from 192.168.x.y: icmp_seq=22 ttl=64 time=31.9 ms
64 bytes from 192.168.x.y: icmp_seq=23 ttl=64 time=1.21 ms
64 bytes from 192.168.x.y: icmp_seq=24 ttl=64 time=x.y5 ms
64 bytes from 192.168.x.y: icmp_seq=25 ttl=64 time=1.66 ms
64 bytes from 192.168.x.y: icmp_seq=26 ttl=64 time=3.42 ms
64 bytes from 192.168.x.y: icmp_seq=27 ttl=64 time=x.y4 ms
64 bytes from 192.168.x.y: icmp_seq=28 ttl=64 time=x.y2 ms
64 bytes from 192.168.x.y: icmp_seq=29 ttl=64 time=1.48 ms
64 bytes from 192.168.x.y: icmp_seq=30 ttl=64 time=1.44 ms
64 bytes from 192.168.x.y: icmp_seq=31 ttl=64 time=35.4 ms
64 bytes from 192.168.x.y: icmp_seq=32 ttl=64 time=1.53 ms
64 bytes from 192.168.x.y: icmp_seq=33 ttl=64 time=x.y1 ms
64 bytes from 192.168.x.y: icmp_seq=34 ttl=64 time=1.33 ms
64 bytes from 192.168.x.y: icmp_seq=35 ttl=64 time=x.y0 ms
64 bytes from 192.168.x.y: icmp_seq=36 ttl=64 time=1.05 ms
64 bytes from 192.168.x.y: icmp_seq=37 ttl=64 time=1.32 ms
64 bytes from 192.168.x.y: icmp_seq=38 ttl=64 time=x.y0 ms
64 bytes from 192.168.x.y: icmp_seq=39 ttl=64 time=1.34 ms
64 bytes from 192.168.x.y: icmp_seq=40 ttl=64 time=1.26 ms
64 bytes from 192.168.x.y: icmp_seq=41 ttl=64 time=3.35 ms
64 bytes from 192.168.x.y: icmp_seq=42 ttl=64 time=1.09 ms
64 bytes from 192.168.x.y: icmp_seq=43 ttl=64 time=1.84 ms
64 bytes from 192.168.x.y: icmp_seq=44 ttl=64 time=1.08 ms
64 bytes from 192.168.x.y: icmp_seq=45 ttl=64 time=1.24 ms
64 bytes from 192.168.x.y: icmp_seq=46 ttl=64 time=1.08 ms
64 bytes from 192.168.x.y: icmp_seq=47 ttl=64 time=x.y3 ms
64 bytes from 192.168.x.y: icmp_seq=48 ttl=64 time=1.42 ms
64 bytes from 192.168.x.y: icmp_seq=49 ttl=64 time=1.27 ms
64 bytes from 192.168.x.y: icmp_seq=50 ttl=64 time=3.88 ms
64 bytes from 192.168.x.y: icmp_seq=51 ttl=64 time=1.03 ms
64 bytes from 192.168.x.y: icmp_seq=52 ttl=64 time=x.y8 ms
64 bytes from 192.168.x.y: icmp_seq=53 ttl=64 time=55.5 ms
64 bytes from 192.168.x.y: icmp_seq=54 ttl=64 time=49.8 ms
64 bytes from 192.168.x.y: icmp_seq=55 ttl=64 time=43.9 ms
64 bytes from 192.168.x.y: icmp_seq=56 ttl=64 time=58.7 ms
64 bytes from 192.168.x.y: icmp_seq=57 ttl=64 time=55.1 ms
64 bytes from 192.168.x.y: icmp_seq=58 ttl=64 time=5x.y ms
64 bytes from 192.168.x.y: icmp_seq=59 ttl=64 time=45.6 ms
64 bytes from 192.168.x.y: icmp_seq=60 ttl=64 time=40.0 ms
64 bytes from 192.168.x.y: icmp_seq=62 ttl=64 time=9.26 ms
64 bytes from 192.168.x.y: icmp_seq=63 ttl=64 time=1.24 ms
64 bytes from 192.168.x.y: icmp_seq=64 ttl=64 time=54.2 ms
64 bytes from 192.168.x.y: icmp_seq=65 ttl=64 time=9.19 ms
64 bytes from 192.168.x.y: icmp_seq=66 ttl=64 time=4.38 ms
64 bytes from 192.168.x.y: icmp_seq=67 ttl=64 time=1.45 ms
64 bytes from 192.168.x.y: icmp_seq=68 ttl=64 time=1.26 ms
64 bytes from 192.168.x.y: icmp_seq=69 ttl=64 time=1.33 ms
64 bytes from 192.168.x.y: icmp_seq=70 ttl=64 time=54.3 ms
64 bytes from 192.168.x.y: icmp_seq=71 ttl=64 time=1.05 ms
64 bytes from 192.168.x.y: icmp_seq=72 ttl=64 time=1.58 ms
64 bytes from 192.168.x.y: icmp_seq=73 ttl=64 time=54.6 ms
64 bytes from 192.168.x.y: icmp_seq=74 ttl=64 time=54.8 ms
64 bytes from 192.168.x.y: icmp_seq=75 ttl=64 time=46.7 ms
64 bytes from 192.168.x.y: icmp_seq=76 ttl=64 time=25.3 ms
64 bytes from 192.168.x.y: icmp_seq=77 ttl=64 time=19.5 ms
64 bytes from 192.168.x.y: icmp_seq=78 ttl=64 time=13.8 ms
64 bytes from 192.168.x.y: icmp_seq=79 ttl=64 time=7.98 ms
64 bytes from 192.168.x.y: icmp_seq=81 ttl=64 time=1.41 ms
64 bytes from 192.168.x.y: icmp_seq=82 ttl=64 time=1.47 ms
64 bytes from 192.168.x.y: icmp_seq=83 ttl=64 time=1.07 ms
64 bytes from 192.168.x.y: icmp_seq=84 ttl=64 time=52.7 ms
64 bytes from 192.168.x.y: icmp_seq=85 ttl=64 time=47.9 ms
64 bytes from 192.168.x.y: icmp_seq=86 ttl=64 time=47.1 ms
64 bytes from 192.168.x.y: icmp_seq=87 ttl=64 time=46.7 ms
64 bytes from 192.168.x.y: icmp_seq=88 ttl=64 time=42.0 ms
64 bytes from 192.168.x.y: icmp_seq=89 ttl=64 time=37.9 ms
64 bytes from 192.168.x.y: icmp_seq=90 ttl=64 time=33.1 ms
64 bytes from 192.168.x.y: icmp_seq=91 ttl=64 time=28.9 ms
64 bytes from 192.168.x.y: icmp_seq=92 ttl=64 time=25.0 ms
64 bytes from 192.168.x.y: icmp_seq=93 ttl=64 time=20.7 ms
64 bytes from 192.168.x.y: icmp_seq=94 ttl=64 time=18.8 ms
64 bytes from 192.168.x.y: icmp_seq=95 ttl=64 time=19.4 ms
64 bytes from 192.168.x.y: icmp_seq=96 ttl=64 time=11.5 ms
64 bytes from 192.168.x.y: icmp_seq=97 ttl=64 time=5.86 ms
64 bytes from 192.168.x.y: icmp_seq=98 ttl=64 time=1.52 ms
64 bytes from 192.168.x.y: icmp_seq=99 ttl=64 time=2.64 ms
64 bytes from 192.168.x.y: icmp_seq=100 ttl=64 time=x.y1 ms
^C
--- 192.168.x.y ping statistics ---
100 packets transmitted, 98 received, 2% packet loss, time 99156ms
rtt min/avg/max/mdev = 1.002/16.628/58.776/19.527 ms
 

cantankerous

Active Member
Joined
Oct 23, 2018
Messages
35
#8
Unfortunately I have to use Wifi in my current location.
Connection strength varies by time of day.
The wifi is actually good enough to game on. I much prefer a LAN cable, of course.


Code:
PING 192.168.x.y (192.168.x.y) 56(84) bytes of data.
64 bytes from 192.168.x.y: icmp_seq=1 ttl=64 time=8.59 ms
64 bytes from 192.168.x.y: icmp_seq=2 ttl=64 time=22.8 ms
64 bytes from 192.168.x.y: icmp_seq=3 ttl=64 time=x.y5 ms
64 bytes from 192.168.x.y: icmp_seq=4 ttl=64 time=x.y6 ms
64 bytes from 192.168.x.y: icmp_seq=5 ttl=64 time=3.82 ms
64 bytes from 192.168.x.y: icmp_seq=6 ttl=64 time=12.3 ms
64 bytes from 192.168.x.y: icmp_seq=7 ttl=64 time=6.96 ms
64 bytes from 192.168.x.y: icmp_seq=8 ttl=64 time=1.25 ms
64 bytes from 192.168.x.y: icmp_seq=9 ttl=64 time=1.21 ms
64 bytes from 192.168.x.y: icmp_seq=10 ttl=64 time=35.5 ms
64 bytes from 192.168.x.y: icmp_seq=11 ttl=64 time=57.1 ms
64 bytes from 192.168.x.y: icmp_seq=12 ttl=64 time=39.9 ms
64 bytes from 192.168.x.y: icmp_seq=13 ttl=64 time=x.y8 ms
64 bytes from 192.168.x.y: icmp_seq=14 ttl=64 time=x.y2 ms
64 bytes from 192.168.x.y: icmp_seq=15 ttl=64 time=1.00 ms
64 bytes from 192.168.x.y: icmp_seq=16 ttl=64 time=1.44 ms
64 bytes from 192.168.x.y: icmp_seq=17 ttl=64 time=18.5 ms
64 bytes from 192.168.x.y: icmp_seq=18 ttl=64 time=13.0 ms
64 bytes from 192.168.x.y: icmp_seq=19 ttl=64 time=27.9 ms
64 bytes from 192.168.x.y: icmp_seq=20 ttl=64 time=23.0 ms
64 bytes from 192.168.x.y: icmp_seq=21 ttl=64 time=29.7 ms
64 bytes from 192.168.x.y: icmp_seq=22 ttl=64 time=31.9 ms
64 bytes from 192.168.x.y: icmp_seq=23 ttl=64 time=1.21 ms
64 bytes from 192.168.x.y: icmp_seq=24 ttl=64 time=x.y5 ms
64 bytes from 192.168.x.y: icmp_seq=25 ttl=64 time=1.66 ms
64 bytes from 192.168.x.y: icmp_seq=26 ttl=64 time=3.42 ms
64 bytes from 192.168.x.y: icmp_seq=27 ttl=64 time=x.y4 ms
64 bytes from 192.168.x.y: icmp_seq=28 ttl=64 time=x.y2 ms
64 bytes from 192.168.x.y: icmp_seq=29 ttl=64 time=1.48 ms
64 bytes from 192.168.x.y: icmp_seq=30 ttl=64 time=1.44 ms
64 bytes from 192.168.x.y: icmp_seq=31 ttl=64 time=35.4 ms
64 bytes from 192.168.x.y: icmp_seq=32 ttl=64 time=1.53 ms
64 bytes from 192.168.x.y: icmp_seq=33 ttl=64 time=x.y1 ms
64 bytes from 192.168.x.y: icmp_seq=34 ttl=64 time=1.33 ms
64 bytes from 192.168.x.y: icmp_seq=35 ttl=64 time=x.y0 ms
64 bytes from 192.168.x.y: icmp_seq=36 ttl=64 time=1.05 ms
64 bytes from 192.168.x.y: icmp_seq=37 ttl=64 time=1.32 ms
64 bytes from 192.168.x.y: icmp_seq=38 ttl=64 time=x.y0 ms
64 bytes from 192.168.x.y: icmp_seq=39 ttl=64 time=1.34 ms
64 bytes from 192.168.x.y: icmp_seq=40 ttl=64 time=1.26 ms
64 bytes from 192.168.x.y: icmp_seq=41 ttl=64 time=3.35 ms
64 bytes from 192.168.x.y: icmp_seq=42 ttl=64 time=1.09 ms
64 bytes from 192.168.x.y: icmp_seq=43 ttl=64 time=1.84 ms
64 bytes from 192.168.x.y: icmp_seq=44 ttl=64 time=1.08 ms
64 bytes from 192.168.x.y: icmp_seq=45 ttl=64 time=1.24 ms
64 bytes from 192.168.x.y: icmp_seq=46 ttl=64 time=1.08 ms
64 bytes from 192.168.x.y: icmp_seq=47 ttl=64 time=x.y3 ms
64 bytes from 192.168.x.y: icmp_seq=48 ttl=64 time=1.42 ms
64 bytes from 192.168.x.y: icmp_seq=49 ttl=64 time=1.27 ms
64 bytes from 192.168.x.y: icmp_seq=50 ttl=64 time=3.88 ms
64 bytes from 192.168.x.y: icmp_seq=51 ttl=64 time=1.03 ms
64 bytes from 192.168.x.y: icmp_seq=52 ttl=64 time=x.y8 ms
64 bytes from 192.168.x.y: icmp_seq=53 ttl=64 time=55.5 ms
64 bytes from 192.168.x.y: icmp_seq=54 ttl=64 time=49.8 ms
64 bytes from 192.168.x.y: icmp_seq=55 ttl=64 time=43.9 ms
64 bytes from 192.168.x.y: icmp_seq=56 ttl=64 time=58.7 ms
64 bytes from 192.168.x.y: icmp_seq=57 ttl=64 time=55.1 ms
64 bytes from 192.168.x.y: icmp_seq=58 ttl=64 time=5x.y ms
64 bytes from 192.168.x.y: icmp_seq=59 ttl=64 time=45.6 ms
64 bytes from 192.168.x.y: icmp_seq=60 ttl=64 time=40.0 ms
64 bytes from 192.168.x.y: icmp_seq=62 ttl=64 time=9.26 ms
64 bytes from 192.168.x.y: icmp_seq=63 ttl=64 time=1.24 ms
64 bytes from 192.168.x.y: icmp_seq=64 ttl=64 time=54.2 ms
64 bytes from 192.168.x.y: icmp_seq=65 ttl=64 time=9.19 ms
64 bytes from 192.168.x.y: icmp_seq=66 ttl=64 time=4.38 ms
64 bytes from 192.168.x.y: icmp_seq=67 ttl=64 time=1.45 ms
64 bytes from 192.168.x.y: icmp_seq=68 ttl=64 time=1.26 ms
64 bytes from 192.168.x.y: icmp_seq=69 ttl=64 time=1.33 ms
64 bytes from 192.168.x.y: icmp_seq=70 ttl=64 time=54.3 ms
64 bytes from 192.168.x.y: icmp_seq=71 ttl=64 time=1.05 ms
64 bytes from 192.168.x.y: icmp_seq=72 ttl=64 time=1.58 ms
64 bytes from 192.168.x.y: icmp_seq=73 ttl=64 time=54.6 ms
64 bytes from 192.168.x.y: icmp_seq=74 ttl=64 time=54.8 ms
64 bytes from 192.168.x.y: icmp_seq=75 ttl=64 time=46.7 ms
64 bytes from 192.168.x.y: icmp_seq=76 ttl=64 time=25.3 ms
64 bytes from 192.168.x.y: icmp_seq=77 ttl=64 time=19.5 ms
64 bytes from 192.168.x.y: icmp_seq=78 ttl=64 time=13.8 ms
64 bytes from 192.168.x.y: icmp_seq=79 ttl=64 time=7.98 ms
64 bytes from 192.168.x.y: icmp_seq=81 ttl=64 time=1.41 ms
64 bytes from 192.168.x.y: icmp_seq=82 ttl=64 time=1.47 ms
64 bytes from 192.168.x.y: icmp_seq=83 ttl=64 time=1.07 ms
64 bytes from 192.168.x.y: icmp_seq=84 ttl=64 time=52.7 ms
64 bytes from 192.168.x.y: icmp_seq=85 ttl=64 time=47.9 ms
64 bytes from 192.168.x.y: icmp_seq=86 ttl=64 time=47.1 ms
64 bytes from 192.168.x.y: icmp_seq=87 ttl=64 time=46.7 ms
64 bytes from 192.168.x.y: icmp_seq=88 ttl=64 time=42.0 ms
64 bytes from 192.168.x.y: icmp_seq=89 ttl=64 time=37.9 ms
64 bytes from 192.168.x.y: icmp_seq=90 ttl=64 time=33.1 ms
64 bytes from 192.168.x.y: icmp_seq=91 ttl=64 time=28.9 ms
64 bytes from 192.168.x.y: icmp_seq=92 ttl=64 time=25.0 ms
64 bytes from 192.168.x.y: icmp_seq=93 ttl=64 time=20.7 ms
64 bytes from 192.168.x.y: icmp_seq=94 ttl=64 time=18.8 ms
64 bytes from 192.168.x.y: icmp_seq=95 ttl=64 time=19.4 ms
64 bytes from 192.168.x.y: icmp_seq=96 ttl=64 time=11.5 ms
64 bytes from 192.168.x.y: icmp_seq=97 ttl=64 time=5.86 ms
64 bytes from 192.168.x.y: icmp_seq=98 ttl=64 time=1.52 ms
64 bytes from 192.168.x.y: icmp_seq=99 ttl=64 time=2.64 ms
64 bytes from 192.168.x.y: icmp_seq=100 ttl=64 time=x.y1 ms
^C
--- 192.168.x.y ping statistics ---
100 packets transmitted, 98 received, 2% packet loss, time 99156ms
rtt min/avg/max/mdev = 1.002/16.628/58.776/19.527 ms
You're going to need to test with a cable... The MTR results you sent there point to your LAN being the issue (first and last hop losses are identical).
 

neoprema

Expert Member
Joined
Jan 12, 2016
Messages
1,995
#9
I gave up with Webafrica ages ago. Its rubbish and their support is even worse...

I had people in the same complex as me on 20mbps with other ISPs and my 50mbps Fibre was downloading from the same websites at half their speed..
 

fundutzi

Well-Known Member
Joined
May 18, 2010
Messages
264
#10
Do not blame the ISPs.
We keep a cool head, look at the facts/ data, then we conclude.
More than 95% of issues in this world occur on the local PC or link form local PC to whatever, say the baboon.
This is set in stone.

Ping does not mean much without knowing:
a. how much data is being sent/ received
b. over what type of link.

Lope, to solve your problem.
a. Link with a cable to router/ modem.
=> Do not Torrent/ newsgroup and have other major downloads running from your network.
b. Now run your pings or path pings with whatever tool you want.
If still poor. Check how much data is passing through your link.

c. Since your ping clearly showed you have packet loss. This mean of of two things:
i. You link with some utter poor manner from PC to local router.
ii. And / or, You download / upload a lot of data to web.
iii. Since ii is quite possible, you may be throttled.
 

cavedog

Honorary Master
Joined
Oct 19, 2007
Messages
12,862
#11
Would be interesting to see how the latency changes once Webafrica switches people to their own network.
 

cavedog

Honorary Master
Joined
Oct 19, 2007
Messages
12,862
#13
My brother had Webafrica Fibre. The network was terrible. Speeds were never great. Lucky he moved ISP's and is much happier
Yeah it's internet solutions. Never been a big fan of that network but hey webafrica is getting their own network so maybe it will be better who knows.
 
Top