Afrihost - Pure Fibre Feedback Thread

[AfriFella]

The best IP to test and see the difference is the official overwatch/battle.net IP if you are looking for 1 IP to test.

IP:185.60.112.157

Here is my trace route to the official overwatch/battle.net

tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 3 ms 2 ms 4 ms cadenex.net.afrihost.co.za [169.1.1.238]
2 3 ms 2 ms 2 ms 169-1-5-76.ip.afrihost.co.za [169.1.5.76]
3 4 ms 3 ms 2 ms 154.73.187.252
4 4 ms 3 ms 3 ms 77.246.59.82
5 158 ms 157 ms 158 ms be-20.lza-p4-jhb.liquidtelecom.net [41.60.135.92]
6 158 ms 158 ms 158 ms te-0-1-0-7.lfr-pe1-mrs.liquidtelecom.net [5.11.10.250]
7 187 ms 185 ms 185 ms 80.249.208.83
8 184 ms 186 ms 184 ms ae1-br01-eqam1.as57976.net [137.221.78.33]
9 186 ms 184 ms 184 ms et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
10 187 ms 184 ms 184 ms 185.60.112.157

Trace complete.

 

[moms]

i don't download, just doing it to illustrate the kodi/RD problem.

I meant you can test with IDM to see if your connection is the same ,

 

[AfriFella]

Look at the results by SeeYou without vpn and compare it to mine.

Afrihost - Pure Fibre Feedback Thread

Complaining about the same thing but Afrihost does not want to change the router to a different model. Have made several attempts at convincing their support that it is an issue, but to no avail. We are still looking into this, there are a few variables to consider before we can decide to...

mybroadband.co.za

Afrihost - Pure Fibre Feedback Thread

@AfriFella Overwatch traceroute: Afrihost: IP:185.60.112.157 |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host -...

mybroadband.co.za

I have looked at the results, it is clear that your latency is much better than @Seeyou

I will discuss this with our GM and give you guys feedback later

 

[AfriFella]

Ditto. I am chatting privateley to @AfriFella for the past week supplying traceroutes upon traceroutes and looking here in the actual thread it seems like the same thing.

Is anything going to get done? I was told the latency on the last liquidtelecom hop shows a routing issue on their side. I am unable to stream twitch higher than 160p on 50/50mbps connection which is just unacceptable.

We have been investigating this issue since last week. It is challenging because we are not able to replicate the issue. I am able to stream on 1080p with no issues. However, I do understand that there is a buffering issue and I am still investigating.

 

[wingnut771]

I meant you can test with IDM to see if your connection is the same ,

i'm sure multithread would improve the dead spot.

 

[Nibiru]

We have been investigating this issue since last week. It is challenging because we are not able to replicate the issue. I am able to stream on 1080p with no issues. However, I do understand that there is a buffering issue and I am still investigating.

Hi, please see PMs ive sent you last night, and then also: frogfoot is doing maintenance in my area tonight form 9pm till 7am (i heard from a neighbor, no notifications form anyone) and confirmed it with frogfoot just now.

Perhaps you can check from your side if this might fix the issue? Its quite a long down time.

 

[Fjorko]

You are right about this, we would need several tests to multiple IP addresses to isolate the issue.

Hi @AfriFella , I don't mean to offend anyone, but you do realize that you guys ( as a company ) are starting to look like amateurs when your user base has to school you on how things should work right ? I know you are just the face of what goes on behind the scenes, but If I were you I'd rather go seek an accurate answer to questions asked on this forum before just saying things that you later have to correct yourself on.

It's clear that latency to EU ( and probably US ) is higher than your competitors, and although I'm no network expert, the issue here seems to be the way your provider routes your traffic.

If I was Gian I'd call some meetings and speak to the right people to see if this can be improved - especially for your clients that are gamers / streamers etc.

There is obviously more to this - i understand that, but if CISP can make a plan when their user base complains that latency is creeping up, then surely you guys can do the same ?

 

[AfriFella]

The funny part is, I made a ticket and started talking here on Mybb at the same time. The Mybb staff is fast and helpful (although nothing has actually been done) , while the support ticket staff replied to my ticket a week later, asking if this issue is still relevant.

