Afrihost Capped DSL Feedback

Hummercellc

Expert Member
Joined
Jan 6, 2008
Messages
3,451
Lucky packet Internet. So sick of the constant buffering on Facebook & Instagram. Every single night this past week and a bit.
Switching to another ISP and it is fine.
 

tanka

Well-Known Member
Joined
Jun 28, 2007
Messages
190
Every evening same issue. Slow international throughput. This is really frustrating:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| rb2011l - 0 | 11 | 11 | 0 | 0 | 2 | 1 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| jhb-in2.ip.adsl.co.za - 0 | 11 | 11 | 30 | 48 | 65 | 45 |
| jhb-net1.ip.adsl.co.za - 0 | 11 | 11 | 2 | 3 | 7 | 7 |
| 169-1-5-74.ip.afrihost.co.za - 0 | 11 | 11 | 2 | 3 | 7 | 3 |
| 41.169.57.216 - 0 | 11 | 11 | 3 | 3 | 7 | 3 |
|ix-ae-7-0.tcore1.jso-johannesburg.as6453.net - 0 | 11 | 11 | 3 | 6 | 30 | 3 |
|if-ae-4-2.tcore1.klt-cape-town.as6453.net - 0 | 11 | 11 | 184 | 186 | 196 | 185 |
| if-ae-5-2.tcore2.pv9-lisbon.as6453.net - 0 | 11 | 11 | 178 | 178 | 182 | 179 |
| if-ae-7-2.tcore2.wv6-madrid.as6453.net - 0 | 11 | 11 | 179 | 184 | 194 | 180 |
| if-ae-11-2.tcore1.wv6-madrid.as6453.net - 0 | 11 | 11 | 178 | 178 | 180 | 178 |
|if-ae-5-2.tcore2.wyn-marseille.as6453.net - 0 | 11 | 11 | 178 | 178 | 179 | 178 |
|if-ae-7-2.tcore2.fnm-frankfurt.as6453.net - 0 | 11 | 11 | 178 | 178 | 179 | 179 |
|if-ae-4-2.tcore1.fr0-frankfurt.as6453.net - 0 | 11 | 11 | 177 | 178 | 179 | 178 |
| 195.219.219.10 - 0 | 11 | 11 | 178 | 178 | 180 | 178 |
| core21.fsn1.hetzner.com - 0 | 11 | 11 | 183 | 184 | 194 | 183 |
| ex9k2.rz14.hetzner.de - 0 | 11 | 11 | 209 | 232 | 256 | 230 |
| server.tanka.co.za - 0 | 11 | 11 | 189 | 211 | 227 | 204 |
|________________________________________________|______|______|______|______|______|______|
 

AfriGenie

Afrihost
Company Rep
Joined
Oct 9, 2014
Messages
7,266
Every evening same issue. Slow international throughput. This is really frustrating:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| rb2011l - 0 | 11 | 11 | 0 | 0 | 2 | 1 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| jhb-in2.ip.adsl.co.za - 0 | 11 | 11 | 30 | 48 | 65 | 45 |
| jhb-net1.ip.adsl.co.za - 0 | 11 | 11 | 2 | 3 | 7 | 7 |
| 169-1-5-74.ip.afrihost.co.za - 0 | 11 | 11 | 2 | 3 | 7 | 3 |
| 41.169.57.216 - 0 | 11 | 11 | 3 | 3 | 7 | 3 |
|ix-ae-7-0.tcore1.jso-johannesburg.as6453.net - 0 | 11 | 11 | 3 | 6 | 30 | 3 |
|if-ae-4-2.tcore1.klt-cape-town.as6453.net - 0 | 11 | 11 | 184 | 186 | 196 | 185 |
| if-ae-5-2.tcore2.pv9-lisbon.as6453.net - 0 | 11 | 11 | 178 | 178 | 182 | 179 |
| if-ae-7-2.tcore2.wv6-madrid.as6453.net - 0 | 11 | 11 | 179 | 184 | 194 | 180 |
| if-ae-11-2.tcore1.wv6-madrid.as6453.net - 0 | 11 | 11 | 178 | 178 | 180 | 178 |
|if-ae-5-2.tcore2.wyn-marseille.as6453.net - 0 | 11 | 11 | 178 | 178 | 179 | 178 |
|if-ae-7-2.tcore2.fnm-frankfurt.as6453.net - 0 | 11 | 11 | 178 | 178 | 179 | 179 |
|if-ae-4-2.tcore1.fr0-frankfurt.as6453.net - 0 | 11 | 11 | 177 | 178 | 179 | 178 |
| 195.219.219.10 - 0 | 11 | 11 | 178 | 178 | 180 | 178 |
| core21.fsn1.hetzner.com - 0 | 11 | 11 | 183 | 184 | 194 | 183 |
| ex9k2.rz14.hetzner.de - 0 | 11 | 11 | 209 | 232 | 256 | 230 |
| server.tanka.co.za - 0 | 11 | 11 | 189 | 211 | 227 | 204 |
|________________________________________________|______|______|______|______|______|______|

