Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Bursty-dude said:
Still running fine my side as well, even though the better half is downloading something via Wifi:
View attachment 76429

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 12 ms 11 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 12 ms 12 ms 13 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 13 ms 13 ms 18 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 12 ms 11 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 193 ms 192 ms 193 ms core2.ams.net.google.com [195.69.145.100]
8 188 ms 189 ms 188 ms 209.85.254.90
9 337 ms 346 ms 337 ms 72.14.238.153
10 342 ms 341 ms 368 ms 209.85.255.73
11 195 ms 195 ms 192 ms 209.85.255.49
12 * * * Request timed out.
13 193 ms 194 ms 191 ms ea-in-f104.1e100.net [74.125.136.104]

Trace complete.
Click to expand...

Glad things are starting to improve :)
 
So it turns out my awful internet is probably congestion on the exchange at night. :mad:
Nearly a second just to ping telkom.co.za. :eek:

Anybody want to buy a house?

C:\>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.1.1
2 841 ms 822 ms 876 ms ???.???.???.???
3 780 ms 818 ms 853 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 831 ms 876 ms 843 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 967 ms 897 ms 684 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 745 ms 764 ms 801 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 846 ms 962 ms 960 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 797 ms 789 ms 802 ms 196.43.25.205
9 733 ms 760 ms 795 ms 196.43.39.166
10 986 ms 926 ms 669 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
11 748 ms 780 ms 927 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
12 831 ms 830 ms * nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]
13 881 ms 897 ms 913 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
Click to expand...

C:\>ping telkom.co.za

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=940ms TTL=241
Reply from 196.43.22.222: bytes=32 time=784ms TTL=241
Reply from 196.43.22.222: bytes=32 time=706ms TTL=241
Reply from 196.43.22.222: bytes=32 time=724ms TTL=241

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

C:\>
Click to expand...
 
notstpaul said:
So it turns out my awful internet is probably congestion on the exchange at night. :mad:
Nearly a second just to ping telkom.co.za. :eek:

Anybody want to buy a house?
Click to expand...

I remember my spending time in congestion city. No thanks. I'll pass :D
 
notstpaul said:
So it turns out my awful internet is probably congestion on the exchange at night. :mad:
Nearly a second just to ping telkom.co.za. :eek:

Anybody want to buy a house?
Click to expand...

Hang on for a bit. Telkom should do a backhaul upgrade in your area when they do their line upgrades next month. Let's hope they have overcompensated this time - we had terrible increases in congestion this time last year due to the upgrades to 384kbps and 1Mbps lines :(
 
@ Afri - who ever

I have a open Ticket ZZM-863-30251 with your "support team - used VERY loosly" for the past week. Nobody bothers to contact me and tell me what is being done. I do all the tracert,ping,dl tests etc and all I get is a cursory "we will look into it and get back to you"
I have come to realise that this just a delaying tactic. A week for you guys to tell me that "you right - something wrong with the News host server" after I phoned and had to listen to some aunty telling me how bloody great Afrihost is while I while away time waiting to speak to someone.

Very poor indeed.
 
avr-rulez said:
@ Afri - who ever

I have a open Ticket ZZM-863-30251 with your "support team - used VERY loosly" for the past week. Nobody bothers to contact me and tell me what is being done. I do all the tracert,ping,dl tests etc and all I get is a cursory "we will look into it and get back to you"
I have come to realise that this just a delaying tactic. A week for you guys to tell me that "you right - something wrong with the News host server" after I phoned and had to listen to some aunty telling me how bloody great Afrihost is while I while away time waiting to speak to someone.

Very poor indeed.
Click to expand...

Sorry about this poor experience. We do need to get as much information from clients before we can make a diagnosis. From what I can see we may not have asked some relevant questions. Firstly, I see you are connecting to News Host, which is the IS News server. Our news service runs using Highwinds, but our news url should direct you there.

Are URL are you using so we can see exactly service you're using?

My own tests show our news server running tops, so I don't think this is the issue. Please drop me a PM :(
 
Hi there

I seem to be stuck with very high latency here, any suggestions?



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

1 <1 ms <1 ms <1 ms 192.168.10.11
2 1 ms 1 ms 1 ms 192.168.1.1
3 906 ms 919 ms * 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.1
0.1]
4 748 ms 646 ms 866 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14
]
5 869 ms 818 ms 818 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

6 814 ms 822 ms 948 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

7 * * * Request timed out.
8 * * * Request timed out.
9 * 1022 ms 1114 ms 72.14.194.74
10 * 946 ms 854 ms 64.233.174.57
11 961 ms 918 ms 1010 ms jnb01s02-in-f16.1e100.net [74.125.233.80]



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

1 2 ms <1 ms <1 ms 192.168.10.11
2 1 ms 1 ms 1 ms 192.168.1.1
3 995 ms 893 ms 954 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.1
0.1]
4 921 ms 939 ms 947 ms 41.181.222.42
5 838 ms 887 ms 762 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

