Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Mortiiy said:
Hi there. Bellville North DSLAM. I have intermittent HOP 2 breaks past few days. See traceroute image.
I have my DSL line with Afrihost, support tickets and images sent through, amazingly NO RESPONSE yet.
Currently using cellular data for essential data. :mad:

Support ticket KIG-691-30070

-snip
Click to expand...

Mortiiy said:
Excuse me, you see nothing wrong? Did you notice the red histogram at bottom of hop2??? Complete disconnects up to 3 mins each.
Ok, I am moving over..
Click to expand...

Thanks for posting here :)
Latency looks fine here, not sure how this tool measures jitter - that's probably what the red lines are.

A traceroute/ MTR via Command Prompt or Terminal should give us a clearer picture.
Are you sure you're using an Afrihost account though? Looks like there tests are being done with an IS based account.

If your line's dropping though, we'll need to see the cause - drop me a PM with your DSL details.
 
I have my DSL line with Afrihost A DSL account...
I can send these instance traces all day, you will notice nada.
That is why I posted the pingplotter historical of HOP2. The red histogram at the bottom is a historical record of pings from HOP 2.
Disconnects up to 3min at a time.

Here is the trace anycase.
Thanks for ansmwering though, much appreciated..


C:\Users\FIN-7>tracert www.afrihost.co.za

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

1 <1 ms <1 ms 1 ms 192.168.0.1
2 10 ms 10 ms 10 ms 196-210-147-1.dynamic.isadsl.co.za [196.210.147.
1]
3 12 ms 13 ms 10 ms 196.38.75.69
4 10 ms 10 ms 11 ms 196.35.115.128
5 12 ms 15 ms 15 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.1
2]
6 13 ms 13 ms 11 ms 168.209.6.131
7 11 ms 12 ms 12 ms mweb.cinx.net.za [196.223.22.32]
8 35 ms 36 ms 34 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
9 33 ms 35 ms 35 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
10 32 ms * 32 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]

11 34 ms 34 ms 31 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
12 32 ms 32 ms 39 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
13 32 ms 32 ms 32 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
14 31 ms 33 ms 32 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
15 31 ms 31 ms 31 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

C:\Users\FIN-7>
 
A Query

Based on the posts in this thread

I did a trace route to the both Afrihost.com and Afrihost.co.za.

Could you provide some insight as to why both of these exist and why the results are so different, if both these devices belong to Afrihost?

Code: 
Tracing route to www.afrihost.com [190.93.242.183]
over a maximum of 20 hops:

  1    <1 ms    <1 ms     1 ms  *************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    13 ms    13 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    13 ms    13 ms    13 ms  jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
  7    13 ms    13 ms    13 ms  cloudflare.jb1.napafrica.net [196.46.25.198]
  8    14 ms    13 ms    13 ms  190.93.242.183

Trace complete.

Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 20 hops:

  1     1 ms     1 ms    <1 ms  ****************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *       12 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    33 ms    33 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  7    33 ms    34 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  8    34 ms    34 ms    34 ms  optinet.ct1.napafrica.net [196.10.140.145]
  9    35 ms    38 ms    38 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
 10    35 ms    38 ms    38 ms  te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
 11    35 ms    34 ms    35 ms  102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
 12    35 ms    34 ms    33 ms  197-81-226-77.jhb.mweb.co.za [197.81.226.77]
 13    35 ms    35 ms    36 ms  197-81-226-53.jhb.mweb.co.za [197.81.226.53]
 14    35 ms    34 ms    35 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 15    35 ms    33 ms    34 ms  197-81-229-9.jhb.mweb.co.za [197.81.229.9]
 16    35 ms    34 ms    34 ms  41-86-112-68.mweb.co.za [41.86.112.68]
 
Mortiiy said:
I have my DSL line with Afrihost A DSL account...
I can send these instance traces all day, you will notice nada.
That is why I posted the pingplotter historical of HOP2. The red histogram at the bottom is a historical record of pings from HOP 2.
Disconnects up to 3min at a time.

Here is the trace anycase.
Thanks for ansmwering though, much appreciated..
Code: 
C:\Users\FIN-7>tracert [url]www.afrihost.co.za[/url]