It looks okay for the most. What sort of throughput to Europe are you seeing?
 

AfriGenie

Afrihost
Company Rep
Joined
Oct 9, 2014
Messages
7,266
Lucky packet Internet. So sick of the constant buffering on Facebook & Instagram. Every single night this past week and a bit.
Switching to another ISP and it is fine.

Is it just Facebook and Instagram? Any other services that aren't running as they should be?
 

Hummercellc

Expert Member
Joined
Jan 6, 2008
Messages
3,451
Is it just Facebook and Instagram? Any other services that aren't running as they should be?
Only Facebook and instagram. And they are only a problem on Afrihost. Other ISPs are fine. I have tested with both Google and Auto DNS.
 

tanka

Well-Known Member
Joined
Jun 28, 2007
Messages
190
It looks okay for the most. What sort of throughput to Europe are you seeing?

speed.PNG

It is extremely erratic but often averaging below 3mb/s in a 100mb fibre line. This is trying to watch a video. Usually I see spikes every 5 seconds for a moment or so at throughput of 20mb/s+.
 

JohnJuniorV3

Expert Member
Joined
Dec 21, 2011
Messages
1,463
If it happens again, could you run a traceroute to Afrihost.com or the LoL server please. Our Network Team is investigating any reports of latency but we'll need the traceroute results to figure out what's going on.


Code:
PS C:\Users\Oliver> ping 185.40.65.1 -t

Pinging 185.40.65.1 with 32 bytes of data:
Reply from 185.40.65.1: bytes=32 time=238ms TTL=47
Reply from 185.40.65.1: bytes=32 time=275ms TTL=47
Reply from 185.40.65.1: bytes=32 time=277ms TTL=46
Reply from 185.40.65.1: bytes=32 time=229ms TTL=47
Reply from 185.40.65.1: bytes=32 time=230ms TTL=47
Reply from 185.40.65.1: bytes=32 time=213ms TTL=46
Reply from 185.40.65.1: bytes=32 time=215ms TTL=47
Reply from 185.40.65.1: bytes=32 time=235ms TTL=46
Reply from 185.40.65.1: bytes=32 time=240ms TTL=47
Reply from 185.40.65.1: bytes=32 time=242ms TTL=47
Reply from 185.40.65.1: bytes=32 time=247ms TTL=46
Reply from 185.40.65.1: bytes=32 time=219ms TTL=46
Reply from 185.40.65.1: bytes=32 time=216ms TTL=46
Reply from 185.40.65.1: bytes=32 time=212ms TTL=47
Reply from 185.40.65.1: bytes=32 time=218ms TTL=46
Reply from 185.40.65.1: bytes=32 time=207ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=46
Reply from 185.40.65.1: bytes=32 time=193ms TTL=46
Reply from 185.40.65.1: bytes=32 time=198ms TTL=47
Reply from 185.40.65.1: bytes=32 time=198ms TTL=47
Reply from 185.40.65.1: bytes=32 time=224ms TTL=47
Reply from 185.40.65.1: bytes=32 time=228ms TTL=47
Reply from 185.40.65.1: bytes=32 time=238ms TTL=47
Reply from 185.40.65.1: bytes=32 time=214ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=47
Reply from 185.40.65.1: bytes=32 time=204ms TTL=47
Reply from 185.40.65.1: bytes=32 time=225ms TTL=47
Reply from 185.40.65.1: bytes=32 time=200ms TTL=47
Reply from 185.40.65.1: bytes=32 time=193ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=46
Reply from 185.40.65.1: bytes=32 time=215ms TTL=46
Reply from 185.40.65.1: bytes=32 time=224ms TTL=47
Reply from 185.40.65.1: bytes=32 time=259ms TTL=47
Reply from 185.40.65.1: bytes=32 time=244ms TTL=46
Reply from 185.40.65.1: bytes=32 time=214ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=47
Reply from 185.40.65.1: bytes=32 time=220ms TTL=47
Reply from 185.40.65.1: bytes=32 time=227ms TTL=46
Reply from 185.40.65.1: bytes=32 time=251ms TTL=47
Reply from 185.40.65.1: bytes=32 time=240ms TTL=46
Reply from 185.40.65.1: bytes=32 time=218ms TTL=47
Reply from 185.40.65.1: bytes=32 time=215ms TTL=47
Reply from 185.40.65.1: bytes=32 time=227ms TTL=46
Reply from 185.40.65.1: bytes=32 time=209ms TTL=46
Reply from 185.40.65.1: bytes=32 time=239ms TTL=46
This is the League of Legends EUW server. You can see how inconsistent it is.
Code:
Tracert:

Tracing route to 185.40.65.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  csp1.zte.com.cn [192.168.1.1]
  2     *        *        *     Request timed out.
  3    18 ms     *        *     jhb-up3.ip.adsl.co.za [169.1.5.29]
  4    31 ms    29 ms    27 ms  jhb-in2.ip.adsl.co.za [169.1.5.30]
  5    29 ms    30 ms    30 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  6    18 ms    19 ms    18 ms  169-1-5-74.ip.afrihost.co.za [169.1.5.74]
  7    49 ms    51 ms    50 ms  41.169.57.216
  8    20 ms    19 ms    19 ms  ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
  9   185 ms   184 ms   184 ms  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 10   179 ms   178 ms   178 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
 11   186 ms   186 ms   186 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 12   179 ms   179 ms   179 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 13   183 ms   184 ms   184 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 14     *        *        *     Request timed out.
 15   185 ms   184 ms   185 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 16   196 ms   179 ms   180 ms  195.219.83.102
 17     *        *        *     Request timed out.
 18   265 ms   252 ms   249 ms  213.19.195.234
 19     *        *        *     Request timed out.
 20   193 ms   209 ms   193 ms  104.160.141.103
 21   193 ms   193 ms   193 ms  104.160.141.105
 22   248 ms   252 ms   272 ms  185.40.65.1

Trace complete.
 
Last edited:

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,957
PS
Code:
C:\Users\Oliver> ping 185.40.65.1 -t