6 818 ms 776 ms 752 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

7 * 836 ms 874 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 774 ms * * qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.16
5.119]
9 * 826 ms 851 ms 72.14.194.74
10 * * 968 ms 64.233.174.57
11 928 ms 907 ms 913 ms jnb01s02-in-f19.1e100.net [74.125.233.83]



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

1 <1 ms <1 ms <1 ms 192.168.10.11
2 1 ms 1 ms 1 ms 192.168.1.1
3 828 ms 772 ms 843 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.1
0.1]
4 934 ms 916 ms 966 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14
]
5 876 ms 796 ms * ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

6 963 ms 896 ms 969 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

7 935 ms 924 ms 886 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * 941 ms 722 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.16
5.119]
9 838 ms 877 ms * jh-dca-2.za--jh-cr-2.za-a.mtnns.net [196.44.0.22
5]
10 * 777 ms * cache.google.com [66.8.14.37]
11 711 ms 777 ms 741 ms cache.google.com [66.8.14.37]

Trace complete.

Thanks.
 
Wynsam said:
Hi there

I seem to be stuck with very high latency here, any suggestions?



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

1 <1 ms <1 ms <1 ms 192.168.10.11
2 1 ms 1 ms 1 ms 192.168.1.1
3 906 ms 919 ms * 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.1
0.1]
4 748 ms 646 ms 866 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14
]
5 869 ms 818 ms 818 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

6 814 ms 822 ms 948 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

7 * * * Request timed out.
8 * * * Request timed out.
9 * 1022 ms 1114 ms 72.14.194.74
10 * 946 ms 854 ms 64.233.174.57
11 961 ms 918 ms 1010 ms jnb01s02-in-f16.1e100.net [74.125.233.80]



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

1 2 ms <1 ms <1 ms 192.168.10.11
2 1 ms 1 ms 1 ms 192.168.1.1
3 995 ms 893 ms 954 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.1
0.1]
4 921 ms 939 ms 947 ms 41.181.222.42
5 838 ms 887 ms 762 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

6 818 ms 776 ms 752 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

7 * 836 ms 874 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 774 ms * * qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.16
5.119]
9 * 826 ms 851 ms 72.14.194.74
10 * * 968 ms 64.233.174.57
11 928 ms 907 ms 913 ms jnb01s02-in-f19.1e100.net [74.125.233.83]



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

1 <1 ms <1 ms <1 ms 192.168.10.11
2 1 ms 1 ms 1 ms 192.168.1.1
3 828 ms 772 ms 843 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.1
0.1]
4 934 ms 916 ms 966 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14
]
5 876 ms 796 ms * ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

6 963 ms 896 ms 969 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

7 935 ms 924 ms 886 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 * 941 ms 722 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.16
5.119]
9 838 ms 877 ms * jh-dca-2.za--jh-cr-2.za-a.mtnns.net [196.44.0.22
5]
10 * 777 ms * cache.google.com [66.8.14.37]
11 711 ms 777 ms 741 ms cache.google.com [66.8.14.37]

Trace complete.

Thanks.
Click to expand...


Hi.

Can you please run the traceroute again. Might have been a temporary glitch on our side.
 
Wynsam said:
It is much better now -- what changed?
Click to expand...

Nothing from our end :( It looks like your router is duplicating itself somehow over hop 1 & 2 - hop 3 is your exchange here which shows higher than normal latency. Maybe indicating a congested exchange.

Could you run another traceroute and post it up here please?
 
AfriGuy said:
Nothing from our end :( It looks like your router is duplicating itself somehow over hop 1 & 2 - hop 3 is your exchange here which shows higher than normal latency. Maybe indicating a congested exchange.

Could you run another traceroute and post it up here please?
Click to expand...

Having two local hops means he's using two networks at home. Perhaps running via a gateway.
 
For the fourth time since 7-45pm tonight, the connection has just dropped dead. Rebooting this router constantly is getting extremely irritating.
I was very happy with the increase in speed and lack of connection issues after having 3+ weeks of bad speeds and bad connections but now it is time to light a fire under someone. Literally and figuratively.

I am tired of sending PM's, my details are with Afri-everyone by now...
 
To add to the last post:

25 past midnight and connection is back again.


Edited.
Never mind.....it is still dead. ADSL light on the router is green but there is no connection.
I'm off to bed, will switch the router on again at 7ish in the morning.
 
Last edited:
Bursty-dude said:
To add to the last post:

25 past midnight and connection is back again.


Edited.
Never mind.....it is still dead. ADSL light on the router is green but there is no connection.
I'm off to bed, will switch the router on again at 7ish in the morning.
Click to expand...

This is definitely not a general issue on the network, I can see that we had a pretty solid connection through the night. I know you're tired of sending PM's - but it really is the best way for me to help you.

PM me if you are still offline and let me know what's happening :(
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X