What a total joke @Afrihost-Gian.

The support staff tells me not to contact Mybb or social and use live chat (almost always offline when i check it) or tickets instead, Mybb staff tells me not to talk to support but talk privately instead.

Meanwhile Jan Piere Wiet is paying R900 a month and cant even stream twitch. My Telkom throw away LTE sim performs 10x better on twitch than my fibre connection. Honestly baffled.

I admit that your experience with us has not been that good since you are not able to stream without buffering on twitch. I sincerely apologise for this, this is not what we wish for our clients.
Your download and upload speeds are great and consistent which means that this issue affects twitch only.

I suspect that the issue is related to distance to the twitch server but have not been able to prove this because most twitch users are not experiencing the issue, and your latency to twitch.tv is around 160ms which is good, this is why I am still investigating and talking to some twitch users about their experiences.

We have several support channels so that you can have the freedom to easily reach us.

I believe what the mybb staff said was;

 

[Seeyou]

These results show that your latency to the UK is 140ms with or without VPN, which is not bad.

You are right about this, we would need several tests to multiple IP addresses to isolate the issue.

I'm beginning to wonder if you're being purposely obtuse about this. I have posted multiple times, on multiple pages, with tests to multiple IP's, showing the same problem. I've said multiple times that traffic to London is not the problem - latency after leaving London to the rest of the EU is. I don't think you could possibly have missed that. Several people, from several cities, have posted the same tests, showing the same issue. Added latency of up to 50ms to other EU cities from London - where they should be 10-20ms at most.

Yet page after page you tell me "your latency to the UK is not bad" and "we need more accurate results" and "what about some other IPs" - are you just stalling? Forward all of these results to your NOC. I can't imagine they'd have any trouble duplicating the results themselves - I don't even think they'd need our MTR's or traceroutes to begin with - these are simple tests they could run themselves. I'm growing more frustrated by your responses and wondering if this issue is actually being investigated than waiting on a resolution.

 

[AfriFella]

Trace from my USG 1Gbps Network switch to 87.117.247.206 from Afrihost PF Account

traceroute to 87.117.247.206 (87.117.247.206), 30 hops max, 38 byte packets
1 USG (192.168.1.1) 0.818 ms 1.162 ms 1.259 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 27.761 ms 27.283 ms 29.675 ms
4 cpt-rx1.ip.adsl.co.za (169.1.5.94) 37.889 ms 29.082 ms 29.152 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 22.696 ms 22.181 ms 28.719 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 29.289 ms 28.649 ms 30.863 ms
7 te-0-0-0-7.luk-p1-tho.liquidtelecom.net (5.11.10.156) 170.757 ms te-0-0-0-15.luk-p1-tho.liquidtelecom.net (5.11.10.220) 173.555 ms te-0-0-0-12.luk-p1-tho.liquidtelecom.net (5.11.10.222) 172.562 ms
8 be-3.luk-pe1-tho.liquidtelecom.net (5.11.10.103) 171.480 ms 177.372 ms 178.322 ms
9 xe-0-1-1.0.luk-pr3-tho.liquidtelecom.net (5.11.10.183) 186.645 ms 168.710 ms 5.11.10.95.liquidtelecom.net (5.11.10.95) 172.792 ms
10 be20.asr01.ld5.as20860.net (195.66.226.230) 167.440 ms 169.996 ms 164.667 ms
11 be10.asr02.dc5.as20860.net (130.180.202.47) 178.112 ms 179.436 ms 175.396 ms
12 po4-30.bor2.dc5.as20860.net (212.84.162.156) 181.474 ms 179.054 ms 181.854 ms
13 e1-41.lea101.1uf.dc5.as20860.net (212.84.179.89) 174.887 ms e1-42.lea101.1uf.dc5.as20860.net (212.84.180.249) 176.599 ms e1-41.lea101.1uf.dc5.as20860.net (212.84.179.89) 168.243 ms
14 87.117.247.1 (87.117.247.1) 168.618 ms 169.676 ms 168.569 ms
15 87.117.247.206 (87.117.247.206) 168.120 ms 169.961 ms 170.184 ms

