It seems to have died down for me too since about 3 weeks ago. From having packetloss ALL THE TIME to mostly NOT having it now.To all the gamers and the people that can check their packetloss.
It seems to been fixed I checked on my teamspeak I went from 20% to 0.01% at night so it seems to be fine my side.
Could you guys confirm I need to give the tech some feedback
Cellc has a massive Packet loss issue on peak times on their network It goes up to 25% for me for local. I am not talking about tower related But the Core itselfI have problems download a file from Amazon S3. It's only 1.5MB, but it takes forever.
So I tried a few pings to S3. Some of them are fine, but others are horrible. For example:
PING s3-1-w.amazonaws.com (184.108.40.206) 56(84) bytes of data.
64 bytes from 220.127.116.11: icmp_seq=1 ttl=38 time=276 ms
64 bytes from 18.104.22.168: icmp_seq=2 ttl=38 time=433 ms
64 bytes from 22.214.171.124: icmp_seq=4 ttl=38 time=272 ms
64 bytes from 126.96.36.199: icmp_seq=8 ttl=38 time=339 ms
64 bytes from 188.8.131.52: icmp_seq=9 ttl=38 time=361 ms
64 bytes from 184.108.40.206: icmp_seq=12 ttl=38 time=418 ms
64 bytes from 220.127.116.11: icmp_seq=13 ttl=38 time=387 ms
--- s3-1-w.amazonaws.com ping statistics ---
15 packets transmitted, 7 received, 53% packet loss, time 23345ms
rtt min/avg/max/mdev = 272.902/355.819/433.520/59.171 ms
The tests at https://cloudharmony.com/speedtest-for-aws:s3 also fail.
And I was also unable to browse / search Giphy.com
Then I reconnected with Telkom LTE and everything worked (the download, the ping, the test and giphy.com).
Well something is still wrong peak times . Two people sitting on teamspeak using 3g one using LTE. Both users on cellc :Ping test had been discontinued and I can understand why: the traditional way for routers to handle congestion is to discard packets. Newer routers may have plenty of RAM and buffer several seconds of data. If latency is several seconds, then the connection will just as useless as when there is massive packet loss.
My gut feel is that Cell C has a descent local network and international traffic is suffering. Because so much content is served locally (YouTube, Google etc), the problem is rarely noticeable.
But try making an international WhatsApp call. It only uses 44 Kbps of bandwidth, so Cell C should handle it with ease. But it's a horrible experience.
I wonder if it's possible to bypass some of problems with a local proxy server, e.g. running it at the office where you have a fibre connection.
heads up tonight try tracert google.co.zaThe infamous packetloss on Cell C is now back in full swing for me. I can only play on weekends now after 12AM using my Telkom 500GB.
Telkom: zero packetloss
MTN: zero packetloss
Vodacom: zero packetloss
I guess Cell C just wants to go against the grain.