Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Mortiiy said:
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.
Click to expand...

As I said in my previous posts, I'm happy to log a fault for you - but we need to run the right tests to pass onto Telkom.
If the line's dropping, your ISP can see a reason for the drop. It's either a drop from the port, the router or the line.

Let me know.
 
AfriGuy said:
As I said in my previous posts, I'm happy to log a fault for you - but we need to run the right tests to pass onto Telkom.
If the line's dropping, your ISP can see a reason for the drop. It's either a drop from the port, the router or the line.

Let me know.
Click to expand...

In that case I do not need Afrihost.
Cheers
 
Mortiiy said:
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.
Click to expand...

Mortiiy said:
In that case I do not need Afrihost.
Cheers
Click to expand...

AfriGuy said:
I'm not sure I follow? I was under the impression you'd like me to log a fault for you?
Click to expand...

Very strange this...
 
krustyrsa said:
yeah I don't think he quite understands the whole ISP routing and line management thing..He blamed Afrihost for a poor connection on IS's network:confused:. And yet he still argues that its Afrihost's fault.
Click to expand...

Not completely correct but I cannot understand his attitude either. The Pingtest he got showing that his ISP was IS was an anomaly this morning as I had exactly the same result when doing a pingtest even though my ISP is Telkom...
 
daniellgr said:
Not completely correct but I cannot understand his attitude either. The Pingtest he got showing that his ISP was IS was an anomaly this morning as I had exactly the same result when doing a pingtest even though my ISP is Telkom...
Click to expand...

I think the query was his exchange, not really the ISP.
 
Okay. So Telkom must have made their way to my exchange today, again (this is common). Because my internet is dead. I know this because afrihost say that it is them.

They (Telkom) normally come back after 2 or more days to fix the exchange. I never log a complaint by Telkom, so I wonder how they know when to come and fix the problem.

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

1 1 ms <1 ms 1 ms 192.168.1.1
2 408 ms 464 ms 306 ms 169-0-19-1.ip.afrihost.co.za [169.0.19.1]
3 797 ms 643 ms 1075 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 510 ms 391 ms 389 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 238 ms 259 ms 432 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 438 ms 268 ms 287 ms africainx.ct1.napafrica.net [196.10.140.7]
7 * * 691 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.
africainx.net [41.84.13.228]
8 502 ms 460 ms 619 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
9 * * 313 ms 190.93.242.183

Trace complete.
 
Bashley said:
Okay. So Telkom must have made their way to my exchange today, again (this is common). Because my internet is dead. I know this because afrihost say that it is them.

They (Telkom) normally come back after 2 or more days to fix the exchange. I never log a complaint by Telkom, so I wonder how they know when to come and fix the problem.

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

1 1 ms <1 ms 1 ms 192.168.1.1
2 408 ms 464 ms 306 ms 169-0-19-1.ip.afrihost.co.za [169.0.19.1]
3 797 ms 643 ms 1075 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 510 ms 391 ms 389 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 238 ms 259 ms 432 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 438 ms 268 ms 287 ms africainx.ct1.napafrica.net [196.10.140.7]
7 * * 691 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.
africainx.net [41.84.13.228]
8 502 ms 460 ms 619 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
9 * * 313 ms 190.93.242.183

Trace complete.
Click to expand...

Telkom could be busy with maintenance in your area. Did you see any Telkom vehicles or techs in your area?
 
So AfriGenie :whistle:

Care to enlighten us as to what happened last night to International traffic for the 10th time this month? :D

Seems like it's back to normal, hitting 40mbps to London now, last night was dismal at 4mbps.
 
Cape Town region.

C:\>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 10.0.0.2
2 11 ms 11 ms 11 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 1516 ms 936 ms * cpt-up1.ip.adsl.co.za [169.1.5.105] <<<<<<<<<<<<---bottleneck
4 13 ms 13 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 20 ms 26 ms 12 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 13 ms 13 ms 16 ms optinet.ct1.napafrica.net [196.10.140.15]
7 35 ms 34 ms 35 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
8 47 ms 98 ms 74 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 34 ms 34 ms 33 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
10 33 ms 33 ms 32 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 36 ms 38 ms 36 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 34 ms 34 ms 34 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 34 ms 32 ms 32 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 32 ms 32 ms 32 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.
 
Last edited:
Cape Town area to international IP

C:\>tracert www.google.com

Tracing route to www.google.com [216.58.210.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 14 ms 10 ms 10 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]

3 * * * Request timed out. <<<---Bottleneck

4 14 ms 12 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 13 ms 12 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 12 ms 12 ms 12 ms 41.164.52.42
7 33 ms 34 ms 35 ms 172.18.1.162
8 56 ms 34 ms 35 ms 72.14.194.206
9 204 ms 204 ms 205 ms 66.249.95.8
10 197 ms 197 ms 196 ms 216.239.59.5
11 195 ms 195 ms 196 ms 108.170.232.105
12 204 ms 204 ms 204 ms lhr25s11-in-f4.1e100.net [216.58.210.36]

Trace complete.

No virus, no malware, no torrent software running in background...
 
DeSLAM said:
Cape Town area to international IP

C:\>tracert www.google.com

Tracing route to www.google.com [216.58.210.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 14 ms 10 ms 10 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]

3 * * * Request timed out. <<<---Bottleneck

4 14 ms 12 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 13 ms 12 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 12 ms 12 ms 12 ms 41.164.52.42
7 33 ms 34 ms 35 ms 172.18.1.162
8 56 ms 34 ms 35 ms 72.14.194.206
9 204 ms 204 ms 205 ms 66.249.95.8
10 197 ms 197 ms 196 ms 216.239.59.5
11 195 ms 195 ms 196 ms 108.170.232.105
12 204 ms 204 ms 204 ms lhr25s11-in-f4.1e100.net [216.58.210.36]

Trace complete.

No virus, no malware, no torrent software running in background...
Click to expand...

AfriGenie said:
Telkom could be busy with maintenance in your area. Did you see any Telkom vehicles or techs in your area?
Click to expand...

Bashley said:
Okay. So Telkom must have made their way to my exchange today, again (this is common). Because my internet is dead. I know this because afrihost say that it is them.

They (Telkom) normally come back after 2 or more days to fix the exchange. I never log a complaint by Telkom, so I wonder how they know when to come and fix the problem.

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

1 1 ms <1 ms 1 ms 192.168.1.1
2 408 ms 464 ms 306 ms 169-0-19-1.ip.afrihost.co.za [169.0.19.1]
3 797 ms 643 ms 1075 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 510 ms 391 ms 389 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 238 ms 259 ms 432 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
6 438 ms 268 ms 287 ms africainx.ct1.napafrica.net [196.10.140.7]
7 * * 691 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.
africainx.net [41.84.13.228]
8 502 ms 460 ms 619 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
9 * * 313 ms 190.93.242.183

Trace complete.
Click to expand...


all in the same exchange area?
 
Hummercellc said:
So AfriGenie :whistle:

Care to enlighten us as to what happened last night to International traffic for the 10th time this month? :D

Seems like it's back to normal, hitting 40mbps to London now, last night was dismal at 4mbps.
Click to expand...

I'm not sure honestly, I haven't checked with the Team that was looking into this last night. I can find out if you want. :)
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X