Test to same server from CISP account from same device

traceroute to 87.117.247.206 (87.117.247.206), 30 hops max, 38 byte packets
1 USG (192.168.1.1) 1.556 ms 1.660 ms 2.057 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 23.954 ms 23.175 ms 22.840 ms
4 192.168.11.6 (192.168.11.6) 20.099 ms 26.908 ms 26.468 ms
5 uwx-cust.coolideas.co.za (154.0.4.161) 32.614 ms 32.671 ms 26.538 ms
6 uvu-cust.coolideas.co.za (154.0.4.122) 166.437 ms 168.303 ms 167.799 ms
7 u102-cust.coolideas.co.za (154.0.5.18) 173.939 ms 171.994 ms 172.248 ms
8 be20.asr01.thn.as20860.net (195.66.224.207) 173.670 ms 169.631 ms 166.810 ms
9 be10.asr01.dc5.as20860.net (130.180.202.45) 161.474 ms 162.965 ms 167.836 ms
10 po2-30.bor2.dc5.as20860.net (212.84.162.158) 175.599 ms 173.058 ms 175.324 ms
11 e1-42.lea101.1uf.dc5.as20860.net (212.84.180.249) 169.519 ms e1-46.lea201.north.dc5.as20860.net (212.84.188.10) 167.120 ms 167.083 ms
12 87.117.247.1 (87.117.247.1) 169.636 ms 167.370 ms 169.116 ms
13 87.117.247.206 (87.117.247.206) 169.389 ms 167.583 ms 174.808 ms

You can see Hop 11 ( AH ) and hop 9 ( CISP ) has a diffs of about 17ms. To a gamer i assume this is the difference between a headshot and a shot in $ass.

I don't think 17ms would make much of a difference for gamers because it's negligible. A hop to hop comparison method won't give us enough information to conclude. Looking at the average round trip to 87.117.247.206 which is 170ms for both(AH and CISP) your connections, I don't see any evidence to support the perception that CISP has better latency, at least not in this case.

The best way to compare the latency on the 2 networks would be to perform a few traceroute tests during different times and sum up the results and compare the average round trip time. This is obviously very tedious which is why we never ask clients to for this.

 

[AfriFella]

Hi, please see PMs ive sent you last night, and then also: frogfoot is doing maintenance in my area tonight form 9pm till 7am (i heard from a neighbor, no notifications form anyone) and confirmed it with frogfoot just now.

Perhaps you can check from your side if this might fix the issue? Its quite a long down time.

Ok, I will check my PM's and reply to you shortly.

 

[wingnut771]

Here is my trace route to the official overwatch/battle.net

tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 3 ms 2 ms 4 ms cadenex.net.afrihost.co.za [169.1.1.238]
2 3 ms 2 ms 2 ms 169-1-5-76.ip.afrihost.co.za [169.1.5.76]
3 4 ms 3 ms 2 ms 154.73.187.252
4 4 ms 3 ms 3 ms 77.246.59.82
5 158 ms 157 ms 158 ms be-20.lza-p4-jhb.liquidtelecom.net [41.60.135.92]
6 158 ms 158 ms 158 ms te-0-1-0-7.lfr-pe1-mrs.liquidtelecom.net [5.11.10.250]
7 187 ms 185 ms 185 ms 80.249.208.83
8 184 ms 186 ms 184 ms ae1-br01-eqam1.as57976.net [137.221.78.33]
9 186 ms 184 ms 184 ms et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
10 187 ms 184 ms 184 ms 185.60.112.157

Trace complete.

There you go, you replicated the problem, please reduce ms by 20ms as that's how long it takes to get from UK to EU, not 187-158=29ms.

 

[luckystrike]

@AfriFella My trace route is almost exactly the same as yours. So i can show you the problem between good and bad routing.