Pinging 185.40.65.1 with 32 bytes of data:
Reply from 185.40.65.1: bytes=32 time=238ms TTL=47
Reply from 185.40.65.1: bytes=32 time=275ms TTL=47
Reply from 185.40.65.1: bytes=32 time=277ms TTL=46
Reply from 185.40.65.1: bytes=32 time=229ms TTL=47
Reply from 185.40.65.1: bytes=32 time=230ms TTL=47
Reply from 185.40.65.1: bytes=32 time=213ms TTL=46
Reply from 185.40.65.1: bytes=32 time=215ms TTL=47
Reply from 185.40.65.1: bytes=32 time=235ms TTL=46
Reply from 185.40.65.1: bytes=32 time=240ms TTL=47
Reply from 185.40.65.1: bytes=32 time=242ms TTL=47
Reply from 185.40.65.1: bytes=32 time=247ms TTL=46
Reply from 185.40.65.1: bytes=32 time=219ms TTL=46
Reply from 185.40.65.1: bytes=32 time=216ms TTL=46
Reply from 185.40.65.1: bytes=32 time=212ms TTL=47
Reply from 185.40.65.1: bytes=32 time=218ms TTL=46
Reply from 185.40.65.1: bytes=32 time=207ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=46
Reply from 185.40.65.1: bytes=32 time=193ms TTL=46
Reply from 185.40.65.1: bytes=32 time=198ms TTL=47
Reply from 185.40.65.1: bytes=32 time=198ms TTL=47
Reply from 185.40.65.1: bytes=32 time=224ms TTL=47
Reply from 185.40.65.1: bytes=32 time=228ms TTL=47
Reply from 185.40.65.1: bytes=32 time=238ms TTL=47
Reply from 185.40.65.1: bytes=32 time=214ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=47
Reply from 185.40.65.1: bytes=32 time=204ms TTL=47
Reply from 185.40.65.1: bytes=32 time=225ms TTL=47
Reply from 185.40.65.1: bytes=32 time=200ms TTL=47
Reply from 185.40.65.1: bytes=32 time=193ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=46
Reply from 185.40.65.1: bytes=32 time=215ms TTL=46
Reply from 185.40.65.1: bytes=32 time=224ms TTL=47
Reply from 185.40.65.1: bytes=32 time=259ms TTL=47
Reply from 185.40.65.1: bytes=32 time=244ms TTL=46
Reply from 185.40.65.1: bytes=32 time=214ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=47
Reply from 185.40.65.1: bytes=32 time=220ms TTL=47
Reply from 185.40.65.1: bytes=32 time=227ms TTL=46
Reply from 185.40.65.1: bytes=32 time=251ms TTL=47
Reply from 185.40.65.1: bytes=32 time=240ms TTL=46
Reply from 185.40.65.1: bytes=32 time=218ms TTL=47
Reply from 185.40.65.1: bytes=32 time=215ms TTL=47
Reply from 185.40.65.1: bytes=32 time=227ms TTL=46
Reply from 185.40.65.1: bytes=32 time=209ms TTL=46
Reply from 185.40.65.1: bytes=32 time=239ms TTL=46
This is the League of Legends EUW server. You can see how inconsistent it is.

Tracert:
Code:
Tracing route to 185.40.65.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  csp1.zte.com.cn [192.168.1.1]
  2     *        *        *     Request timed out.
  3    18 ms     *        *     jhb-up3.ip.adsl.co.za [169.1.5.29]
  4    31 ms    29 ms    27 ms  jhb-in2.ip.adsl.co.za [169.1.5.30]
  5    29 ms    30 ms    30 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  6    18 ms    19 ms    18 ms  169-1-5-74.ip.afrihost.co.za [169.1.5.74]
  7    49 ms    51 ms    50 ms  41.169.57.216
  8    20 ms    19 ms    19 ms  ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
  9   185 ms   184 ms   184 ms  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 10   179 ms   178 ms   178 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
 11   186 ms   186 ms   186 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 12   179 ms   179 ms   179 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 13   183 ms   184 ms   184 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 14     *        *        *     Request timed out.
 15   185 ms   184 ms   185 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 16   196 ms   179 ms   180 ms  195.219.83.102
 17     *        *        *     Request timed out.
 18   265 ms   252 ms   249 ms  213.19.195.234
 19     *        *        *     Request timed out.
 20   193 ms   209 ms   193 ms  104.160.141.103
 21   193 ms   193 ms   193 ms  104.160.141.105
 22   248 ms   252 ms   272 ms  185.40.65.1

Trace complete.
Add a ping to bras.afrihost.com, that's a piece of equipment sitting behind the exchange/before the network gets to the ISP.

Note to all, please add your tracerts/pings in [code ] tags, it keeps the format of your tracert/ping and keeps it in its own window that is scroll-able as seen above.

/sorry @Afripeps, not a customer anymore, just helping oliver
 

JohnJuniorV3

Expert Member
Joined
Dec 21, 2011
Messages
1,463
Add a ping to bras.afrihost.com, that's a piece of equipment sitting behind the exchange/before the network gets to the ISP.

Note to all, please add your tracerts/pings in [code ] tags, it keeps the format of your tracert/ping and keeps it in its own window that is scroll-able as seen above.

/sorry @Afripeps, not a customer anymore, just helping oliver

Code:
 Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\Oliver> ping bras.afrihost.com -t

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Thank you very much ;)
 
