Afrihost overseas high pings?

2

2525252525

Expert Member
Joined
Apr 2, 2018
Messages
1,844
Reaction score
2,038
I'm trying to play some BF3 which has a server in Germany but how is it that the EU servers there are 200-220ms ping on Openserve Afrihost? Surely it shouldn't be this bad?

Look at this crap

Tracing route to 94.250.199.214 over a maximum of 30 hops

1 3 ms 3 ms 2 ms homerouter.cpe [192.168.8.1]
2 16 ms 16 ms 17 ms 41.170.75.1
3 37 ms 27 ms 28 ms 165-73-14-41.ip.afrihost.co.za [165.73.14.41]
4 23 ms 23 ms 23 ms 169-1-21-28.ip.afrihost.co.za [169.1.21.28]
5 24 ms 23 ms 24 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
6 25 ms 23 ms 23 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
7 24 ms 24 ms 24 ms 206.249.2.73
8 211 ms 210 ms 211 ms be2385.ccr21.lon01.atlas.cogentco.com [154.54.40.93]
9 219 ms 242 ms 218 ms ldn-b3-link.ip.twelve99.net [62.115.9.28]
10 210 ms 211 ms 210 ms ldn-bb1-link.ip.twelve99.net [62.115.120.74]
11 218 ms 218 ms 218 ms prs-bb1-link.ip.twelve99.net [62.115.135.25]
12 232 ms 233 ms 233 ms ffm-bb1-link.ip.twelve99.net [62.115.123.12]
13 233 ms 233 ms 234 ms ffm-b5-link.ip.twelve99.net [62.115.114.89]
14 221 ms 222 ms 222 ms ae10-0.fra10.core-backbone.com [62.115.9.226]
15 221 ms 221 ms 278 ms cbb.fra14.edge-1.et-0-0-1 [5.56.21.154]
16 221 ms 221 ms 220 ms core01.fra.ix.fra14.ae2.0 [94.250.214.1]
17 222 ms 222 ms 222 ms
 
I get around 165ms to that IP on Cool Ideas.

1 1 ms 1 ms 1 ms 10.0.0.1
2 12 ms 12 ms 12 ms 154.0.0.242
3 12 ms 12 ms 12 ms 100.98.0.3
4 152 ms 153 ms 152 ms 100.99.0.126
5 * * * Request timed out.
6 153 ms 152 ms 152 ms ldn-b3-link.ip.twelve99.net [62.115.9.28]
7 153 ms 152 ms * ldn-bb4-link.ip.twelve99.net [62.115.122.180]
8 159 ms 160 ms 159 ms prs-bb2-link.ip.twelve99.net [62.115.133.239]
9 173 ms 167 ms 167 ms ffm-bb2-link.ip.twelve99.net [62.115.122.139]
10 168 ms 167 ms 181 ms ffm-b5-link.ip.twelve99.net [62.115.114.91]
11 165 ms 166 ms 166 ms ae10-0.fra10.core-backbone.com [62.115.9.226]
12 166 ms 165 ms 165 ms cbb.fra14.edge-1.et-0-0-1 [5.56.21.154]
13 166 ms 165 ms 165 ms core01.fra.ix.fra14.ae2.0 [94.250.214.1]
14 212 ms 166 ms 167 ms spine2.fra.iw.xe-0-0-30.0 [94.250.214.239]
15 166 ms 165 ms 165 ms 94.250.199.214
 
BlackStatic said:
Thanks that shaved off like 10ms but nowhere close to the peformance of Cool Ideas, I wonder what they do different from Afrihost to make sure a dramatic change in latency?
Click to expand...

It depends a lot on what region you are in, if you are in JHB you will get ~17-20ms higher than CPT.
It's also possible you might be routed via the East coast instead of the West coast, but I'm not 100% sure.
 
Soul Assassin said:
What's your ping if you do a speedtest?
Click to expand...
Yeah this looks pretty bad for fiber

Pinging www.google.co.za [2c0f:fb50:4002:804::2003] with 32 bytes of data:
Reply from 2c0f:fb50:4002:804::2003: time=40ms
Reply from 2c0f:fb50:4002:804::2003: time=41ms
Reply from 2c0f:fb50:4002:804::2003: time=32ms
Reply from 2c0f:fb50:4002:804::2003: time=40ms
 
Yeah I don't think you should be getting 40ms to JHB.

When I moved from Vuma to Openserve my ping went up by 5ms but that's about it.
 
Soul Assassin said:
Yeah I don't think you should be getting 40ms to JHB.

When I moved from Vuma to Openserve my ping went up by 5ms but that's about it.
Click to expand...
Yeah I'm used to single digit local pings this is a bit riciculous

Tracing route to www.google.co.za [172.217.170.3]
over a maximum of 30 hops:

1 24 ms 24 ms 23 ms 172.16.0.1
2 25 ms 24 ms 24 ms 197.234.241.1
3 26 ms 24 ms 24 ms 197.234.240.5
4 24 ms 26 ms 29 ms 172.253.65.163
5 27 ms 29 ms 28 ms 172.253.66.3
6 25 ms 24 ms 26 ms jnb02s02-in-f3.1e100.net [172.217.170.3]

Trace complete.
 
Soul Assassin said:
Yeah I don't think you should be getting 40ms to JHB.

When I moved from Vuma to Openserve my ping went up by 5ms but that's about it.
Click to expand...
Sorry that previous tracert was with that cloudflare stuff, here's a better articulated one, check out that second hop.

