Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
AfriMan said:
Definitely not good at all. can we see a traceroute?

Drop me a PM if you can, let's see where the latency is coming from :(
Click to expand...

Thanks, AfriMan. PM sent. Copying my tracert result below:

C:\>tracert google.com

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

1 <1 ms 1 ms 1 ms 192.168.1.1
2 524 ms 523 ms 564 ms ???-???-???-???-esr-lo.mtnbusiness.co.za [???.???.???.???]
3 729 ms 759 ms 727 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 689 ms 742 ms 749 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 595 ms 537 ms 514 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 702 ms 784 ms 880 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 695 ms 652 ms 643 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 705 ms 726 ms 771 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
9 633 ms 630 ms 649 ms core2.ams.net.google.com [195.69.145.100]
10 740 ms 783 ms 802 ms 209.85.254.90
11 912 ms 957 ms 987 ms 72.14.238.153
12 819 ms 856 ms 944 ms 209.85.240.158
13 1007 ms 1029 ms 1000 ms 209.85.253.21
14 832 ms 790 ms 789 ms 72.14.235.168
15 890 ms 922 ms 914 ms 209.85.243.47
16 832 ms 833 ms 864 ms par10s10-in-f6.1e100.net [173.194.40.134]

Trace complete.
 
Sunday night, 7-20pm:

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 10 ms 9 ms 10 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 12 ms 12 ms 12 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 13 ms 13 ms 13 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 13 ms 15 ms 15 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 52 ms 13 ms 13 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 194 ms 199 ms 202 ms core2.ams.net.google.com [195.69.145.100]
8 187 ms 185 ms 186 ms 209.85.254.95
9 331 ms 330 ms 330 ms 209.85.253.247
10 339 ms 337 ms 337 ms 209.85.255.85
11 200 ms 189 ms 188 ms 216.239.49.38
12 * * * Request timed out.
13 192 ms 193 ms 192 ms ea-in-f104.1e100.net [74.125.136.104]

Trace complete.

3031229879.png

http://speedtest.ookla.com/result/2342740673.png

http://speedtest.ookla.com/result/2342741399.png



Something is wrong somewhere...
 
Bursty-dude said:
"10mb" and 100Gb capped account.
Click to expand...

Ok. I have found that (I'm new to 10Mb, coming from 2) single-threaded downloads on international aren't all that awesome. I can easily max out my line with 2-3 threads, but 1 doesn't cut it nicely. I tested it and found the same with IS. Asked a friend who's on 10Mb and he says it's how things roll.
My local is perfect. Flawless in every way.

My intl speedtests suck really badly but it's no reflection of my intl performance as a whole.
Is this perhaps what you're experiencing?
 
Like I mentioned previously in this thread, when I first got the 10Mb ADSL line in January, it was constantly close to or over 10Mb.

Then in March, if I remember correctly, the speeds and issues started creeping in and a line sync was done to 7Mb and all as perfectly fine. And since about 2.5 to 3 weeks ago, it has started degrading again.
 
Guys, with Afrihost's uncapped accounts/network having latency issues lately (and shaping, but I'm mostly talking about the latency problems at the moment) - can any of you on the Afrihost Capped products tell me what your service is like? Especially streaming (Netflix, Hulu), gaming, and P2P? I'm considering changing my uncapped to a 200gb capped (and hoping it'll be enough, Netflix is bandwidth-hungry)
 
aktor said:
Guys, with Afrihost's uncapped accounts/network having latency issues lately (and shaping, but I'm mostly talking about the latency problems at the moment) - can any of you on the Afrihost Capped products tell me what your service is like? Especially streaming (Netflix, Hulu), gaming, and P2P? I'm considering changing my uncapped to a 200gb capped (and hoping it'll be enough, Netflix is bandwidth-hungry)
Click to expand...

I don't watch Netflix, but streaming is a breeze with whatever I watch. My latency on the product is amazing. Gaming is good, and p2p is just epic - I got 950KB/s on a torrent that I tested.
 
notstpaul said:
Thanks, AfriMan. PM sent. Copying my tracert result below:

C:\>tracert google.com

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