Last edited:

AfriFella

Afrihost
Company Rep
Joined
Jun 2, 2015
Messages
2,828
Code:
 Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\Oliver> ping bras.afrihost.com -t

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Thank you very much ;)

Thanks for testing. I must say that I'm finding it hard to see much wrong with your test results here. :( Your European latency looks OK and I'm not seeing any P/L in your pingtest. Your ping to the bras also looks good. Are you experiencing in-game issues?
 

JohnJuniorV3

Expert Member
Joined
Dec 21, 2011
Messages
1,463
Thanks for testing. I must say that I'm finding it hard to see much wrong with your test results here. :( Your European latency looks OK and I'm not seeing any P/L in your pingtest. Your ping to the bras also looks good. Are you experiencing in-game issues?

Other than latency that is jumpy as hell from about 8pm onwards, nothing at all.. Ping settles around 11pm again. I know you cannot justify what is wrong here, but the fact that my ping to Europe is irratic is slightly worrying. I don't experience it on any other ISP.
 

JohnJuniorV3

Expert Member
Joined
Dec 21, 2011
Messages
1,463
My worry is this: Can you explain what the 5th hop is? It is quite a jump.

Code:
Tracing route to bbc.co.uk [212.58.244.23]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  csp1.zte.com.cn [192.168.1.1]
  2     *        *        *     Request timed out.
  3    20 ms    19 ms    19 ms  jhb-up3.ip.adsl.co.za [169.1.5.29]
  4    27 ms    25 ms    23 ms  jhb-in2.ip.adsl.co.za [169.1.5.30]
[B]  5    86 ms    85 ms    84 ms  jhb-net1.ip.adsl.co.za [169.1.5.52][/B]
  6    19 ms    19 ms    19 ms  169-1-5-74.ip.afrihost.co.za [169.1.5.74]
  7    99 ms     *       62 ms  41.169.57.216
  8    19 ms    19 ms    28 ms  ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
  9   200 ms   200 ms   200 ms  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 10   198 ms   198 ms   198 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
 11   195 ms   194 ms   195 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 12   200 ms   200 ms   201 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 13   247 ms   249 ms   238 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 14     *        *      192 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 15   191 ms   191 ms   191 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 16   198 ms   201 ms   198 ms  195.219.83.102
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19   199 ms   199 ms   199 ms  NIU-SOLUTIO.ear1.London15.Level3.net [212.187.173.210]
 20     *        *        *     Request timed out.
 21   270 ms   262 ms   263 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
 22   200 ms   200 ms   201 ms  132.185.255.148
 23   201 ms   200 ms   201 ms  212.58.244.23
 

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,957
Thanks for testing. I must say that I'm finding it hard to see much wrong with your test results here. :( Your European latency looks OK and I'm not seeing any P/L in your pingtest. Your ping to the bras also looks good. Are you experiencing in-game issues?

This is on another ISP, why don't you post what your connection ping is to that result?
Code:
ping 185.40.65.1

Pinging 185.40.65.1 with 32 bytes of data:
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=193ms TTL=51

Ping statistics for 185.40.65.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 191ms, Maximum = 193ms, Average = 191ms
 

AfriFella

Afrihost
Company Rep
Joined
Jun 2, 2015
Messages
2,828
Other than latency that is jumpy as hell from about 8pm onwards, nothing at all.. Ping settles around 11pm again. I know you cannot justify what is wrong here, but the fact that my ping to Europe is irratic is slightly worrying. I don't experience it on any other ISP.

I did see that jump, but it doesn't appear to affect your overall latency which is sitting at around 200ms. Are you using any specifi DNS settings?
 

AfriFella

Afrihost
Company Rep
Joined
Jun 2, 2015
Messages
2,828
This is on another ISP, why don't you post what your connection ping is to that result?
Code:
ping 185.40.65.1

Pinging 185.40.65.1 with 32 bytes of data:
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=193ms TTL=51

Ping statistics for 185.40.65.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 191ms, Maximum = 193ms, Average = 191ms

Thanks for your input. There seems to be a 10ms difference in latency in what appears to be your comparative test. It's not to the same server, though. :(
 