Here is my Trace Route with Afrihost. As you can see its almost exactly the same as yours.
AFRIHOST:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| pfSense.localdomain - 0 | 17 | 17 | 0 | 11 | 14 | 14 |
| 169-1-23-193.ip.afrihost.joburg - 0 | 17 | 17 | 3 | 12 | 15 | 14 |
| 169-1-21-101.ip.afrihost.co.za - 0 | 17 | 17 | 3 | 3 | 3 | 3 |
| 154.73.187.252 - 0 | 17 | 17 | 3 | 3 | 4 | 4 |
| 77.246.59.82 - 0 | 16 | 16 | 3 | 4 | 13 | 4 |
| be-20.lza-p4-jhb.liquidtelecom.net - 0 | 16 | 16 | 157 | 158 | 169 | 158 |
|te-0-1-0-7.lfr-pe1-mrs.liquidtelecom.net - 0 | 16 | 16 | 157 | 158 | 170 | 157 |
| 80.249.208.83 - 0 | 16 | 16 | 184 | 198 | 228 | 186 |
| ae1-br02-eqam1.as57976.net - 0 | 16 | 16 | 183 | 196 | 239 | 195 |
| et-0-0-67-pe02-eqam1.as57976.net - 0 | 16 | 16 | 184 | 194 | 228 | 196 |
| 137.221.66.47 - 0 | 16 | 16 | 185 | 193 | 196 | 193 |
| 185.60.112.157 - 0 | 16 | 16 | 184 | 192 | 194 | 193 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )


If i then connect to Nordvpn in London: I get +-162 ms to my nordvpn server. That is already +- 5ms more than yours and mine on afrihost to london. As you can see the route from Nordvpn server to that Ip(185.60.112.157) is great. It sits at +- 8 ms from london to IP:185.60.112.157

Using Nordvpn in London:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.8.8.1 - 0 | 23 | 23 | 161 | 162 | 163 | 162 |
| 88.202.231.1.static.midphase.com - 0 | 23 | 23 | 162 | 166 | 220 | 172 |
| 88.202.187.181.static.midphase.com - 0 | 23 | 23 | 162 | 165 | 215 | 164 |
| 195.66.226.234 - 0 | 23 | 23 | 163 | 178 | 366 | 164 |
| 137.221.79.33 - 0 | 23 | 23 | 169 | 173 | 190 | 170 |
| 137.221.65.91 - 5 | 23 | 22 | 170 | 556 | 1581 | 188 |
| 137.221.78.73 - 0 | 22 | 22 | 169 | 176 | 223 | 170 |
| 185.60.112.157 - 0 | 22 | 22 | 169 | 171 | 180 | 171 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )

So thats the problem we sit with.

We have amazing ping/latency to london. But from london to this IP(185.60.112.157) cant be more than 10 ms if routing works great. Currently it sits at +- 30 as you can see in your own trace route.

I hope this helps to show the problem we have.

If i look at your trace route and you can get 158ms to london (ANd that is amazing btw from Gauteng) Then we must be able to get +- 165ms to that IP and not +- 185ms.

 

[Loppas]

@AfriFella We have amazing ping/latency to london. But from london to this IP(185.60.112.157) cant be more than 10 ms if routing works great. Currently it sits at +- 30 as you can see in your own trace route.

I pointed it out yesterday, but if you look at the names of the hops you can see its not actually going via london to that ip on AH, but via south of france (Marseille) and thats why theres a higher latency in this specific route, its taking the east coast cable to eu. If you try test the latency from that point its 27-29ms to germany.

 

[AfriFella]

I have looked at the results, it is clear that your latency is much better than @Seeyou

I will discuss this with our GM and give you guys feedback later

Thank you so much for the traceroute results @Loppas @Seeyou
I discussed the routing challenges with our GM and we concluded that our routing, especially in CT is not optimal. As a result, we have logged this with our upstream provider to optimize the routes.

I believe that this will resolve a few issues which the community has brought to our attention. There is no ETA but I will keep you guys informed.

 

[AfriFella]

I'm beginning to wonder if you're being purposely obtuse about this. I have posted multiple times, on multiple pages, with tests to multiple IP's, showing the same problem. I've said multiple times that traffic to London is not the problem - latency after leaving London to the rest of the EU is. I don't think you could possibly have missed that. Several people, from several cities, have posted the same tests, showing the same issue. Added latency of up to 50ms to other EU cities from London - where they should be 10-20ms at most.

