Afrihost New Network Feedback

Status
Not open for further replies.

Icemanbrfc

Honorary Master
Joined
Jul 28, 2011
Messages
20,851
Throughput doesn't look too great here.
What line sync stats are available on the router?
I still can't understand, if eg Telkom manages the line, and the Data is with an ISP. How does that impact the isp, or indeed the client using the data, when the host of the line is being impacted. Or let me rephrase Afriguy, if Afrihost doesn't manage the line, how does these stats become an ISP issue, when it is clearly or in most cases an issue with the line or the exchange etc.

Unless the ISP modifies a line to a degree, where they have a full control of the users line, I'm still trying to understand how an ISP gets blamed when their issue.
 

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,955
Would you mind posting a comparative traceroute to news24 just to see if you also get a weird spike?

Here
Code:
Tracing route to news24.com [41.86.110.143]
over a maximum of 30 hops:

  1     1 ms     1 ms     4 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    10 ms    11 ms     9 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    63 ms    12 ms    10 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  5    10 ms    10 ms    10 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    19 ms    11 ms    14 ms  optinet.ct1.napafrica.net [196.10.140.145]
  7    15 ms    12 ms    13 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
  8    14 ms    10 ms    10 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238]
  9    11 ms    10 ms    10 ms  196.28.178.66
 10    12 ms    10 ms    11 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
 11    23 ms    10 ms    12 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
 12    23 ms    15 ms    27 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146]
 13    42 ms    14 ms    17 ms  41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

EDIT:
Code:
Pinging news24.com [41.86.110.143] with 32 bytes of data:
Reply from 41.86.110.143: bytes=32 time=28ms TTL=243
Reply from 41.86.110.143: bytes=32 time=11ms TTL=243
Reply from 41.86.110.143: bytes=32 time=11ms TTL=243
Reply from 41.86.110.143: bytes=32 time=10ms TTL=243
Reply from 41.86.110.143: bytes=32 time=10ms TTL=243

Ping statistics for 41.86.110.143:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 28ms, Average = 14ms
 

NewBiks

Well-Known Member
Joined
Jul 29, 2015
Messages
480
I'm having constant issues with Twitch.tv and Vessel.com, constant buffering seeing the same performance even after upgrading my line speed. No point in pinging these sites they always comeback as "Request timed out".

ab5882a197.png

e054872fb6.png
 

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,955
I'm having constant issues with Twitch.tv and Vessel.com, constant buffering seeing the same performance even after upgrading my line speed. No point in pinging these sites they always comeback as "Request timed out".

That issue is due to twitch's cache servers.
Depending on Twitch, you either connect directly to their servers which guarantees a good stream, or you connect to one of the caches which are really bad.

(Side note: You can copy from CMD by right-click > select all > enter or ctrl-a > enter. Just paste it into [ code] [/code ] (without the spacing))
 

craigcul

Well-Known Member
Joined
Dec 17, 2012
Messages
281
ping is fine?
Pinging www.news24.com [41.86.110.200] with 32 bytes of data:
Reply from 41.86.110.200: bytes=32 time=32ms TTL=239
Reply from 41.86.110.200: bytes=32 time=29ms TTL=239
Reply from 41.86.110.200: bytes=32 time=30ms TTL=239
Reply from 41.86.110.200: bytes=32 time=30ms TTL=239

Ping statistics for 41.86.110.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 32ms, Average = 30ms
 
Last edited:

AfriFella

Afrihost
Company Rep
Joined
Jun 2, 2015
Messages
2,828
Here
Code:
Tracing route to news24.com [41.86.110.143]
over a maximum of 30 hops:

  1     1 ms     1 ms     4 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    10 ms    11 ms     9 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    63 ms    12 ms    10 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  5    10 ms    10 ms    10 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    19 ms    11 ms    14 ms  optinet.ct1.napafrica.net [196.10.140.145]
  7    15 ms    12 ms    13 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
  8    14 ms    10 ms    10 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238]
  9    11 ms    10 ms    10 ms  196.28.178.66
 10    12 ms    10 ms    11 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
 11    23 ms    10 ms    12 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
 12    23 ms    15 ms    27 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146]
 13    42 ms    14 ms    17 ms  41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