Tracing route to [url]www.afrihost.co.za[/url] [41.86.112.68]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  192.168.0.1
  2    10 ms    10 ms    10 ms  196-210-147-1.dynamic.isadsl.co.za [196.210.147.
1]
  3    12 ms    13 ms    10 ms  196.38.75.69
  4    10 ms    10 ms    11 ms  196.35.115.128
  5    12 ms    15 ms    15 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.1
2]
  6    13 ms    13 ms    11 ms  168.209.6.131
  7    11 ms    12 ms    12 ms  mweb.cinx.net.za [196.223.22.32]
  8    35 ms    36 ms    34 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
  9    33 ms    35 ms    35 ms  te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
 10    32 ms     *       32 ms  102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]

 11    34 ms    34 ms    31 ms  197-81-226-77.jhb.mweb.co.za [197.81.226.77]
 12    32 ms    32 ms    39 ms  197-81-226-53.jhb.mweb.co.za [197.81.226.53]
 13    32 ms    32 ms    32 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 14    31 ms    33 ms    32 ms  197-81-229-9.jhb.mweb.co.za [197.81.229.9]
 15    31 ms    31 ms    31 ms  41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

C:\Users\FIN-7>
Click to expand...

Just because you have your line with Afrihost doesn't mean it will use Afrihost's route. You pay Afrihost, Afrihost pays Telkom. That's why you can also use other Telkom providers on the line. That tracert looks perfect though.
 
Mortiiy said:
I have my DSL line with Afrihost A DSL account...
I can send these instance traces all day, you will notice nada.
That is why I posted the pingplotter historical of HOP2. The red histogram at the bottom is a historical record of pings from HOP 2.
Disconnects up to 3min at a time.

Here is the trace anycase.
Thanks for ansmwering though, much appreciated..


C:\Users\FIN-7>tracert www.afrihost.co.za

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

1 <1 ms <1 ms 1 ms 192.168.0.1
2 10 ms 10 ms 10 ms 196-210-147-1.dynamic.isadsl.co.za [196.210.147.
1]
3 12 ms 13 ms 10 ms 196.38.75.69
4 10 ms 10 ms 11 ms 196.35.115.128
5 12 ms 15 ms 15 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.1
2]
6 13 ms 13 ms 11 ms 168.209.6.131
7 11 ms 12 ms 12 ms mweb.cinx.net.za [196.223.22.32]
8 35 ms 36 ms 34 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
9 33 ms 35 ms 35 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
10 32 ms * 32 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]

11 34 ms 34 ms 31 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
12 32 ms 32 ms 39 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
13 32 ms 32 ms 32 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
14 31 ms 33 ms 32 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
15 31 ms 31 ms 31 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

C:\Users\FIN-7>
Click to expand...

This is what an Afrihost account should show in a tracert

Tracing route to www.afrihost.com [190.93.241.183]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 * 19 ms 19 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
4 19 ms 18 ms 18 ms 169-1-5-202.ip.afrihost.co.za [169.1.5.202]
5 19 ms 18 ms 18 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 16 ms 16 ms 15 ms eoh-ns.jb1.napafrica.net [196.46.25.157]
7 30 ms 22 ms 16 ms 41-66-181-63-3f.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.63]
8 19 ms 18 ms 18 ms 190.93.241.183

Trace complete.
 
Mortiiy said:
I have my DSL line with Afrihost A DSL account...
I can send these instance traces all day, you will notice nada.
That is why I posted the pingplotter historical of HOP2. The red histogram at the bottom is a historical record of pings from HOP 2.
Disconnects up to 3min at a time.

Here is the trace anycase.
Thanks for ansmwering though, much appreciated..


C:\Users\FIN-7>tracert www.afrihost.co.za

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

1 <1 ms <1 ms 1 ms 192.168.0.1
2 10 ms 10 ms 10 ms 196-210-147-1.dynamic.isadsl.co.za [196.210.147.
1]
3 12 ms 13 ms 10 ms 196.38.75.69
4 10 ms 10 ms 11 ms 196.35.115.128
5 12 ms 15 ms 15 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.1
2]
6 13 ms 13 ms 11 ms 168.209.6.131
7 11 ms 12 ms 12 ms mweb.cinx.net.za [196.223.22.32]
8 35 ms 36 ms 34 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
9 33 ms 35 ms 35 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
10 32 ms * 32 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]