Yet page after page you tell me "your latency to the UK is not bad" and "we need more accurate results" and "what about some other IPs" - are you just stalling? Forward all of these results to your NOC. I can't imagine they'd have any trouble duplicating the results themselves - I don't even think they'd need our MTR's or traceroutes to begin with - these are simple tests they could run themselves. I'm growing more frustrated by your responses and wondering if this issue is actually being investigated than waiting on a resolution.

I understand how frustrating this issue has been. I really do appreciate all the tests you forwarded to us. We have logged this issue with our upstream providers.

 

[AfriFella]

There you go, you replicated the problem, please reduce ms by 20ms as that's how long it takes to get from UK to EU, not 187-158=29ms.

Ok I understand your point of view. We have logged this issue with our upstream providers.

 

[AfriFella]

CISP -> 151.106.5.253

traceroute to 151.106.5.253 (151.106.5.253), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.532 ms 0.516 ms 0.578 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 27.317 ms 21.279 ms 27.292 ms
4 192.168.11.6 (192.168.11.6) 20.603 ms 20.648 ms 20.477 ms
5 154.0.4.162 (154.0.4.162) 20.713 ms 20.488 ms 20.495 ms
6 usi-cust.coolideas.co.za (154.0.4.2) 159.884 ms 166.035 ms 160.066 ms
7 v1000.core1.lon3.he.net (216.66.80.169) 165.999 ms 165.808 ms 165.799 ms
8 100ge14-1.core1.lon2.he.net (184.105.64.237) 188.603 ms 188.389 ms 188.218 ms
9 ae1.cr-sargas.lon1.core.heg.com (195.66.225.173) 166.192 ms 171.716 ms 165.783 ms
10 ae0.cr-merak.lon5.bb.godaddy.com (87.230.113.
1) 166.473 ms 161.561 ms 161.943 ms
11 ae0.cr-nunki.sxb1.bb.godaddy.com (87.230.113.3) 180.800 ms 180.666 ms 174.455 ms
12 gw-heg.newton.router.fr.velia.net (87.230.112.15) 180.723 ms 180.104 ms 186.027 ms
13 sxb13ahB.strasbourg.fr.velia.net (134.119.212.3) 202.553 ms 176.232 ms 187.004 ms
14 151.106.5.253 (151.106.5.253) 178.596 ms 181.086 ms 174.870 ms

CISP -> 85.195.114.189

traceroute to 85.195.114.189 (85.195.114.189), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.530 ms 0.479 ms 0.564 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 20.329 ms 23.064 ms 30.097 ms
4 192.168.11.6 (192.168.11.6) 22.383 ms 28.261 ms 22.349 ms
5 154.0.4.162 (154.0.4.162) 28.277 ms 28.198 ms 28.195 ms
6 uvu-cust.coolideas.co.za (154.0.4.122) 173.477 ms 171.670 ms 165.671 ms
7 v1000.core1.lon3.he.net (216.66.80.169) 159.986 ms 159.610 ms 166.096 ms
8 100ge14-1.core1.lon2.he.net (184.105.64.237) 172.015 ms 171.764 ms 166.156 ms
9 ae1.cr-sargas.lon1.core.heg.com (195.66.225.173) 172.887 ms 172.702 ms 172.782 ms
10 ae9.cr-polaris.fra1.bb.godaddy.com (87.230.113.29) 176.682 ms 178.548 ms 178.276 ms
11 gw-heg.meitner.router.frankfurt.de.velia.net (87.230.115.5) 178.701 ms 173.960 ms 173.246 ms
12 dabuieg17.frankfurt.de.velia.net (85.195.113.12) 206.841 ms 225.975 ms 221.143 ms
13 85.195.114.189 (85.195.114.189) 178.474 ms 177.633 ms 183.300 ms

CISP -> 88.202.177.96