EDIT:
Code:
Pinging news24.com [41.86.110.143] with 32 bytes of data:
Reply from 41.86.110.143: bytes=32 time=28ms TTL=243
Reply from 41.86.110.143: bytes=32 time=11ms TTL=243
Reply from 41.86.110.143: bytes=32 time=11ms TTL=243
Reply from 41.86.110.143: bytes=32 time=10ms TTL=243
Reply from 41.86.110.143: bytes=32 time=10ms TTL=243

Ping statistics for 41.86.110.143:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 28ms, Average = 14ms

That looks good to me! :)
 

craigcul

Well-Known Member
Joined
Dec 17, 2012
Messages
281
@AfriFella
now news 24 loading in about 5 seconds maybe the server was busy just now. i see Johnatan get the same spick in the tracert.
 

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,955
@AfriFella
now news 24 loading in about 5 seconds maybe the server was busy just now. i see Johnatan get the same spick in the tracert.

Note to take my tracert as slightly better than it is, on WiFi and downloading at the same time.
 

AfriFella

Afrihost
Company Rep
Joined
Jun 2, 2015
Messages
2,828
Note to take my tracert as slightly better than it is, on WiFi and downloading at the same time.

Yeah I must say that 62ms is not really "stand-outish" compared to your 2000ms+ spike... Still worth looking into, though! Please keep testing to see if it persists.
 

Vorastra

Honorary Master
Joined
Jan 13, 2013
Messages
14,123
Alright so your guy phoned me, we did a bit of testing. Seems the game was being picked up by the P2P shaper. So your guys are going to be working on that (support was explaining, sounds like quite a lot of work to to get game signatures). Your support is really helpful btw. I can't recall the name of the guy who called me though :erm: If you can, thank him again for me. He was really helpful.
 

justinTek

Active Member
Joined
Oct 16, 2015
Messages
50
Hi Newbiks,

Try not to tracert to MyBroadband. Their hosts are using Cloudflare protection, which affects the results. I'm surprised JustinTek doesn't know this .. ha ha... !

I'd invest in glasses if I were you. Read the trace since you think you're so bloody clever.
 

akuma

Well-Known Member
Joined
Oct 19, 2005
Messages
128
Really horrible latency. Vids not loading, slow refresh rates. Pathetic...

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=54 time=178 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=54 time=78 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=54 time=252 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


ping 8.8.8.8

Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=109 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=45 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=206 ms
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 2 ms 1 ms 6 ms
2 Request timed out * * *
3 Request timed out * * *
4 Request timed out * * *
5 Request timed out * * *
6 Request timed out * * *
7 Request timed out * *
196.44.0.7 23 ms
8 Request timed out * *
196.44.31.6 104 ms
9 Request timed out * *
196.44.31.9 47 ms
10 Request timed out * * *
11 Request timed out * * *
12 Request timed out * * *
13 Request timed out * * *
14 Request timed out * * *
15 Request timed out * * *
16 Request timed out * * *
17 Request timed out * * *
18 Request timed out * * *
19 Request timed out * * *
20 Request timed out * *
21 Request timed out *
22 Request timed out *
23 Request timed out *
24 Request timed out *
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 Request timed out *


traceroute -n 8.8.8.8

1 192.168.1.1 2 ms 1 ms 1 ms
2 Request timed out * * *
3 Request timed out *
169.1.5.1 21 ms 22 ms
4 Request timed out * *
169.1.5.1 21 ms
5 Request timed out * * *
6 Request timed out *
72.14.194.2 77 ms
8.8.8.8 108 ms
7 Request timed out * *
8 Request timed out * *
9 Request timed out * *
10 Request timed out * *
11 Request timed out * *
12 Request timed out *
13 Request timed out *
14 Request timed out *


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 41.181.185.18


nslookup www.google.com

Name: www.google.com
Address: 216.58.223.4


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Status
Not open for further replies.
Top