I think it is easy to replicate the packet loss and latency on Afrihost's network.
So using my free 1GB Afrihost account, I have a monitoring server at home, that specifically tests the IPC links (Cape Town).
A traceroute look like this:
Code:
[root@dl ~]# traceroute -I 105.237.67.65
traceroute to 105.237.67.65 (105.237.67.65), 30 hops max, 60 byte packets
1 router.heaven.za.net (10.0.0.1) 1.940 ms 1.911 ms 1.906 ms
2 * * *
3 41.181.53.149 (41.181.53.149) 176.918 ms 178.052 ms 179.473 ms
4 ipc-recieve-tb-1a.mtnbusiness.net (41.181.53.150) 154.864 ms 155.962 ms 157.036 ms
5 tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 120.128 ms 121.341 ms 123.098 ms
6 qux--tb-dca-2.za-b.za.mtnbusiness.net (41.181.184.31) 187.657 ms 185.998 ms 187.177 ms
7 41.181.223.221 (41.181.223.221) 24.211 ms 7.180 ms 7.792 ms
8 105-237-67-65-esr-lo.mtnbusiness.co.za (105.237.67.65) 131.403 ms 127.567 ms 127.016 m
ps. That latency is not my exchange, it is the IPC links, because the same graphs for other ISPs on my line is perfectly fine. Right now for some reason latency on cape town IPCs for Afrihost.
Either way, to explain what happen above:
I do a traceroute to the IP address assigned to the BRAS or BNG in my case, as I was moved over to an Alcatel router instead of a Cisco one on Telkom's side.
1. DSL router
2. BRAS/BNG not pingable with BNG
3. Afrihost IPC-up-something
4. Afrihost IPC-up-something
5. Afrihost router
6. Afrihost IPC-down-something
7. Afrihost IPC-down-something
8. Afrihost IP address on Telkom BRAS/BNG
How does it work that a packet traverses both direction of the IPC links in a single trace? Easy. Telkom IPC makes use of half-duplex MPLS vpn.
Here are the graphs.
Right now, high latency:
View attachment 197070
Earlier this week, normal latency high packet loss:
View attachment 197072
That is some very good information, to pin point exactly where there is packet loss, that the guys notice in CS:GO. Look no further than IPCs. At least in Cape Town.