traceroute to 88.202.177.96 (88.202.177.96), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.504 ms 0.472 ms 0.537 ms
2 * * *
3 192.168.10.5 (192.168.10.5) 28.157 ms 28.127 ms 22.022 ms
4 192.168.11.6 (192.168.11.6) 27.258 ms 21.310 ms 21.216 ms
5 154.0.4.162 (154.0.4.162) 21.409 ms 21.260 ms 21.103 ms
6 usi-cust.coolideas.co.za (154.0.4.2) 166.334 ms 160.979 ms 160.693 ms
7 u102-cust.coolideas.co.za (154.0.5.18) 172.811 ms 165.513 ms 165.437 ms
8 linx-224.as13213.net (195.66.224.19) 172.357 ms 172.445 ms 172.410 ms
9 te0-0-0-5.ccr22.lon01.atlas.cogentco.com (149.6.3.157) 171.847 ms 172.620 ms 172.231 ms
10 be2869.ccr42.lon13.atlas.cogentco.com (154.54.57.161) 172.269 ms 174.559 ms 179.127 ms
11 be12194.ccr41.ams03.atlas.cogentco.com (154.54.56.94) 177.952 ms be12488.ccr42.ams03.atlas.cogentco.com (130.117.51.42) 181.085 ms 177.382 ms
12 be3433.rcr21.ams06.atlas.cogentco.com (154.54.58.202) 171.921 ms 171.344 ms 179.014 ms
13 uk2.net.demarc.cogentco.com (149.14.92.130) 183.411 ms 175.781 ms 178.609 ms
14 10.125.4.7 (10.125.4.7) 172.769 ms 10.125.4.9 (10.125.4.9) 187.450 ms 167.837 ms
15 58cab160.setaptr.net (88.202.177.96) 179.302 ms 173.493 ms *

==================================

AH -> 151.106.5.253

traceroute to 151.106.5.253 (151.106.5.253), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.522 ms 0.482 ms 0.561 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 31.435 ms 31.252 ms 31.332 ms
4 169-1-21-54.ip.afrihost.co.za (169.1.21.54) 33.566 ms 28.413 ms 28.341 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 22.116 ms 21.957 ms 21.769 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 29.742 ms 23.470 ms 29.818 ms
7 te-0-3-0-19.lza-p4-jhb.liquidtelecom.net (77.246.57.39) 200.648 ms te-0-3-0-7.lza-p4-jhb.liquidtelecom.net (41.60.135.94) 207.854 ms 208.283 ms
8 xe-0-1-5-0.lfr-pe2-mrs.liquidtelecom.net (46.17.232.25) 197.097 ms 202.706 ms te-0-1-0-2.lfr-pe1-mrs.liquidtelecom.net (5.11.10.252) 201.123 ms
9 et-7-0-0-u100.cr-polaris.fra1.core.heg.com (80.81.192.239) 218.088 ms 217.317 ms 214.987 ms
10 ae0.cr-antares.fra10.bb.godaddy.com (87.230.115.1) 221.306 ms 226.469 ms 225.170 ms
11 ae0.cr-vega.sxb1.bb.godaddy.com (87.230.115.3) 222.586 ms 231.200 ms 243.723 ms
12 gw-heg.curie.router.fr.velia.net (87.230.112.17) 215.853 ms 222.443 ms 221.781 ms
13 sxb13ahB.strasbourg.fr.velia.net (134.119.212.3) 226.264 ms 230.515 ms 227.239 ms
14 151.106.5.253 (151.106.5.253) 217.676 ms 216.379 ms 221.676 ms

AH -> 85.195.114.189

traceroute to 85.195.114.189 (85.195.114.189), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.527 ms 0.456 ms 0.550 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 24.061 ms 28.681 ms 23.915 ms
4 cpt-rx1.ip.adsl.co.za (169.1.5.94) 34.615 ms 29.398 ms 34.245 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 29.279 ms 23.436 ms 28.989 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 29.397 ms 29.082 ms 28.913 ms
7 Te-0-3-0-11.lza-p3-jhb.liquidtelecom.net (77.246.57.37) 203.971 ms 211.657 ms 46.17.232.91 (46.17.232.91) 211.373 ms
8 te-0-1-0-2.lfr-pe1-mrs.liquidtelecom.net (5.11.10.252) 200.227 ms 192.535 ms 205.303 ms
9 et-7-0-0-u100.cr-polaris.fra1.core.heg.com (80.81.192.239) 220.674 ms 220.519 ms 219.096 ms
10 gw-heg.meitner.router.frankfurt.de.velia.net (87.230.115.5) 221.334 ms 225.141 ms 221.947 ms
11 dabuieg17.frankfurt.de.velia.net (85.195.113.12) 250.753 ms 233.452 ms 250.675 ms
12 85.195.114.189 (85.195.114.189) 219.203 ms 220.998 ms 215.576 ms