11 34 ms 34 ms 31 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
12 32 ms 32 ms 39 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
13 32 ms 32 ms 32 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
14 31 ms 33 ms 32 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
15 31 ms 31 ms 31 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

C:\Users\FIN-7>
Click to expand...

Your line rental with us only means we manage the line, not the hops or how the traffic works - that's entirely up to your ISP.
Anyway, the 2nd hop is generally your exchange.

Your pings look solid to your exchange, what does this show? http://www.pingtest.net/
 
daniellgr said:
Based on the posts in this thread

I did a trace route to the both Afrihost.com and Afrihost.co.za.

Could you provide some insight as to why both of these exist and why the results are so different, if both these devices belong to Afrihost?

Code: 
Tracing route to www.afrihost.com [190.93.242.183]
over a maximum of 20 hops:

  1    <1 ms    <1 ms     1 ms  *************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    13 ms    13 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    13 ms    13 ms    13 ms  jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
  7    13 ms    13 ms    13 ms  cloudflare.jb1.napafrica.net [196.46.25.198]
  8    14 ms    13 ms    13 ms  190.93.242.183

Trace complete.

Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 20 hops:

  1     1 ms     1 ms    <1 ms  ****************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *       12 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    33 ms    33 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  7    33 ms    34 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  8    34 ms    34 ms    34 ms  optinet.ct1.napafrica.net [196.10.140.145]
  9    35 ms    38 ms    38 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
 10    35 ms    38 ms    38 ms  te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
 11    35 ms    34 ms    35 ms  102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
 12    35 ms    34 ms    33 ms  197-81-226-77.jhb.mweb.co.za [197.81.226.77]
 13    35 ms    35 ms    36 ms  197-81-226-53.jhb.mweb.co.za [197.81.226.53]
 14    35 ms    34 ms    35 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 15    35 ms    33 ms    34 ms  197-81-229-9.jhb.mweb.co.za [197.81.229.9]
 16    35 ms    34 ms    34 ms  41-86-112-68.mweb.co.za [41.86.112.68]
Click to expand...

I think that's to the server vs the cache.
 
daniellgr said:
Based on the posts in this thread

I did a trace route to the both Afrihost.com and Afrihost.co.za.

Could you provide some insight as to why both of these exist and why the results are so different, if both these devices belong to Afrihost?

Code: 
Tracing route to www.afrihost.com [190.93.242.183]
over a maximum of 20 hops:

  1    <1 ms    <1 ms     1 ms  *************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    13 ms    13 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    13 ms    13 ms    13 ms  jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
  7    13 ms    13 ms    13 ms  cloudflare.jb1.napafrica.net [196.46.25.198]
  8    14 ms    13 ms    13 ms  190.93.242.183

Trace complete.

Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 20 hops:

  1     1 ms     1 ms    <1 ms  ****************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *       12 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    33 ms    33 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  7    33 ms    34 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  8    34 ms    34 ms    34 ms  optinet.ct1.napafrica.net [196.10.140.145]
  9    35 ms    38 ms    38 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
 10    35 ms    38 ms    38 ms  te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
 11    35 ms    34 ms    35 ms  102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
 12    35 ms    34 ms    33 ms  197-81-226-77.jhb.mweb.co.za [197.81.226.77]
 13    35 ms    35 ms    36 ms  197-81-226-53.jhb.mweb.co.za [197.81.226.53]
 14    35 ms    34 ms    35 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 15    35 ms    33 ms    34 ms  197-81-229-9.jhb.mweb.co.za [197.81.229.9]
 16    35 ms    34 ms    34 ms  41-86-112-68.mweb.co.za [41.86.112.68]
Click to expand...

That is interesting.
AFAIK, the domain setup from our end is that the .co.za is only an alias for the .com.

I'll see what insights our team have on this :)
 
Thanks for all the pointers folks.
My issue is between my router and the DSLAM, HOP2, which is Telkom, which would mean Afrihost management.

As you can see, traceroutes are perfect to HOP2, but HOP2 drops out.
If i cannot take this to Afrihost, I am waisting my time and money here.


As requested.