JohnJuniorV3

Expert Member
Joined
Dec 21, 2011
Messages
1,463
I did see that jump, but it doesn't appear to affect your overall latency which is sitting at around 200ms. Are you using any specifi DNS settings?

Default DNS.
Code:
ping 185.40.65.1

Pinging 185.40.65.1 with 32 bytes of data:
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=191ms TTL=51
Reply from 185.40.65.1: bytes=32 time=193ms TTL=51

Ping statistics for 185.40.65.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 191ms, Maximum = 193ms, Average = 191ms

Yet as Johnatan has posted, look at how much more stable this ping is...?

My test:
Code:
C:\Users\Oliver> ping 185.40.65.1 -t

Pinging 185.40.65.1 with 32 bytes of data:
Reply from 185.40.65.1: bytes=32 time=238ms TTL=47
Reply from 185.40.65.1: bytes=32 time=275ms TTL=47
Reply from 185.40.65.1: bytes=32 time=277ms TTL=46
Reply from 185.40.65.1: bytes=32 time=229ms TTL=47
Reply from 185.40.65.1: bytes=32 time=230ms TTL=47
Reply from 185.40.65.1: bytes=32 time=213ms TTL=46
Reply from 185.40.65.1: bytes=32 time=215ms TTL=47
Reply from 185.40.65.1: bytes=32 time=235ms TTL=46
Reply from 185.40.65.1: bytes=32 time=240ms TTL=47
Reply from 185.40.65.1: bytes=32 time=242ms TTL=47
Reply from 185.40.65.1: bytes=32 time=247ms TTL=46
Reply from 185.40.65.1: bytes=32 time=219ms TTL=46
Reply from 185.40.65.1: bytes=32 time=216ms TTL=46
Reply from 185.40.65.1: bytes=32 time=212ms TTL=47
Reply from 185.40.65.1: bytes=32 time=218ms TTL=46
Reply from 185.40.65.1: bytes=32 time=207ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=46
Reply from 185.40.65.1: bytes=32 time=193ms TTL=46
Reply from 185.40.65.1: bytes=32 time=198ms TTL=47
Reply from 185.40.65.1: bytes=32 time=198ms TTL=47
Reply from 185.40.65.1: bytes=32 time=224ms TTL=47
Reply from 185.40.65.1: bytes=32 time=228ms TTL=47
Reply from 185.40.65.1: bytes=32 time=238ms TTL=47
Reply from 185.40.65.1: bytes=32 time=214ms TTL=46
Reply from 185.40.65.1: bytes=32 time=194ms TTL=47
Reply from 185.40.65.1: bytes=32 time=204ms TTL=47
Reply from 185.40.65.1: bytes=32 time=225ms TTL=47

There is a significant difference.
 

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,957
Thanks for your input. There seems to be a 10ms difference in latency in what appears to be your comparative test. It's not to the same server, though. :(

Ah sorry!
Code:
ping 212.58.244.23 -t

Pinging 212.58.244.23 with 32 bytes of data:
Reply from 212.58.244.23: bytes=32 time=149ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=150ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=149ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52

Ping statistics for 212.58.244.23:
    Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 148ms, Average = 149ms

EDIT: For anyone reading, the above is for comparison to an Afrihost account, it's an alternative ISP.
 
Last edited:

BrendanMc

Expert Member
Joined
Jan 14, 2008
Messages
1,965
So last tested an Afrihost account 2 months ago. Logged onto to night to check. Latency to LoL EUW servers over 300ms...two months later and nothing has changed it seems.
 

Vixation

Active Member
Joined
Jun 12, 2012
Messages
34
I am starting to feel like a broken record here. Ticket BSL-413-35004 is still not resolved. Latency every night to any euw related server is 300-400 and I have sent more tracer routes to Afrihost than I dare count.

Is it going to be an ongoing back and forth constantly as this issue has been there for months now and I never get a clear concrete answer to yes this is an issue that is going to be fixed or can't be fixed. I know I am not the only person experiencing this.

Can we please just get a clear answer and get support tickets looked at in a timely manner. If I had to leave any support ticket unresolved for a week I would get fired.
 
Top