1 <1 ms 1 ms 1 ms 192.168.1.1
2 524 ms 523 ms 564 ms ???-???-???-???-esr-lo.mtnbusiness.co.za [???.???.???.???]
3 729 ms 759 ms 727 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 689 ms 742 ms 749 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 595 ms 537 ms 514 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 702 ms 784 ms 880 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 695 ms 652 ms 643 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 705 ms 726 ms 771 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
9 633 ms 630 ms 649 ms core2.ams.net.google.com [195.69.145.100]
10 740 ms 783 ms 802 ms 209.85.254.90
11 912 ms 957 ms 987 ms 72.14.238.153
12 819 ms 856 ms 944 ms 209.85.240.158
13 1007 ms 1029 ms 1000 ms 209.85.253.21
14 832 ms 790 ms 789 ms 72.14.235.168
15 890 ms 922 ms 914 ms 209.85.243.47
16 832 ms 833 ms 864 ms par10s10-in-f6.1e100.net [173.194.40.134]

Trace complete.
Click to expand...

This morning things look MUCH better. I've no idea what happened, but I didn't do anything. Not sure if AfriMan had a hand in it? :)

2343270555.png
 
froot said:
I don't watch Netflix, but streaming is a breeze with whatever I watch. My latency on the product is amazing. Gaming is good, and p2p is just epic - I got 950KB/s on a torrent that I tested.
Click to expand...
I hope that's the norm - I've had issues with my Afrihost capped account now and then.
 
aktor said:
I hope that's the norm - I've had issues with my Afrihost capped account now and then.
Click to expand...

Only issues I've had was last week when the IPC was a tad congested, but it didn't happen on Friday and hasn't happened today, so I think that's sorted.
 
It's much better than it has been for the last few weeks, but still not where it used to be.

Did this after the connection came back:
ScreenShot011.jpg

Checked it:
ScreenShot012.jpg

Done this:
3032261266.png

And finally:

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 9 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 13 ms 16 ms 13 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 33 ms 24 ms 24 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 12 ms 12 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 54 ms 11 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 193 ms 193 ms 192 ms core2.ams.net.google.com [195.69.145.100]
8 188 ms 218 ms * 209.85.254.90
9 338 ms 339 ms 339 ms 209.85.253.249
10 341 ms 340 ms 342 ms 209.85.254.213
11 206 ms 205 ms 207 ms 209.85.254.189
12 * * * Request timed out.
13 196 ms 197 ms 231 ms ea-in-f147.1e100.net [74.125.136.147]

Trace complete.
 
notstpaul said:
This morning things look MUCH better. I've no idea what happened, but I didn't do anything. Not sure if AfriMan had a hand in it? :)

View attachment 76063
Click to expand...

What line speed do you have with us? If there is congestion on your exchange the higher latencies may return later on tonight :(
Drop me a PM and I'll take a look at things for you.
 
Hello? Anyone out there?

3032592232.png


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

1 <1 ms 1 ms <1 ms 192.168.0.1
2 20 ms 10 ms 62 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 13 ms 12 ms 13 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 14 ms 17 ms 14 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 13 ms 13 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 * 12 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 193 ms * 193 ms core2.ams.net.google.com [195.69.145.100]
8 190 ms 189 ms * 209.85.254.90
9 * 339 ms 337 ms 72.14.238.153
10 354 ms 341 ms 338 ms 209.85.254.231
11 197 ms 242 ms 203 ms 216.239.49.38
12 * * * Request timed out.
13 197 ms 196 ms 196 ms ea-in-f147.1e100.net [74.125.136.147]

Trace complete.



This is getting a tad irritating now...
 
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 10 ms 9 ms 9 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 14 ms 11 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 24 ms 23 ms 23 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 18 ms 20 ms 14 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 14 ms 14 ms 14 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 193 ms 200 ms 210 ms core2.ams.net.google.com [195.69.145.100]
8 188 ms 190 ms 200 ms 209.85.254.90
9 336 ms 339 ms 344 ms 72.14.238.153
10 338 ms 343 ms 341 ms 209.85.254.213
11 211 ms 208 ms 192 ms 209.85.255.51
12 * * * Request timed out.
13 192 ms 192 ms 193 ms ea-in-f104.1e100.net [74.125.136.104]

Trace complete.


Why does hop 12 always time out?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X