I am now referring to my ISP. If they can help, I am out of here.
 
Last edited:
Mortiiy said:
Thanks for all the pointers folks.
My issue is between my router and the DSLAM, HOP2, which is Telkom, which would mean Afrihost management.

As you can see, traceroutes are perfect to HOP2, but HOP2 drops out.
If i cannot take this to Afrihost, I am waisting my time and money here.


As requested.


I am now referring to my ISP. If they can help, I am out of here.
Click to expand...

Happy to log a fault for you, but we do need to run some tests to give Telkom the right info.
Is there not a server closer to you to test?

From the traceroutes you've provided it does look like you're on older Telkom hardware.
 
AfriGuy said:
Happy to log a fault for you, but we do need to run some tests to give Telkom the right info.
Is there not a server closer to you to test?

From the traceroutes you've provided it does look like you're on older Telkom hardware.
Click to expand...

I am not all that familiar with pingtest.net, so I used this opportunity to learn something and cannot get anything but a test from Nairobi to run?
 
Mortiiy said:
Thanks for all the pointers folks.
My issue is between my router and the DSLAM, HOP2, which is Telkom, which would mean Afrihost management.

As you can see, traceroutes are perfect to HOP2, but HOP2 drops out.
If i cannot take this to Afrihost, I am waisting my time and money here.


As requested.


I am now referring to my ISP. If they can help, I am out of here.
Click to expand...

Um, you are using a IS account?
So how is this a Afrihost problem?

Although you might pay Afrihost for you DSL line, you are still connected via the Telkom Network to IS.

So no offence, but Afrihost have sweet nothing to do with this, either Telkom or IS need to assist you.

Sorry I had to state the obvious. :whistle:
 
Mortiiy said:
Thanks for all the pointers folks.
My issue is between my router and the DSLAM, HOP2, which is Telkom, which would mean Afrihost management.

As you can see, traceroutes are perfect to HOP2, but HOP2 drops out.
If i cannot take this to Afrihost, I am waisting my time and money here.


As requested.


I am now referring to my ISP. If they can help, I am out of here.
Click to expand...

May I ask what the issue is? At ~4000km that's a fine ping test.
 
Hummercellc said:
Um, you are using a IS account?
So how is this a Afrihost problem?

Although you might pay Afrihost for you DSL line, you are still connected via the Telkom Network to IS.

So no offence, but Afrihost have sweet nothing to do with this, either Telkom or IS need to assist you.

Sorry I had to state the obvious. :whistle:
Click to expand...


But this IS the point. OP is with Afrihost and he is getting all sorts of strange results. I am not with Afrihost at all and are very puzzled by the results I am getting .... A ping test I ran ( and I am with Telkom) indicated my ISP was also IS?
 
daniellgr said:
But this IS the point. OP is with Afrihost and he is getting all sorts of strange results. I am not with Afrihost at all and are very puzzled by the results I am getting .... A ping test I ran ( and I am with Telkom) indicated my ISP was also IS?
Click to expand...

The traceroutes you posted to our website show you're routing via Telkom :)
 
Ja, the results are good, so are mine, but still can't understand why Nairobi, when I can choose servers for the ookla speetests ...

Looks like The DNS servers are all suffering from a hangover or something ....
 
daniellgr said:
Ja, the results are good, so are mine, but still can't understand why Nairobi, when I can choose servers for the ookla speetests ...

Looks like The DNS servers are all suffering from a hangover or something ....
Click to expand...

Pingtest only seems to have one location, the servers differ to what's available on speedtest.net
 
And here is the ISP response as expected.

"Hi ******,
Thanks for getting in touch with us. Hop 2 is actually your Telkom exchange, thats still before any of our infrastructure. The disconnects are either coming from your line or your Telkom exchange. I would advise contacting whoever manages your DSL line so they can investigate and possibly contact Telkom on your behalf.
Regards
***** "

Some responses here..:whistle: is why taking a support ticket off the support portal to a public forum is not a good idea, unless you feel like bantering the obvious all day...

There are numerous articles and posts explaining infrastructure etc, First Telkom, then ISP.
Since Afrihost is paid to manage my DSL line with Telkom, I am asking Afriguy to log the call if he sees nothing else to verify. Thanks Afriguy.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X