AH -> 88.202.177.96

traceroute to 88.202.177.96 (88.202.177.96), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.508 ms 0.498 ms 0.523 ms
2 * * *
3 cpt-tx2.ip.adsl.co.za (169.1.5.81) 23.675 ms 27.482 ms 23.613 ms
4 cpt-rx1.ip.adsl.co.za (169.1.5.94) 30.269 ms 33.613 ms 30.192 ms
5 cpt-net1.ip.adsl.co.za (169.1.5.128) 22.003 ms 28.259 ms 28.089 ms
6 77.246.59.84.liquidtelecom.net (77.246.59.84) 28.617 ms 23.405 ms 31.066 ms
7 te-0-2-0-16.luk-pe1-gsw.liquidtelecom.net (5.11.10.216) 179.073 ms te-0-2-0-17.luk-pe1-gsw.liquidtelecom.net (5.11.10.218) 174.761 ms te-0-3-0-5.luk-p1-tho.liquidtelecom.net (5.11.10.170) 163.752 ms
8 be-5.luk-pe1-tcy.liquidtelecom.net (5.11.10.191) 176.557 ms be-1.luk-pe1-tcy.liquidtelecom.net (5.11.10.189) 172.766 ms 170.678 ms
9 be5656.rcr21.b015534-1.lon01.atlas.cogentco.com (149.14.250.177) 179.483 ms 179.600 ms 174.765 ms
10 be2186.ccr22.lon01.atlas.cogentco.com (154.54.61.70) 177.989 ms be2185.ccr21.lon01.atlas.cogentco.com (154.54.61.62) 176.215 ms 165.746 ms
11 be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173) 182.945 ms be2869.ccr42.lon13.atlas.cogentco.com (154.54.57.161) 171.097 ms be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173) 178.223 ms
12 be12488.ccr42.ams03.atlas.cogentco.com (130.117.51.42) 182.775 ms 180.886 ms 177.044 ms
13 be3434.rcr21.ams06.atlas.cogentco.com (154.54.59.50) 180.096 ms 180.718 ms be3433.rcr21.ams06.atlas.cogentco.com (154.54.58.202) 179.675 ms
14 uk2.net.demarc.cogentco.com (149.14.92.58) 178.677 ms uk2.net.demarc.cogentco.com (149.14.92.130) 184.635 ms 184.548 ms
15 10.125.4.5 (10.125.4.5) 174.089 ms 10.125.4.7 (10.125.4.7) 184.568 ms 10.125.4.9 (10.125.4.9) 182.499 ms
16 58cab160.setaptr.net (88.202.177.96) 179.119 ms 179.142 ms *

Thank you so much for this information. It is clear that we don't have optimal routes, especially in capetown. Our GM is talking to our upstream providers about this issue.

 

[AfriFella]

There you go, you replicated the problem, please reduce ms by 20ms as that's how long it takes to get from UK to EU, not 187-158=29ms.

It's a very valid point, our upstream provider is already working to reduce the latency.

 

[SeaSickMama]

Ditto. I am chatting privateley to @AfriFella for the past week supplying traceroutes upon traceroutes and looking here in the actual thread it seems like the same thing.

Is anything going to get done? I was told the latency on the last liquidtelecom hop shows a routing issue on their side. I am unable to stream twitch higher than 160p on 50/50mbps connection which is just unacceptable.

Do a test on this link and post the result

Gartner | Delivering Actionable, Objective Insight to Executives and Their Teams

Gartner provides actionable insights, guidance, and tools that enable faster, smarter decisions and stronger performance on an organization’s mission-critical priorities.

cloudharmony.com