C:\Windows\system32>tracert www.google.co.za

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms homerouter.cpe [192.168.8.1]
2 17 ms 16 ms 17 ms 41.170.75.1
3 * * * Request timed out.
4 26 ms 24 ms 24 ms 169-1-21-28.ip.afrihost.co.za [169.1.21.28]
5 26 ms 24 ms 25 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
6 26 ms 24 ms 23 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
7 24 ms 23 ms 23 ms 72.14.216.130
8 25 ms 25 ms 25 ms 172.253.65.163
9 25 ms 25 ms 24 ms 142.251.52.3
10 25 ms 24 ms 24 ms jnb02s11-in-f3.1e100.net [172.217.170.99]
 
BlackStatic said:
Sorry that previous tracert was with that cloudflare stuff, here's a better articulated one, check out that second hop.

C:\Windows\system32>tracert www.google.co.za

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms homerouter.cpe [192.168.8.1]
2 17 ms 16 ms 17 ms 41.170.75.1
3 * * * Request timed out.
4 26 ms 24 ms 24 ms 169-1-21-28.ip.afrihost.co.za [169.1.21.28]
5 26 ms 24 ms 25 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
6 26 ms 24 ms 23 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
7 24 ms 23 ms 23 ms 72.14.216.130
8 25 ms 25 ms 25 ms 172.253.65.163
9 25 ms 25 ms 24 ms 142.251.52.3
10 25 ms 24 ms 24 ms jnb02s11-in-f3.1e100.net [172.217.170.99]
Click to expand...

Hi

It looks like latency starts off with 25ms between you and JHB and this could be the reason why you are getting over 200ms on your international tests.

If you subtract 20ms from those your average should be around 197ms or less.

We are aware that some ip ranges generally have higher latency than others and possibly other ISP's like Cool Ideas. We explored our options however due to traffic levels we had to get extra capacity from a 3rd transit provider and Liquid Telecoms made the most sense to us.

This unfortunately makes things much more complicated to control reverse paths if other networks see us in the 4 different Eu locations our transit providers have peering points at for example London, Amsterdam, Frankfurt and Marseille. On th reverse networks choose which path better suits them to return traffic to us and in some cases these are not always the lowest latency.

Because of this we see variable latency of between 163ms to 190ms to various networks in EU and for now, it's not possible for us to tweak this. We are looking at ways we can achieve better latency once we have moved clients over to pppoe where we can announce only certain prefixes over certain transit providers to steer traffic a bit.
 
And I hate to say it but I don't think Openserve would do anything about that 25ms to JHB.
 
AfriNatic said:
Hi

It looks like latency starts off with 25ms between you and JHB and this could be the reason why you are getting over 200ms on your international tests.

If you subtract 20ms from those your average should be around 197ms or less.

We are aware that some ip ranges generally have higher latency than others and possibly other ISP's like Cool Ideas. We explored our options however due to traffic levels we had to get extra capacity from a 3rd transit provider and Liquid Telecoms made the most sense to us.

This unfortunately makes things much more complicated to control reverse paths if other networks see us in the 4 different Eu locations our transit providers have peering points at for example London, Amsterdam, Frankfurt and Marseille. On th reverse networks choose which path better suits them to return traffic to us and in some cases these are not always the lowest latency.

Because of this we see variable latency of between 163ms to 190ms to various networks in EU and for now, it's not possible for us to tweak this. We are looking at ways we can achieve better latency once we have moved clients over to pppoe where we can announce only certain prefixes over certain transit providers to steer traffic a bit.
Click to expand...
You should add a disclaimer that this is a high latency service.

Your Vuma based service has dramatically less ping, think 180ms vs 220ms, it's a shame because the Vuma uptime is horrible.
 
Soul Assassin said:
And I hate to say it but I don't think Openserve would do anything about that 25ms to JHB.
Click to expand...
It jumps between 25 and 40 something ms to JHB, something isn't right with Openserve here.

Should I just cancel Openserve and move back to Vuma? I don't really want to because Vuma availability in the Vaal area is dogwater, outages every week, but it's 6ms to Jhb at least.
 
Last edited:
Y'll always get high ping added if you with Openserve. I witness this.
 
On afrihost-openserve

Tracing route to 94.250.199.214 over a maximum of 30 hops

1 4 ms 3 ms 2 ms 192.168.1.100
2 5 ms 5 ms 4 ms 41.17xxxxxx
3 9 ms * 9 ms 165-73-14-17.ip.afrihost.co.za [165.73.14.17]
4 8 ms 9 ms 7 ms 169-1-21-28.ip.afrihost.co.za [169.1.21.28]
5 8 ms 7 ms 6 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
6 7 ms 6 ms 6 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
7 8 ms 7 ms 7 ms 206.249.2.73
8 182 ms 182 ms 182 ms be2385.ccr21.lon01.atlas.cogentco.com [154.54.40.93]
9 182 ms 181 ms 181 ms ldn-b3-link.ip.twelve99.net [62.115.9.28]
10 183 ms 183 ms 182 ms ldn-bb4-link.ip.twelve99.net [62.115.122.180]
11 201 ms 201 ms 201 ms prs-bb2-link.ip.twelve99.net [62.115.133.239]
12 196 ms 197 ms 197 ms ffm-bb2-link.ip.twelve99.net [62.115.122.139]
13 196 ms 196 ms 196 ms ffm-b5-link.ip.twelve99.net [62.115.114.91]
14 205 ms 205 ms 205 ms ae10-0.fra10.core-backbone.com [62.115.9.226]
15 220 ms 204 ms 204 ms cbb.fra14.edge-1.et-0-0-1 [5.56.21.154]
16 204 ms 203 ms 204 ms core01.fra.ix.fra14.ae2.0 [94.250.214.1]
17 204 ms 205 ms 217 ms spine2.fra.iw.xe-0-0-30.0 [94.250.214.239]
18 205 ms 204 ms 204 ms 94.250.199.214
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X