Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
What ever has been fiddled with, please stop now:

C:\Users\Joshua>tracert www.youtube.com

Tracing route to youtube-ui.l.google.com [216.58.223.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 8 ms 8 ms 41.181.201.93
4 9 ms 9 ms 8 ms 41.181.201.94
5 8 ms 8 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 9 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 70 ms 37 ms 31 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 32 ms 32 ms 32 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
9 39 ms 40 ms 39 ms 41.181.139.99
10 45 ms 53 ms 51 ms 72.14.194.74
11 32 ms 31 ms 31 ms 72.14.237.239
12 31 ms 39 ms 43 ms jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.


If the you can perform like this at 6pm, lets keep it this way please?

Ah! The whipping worked! :P

Let's hope things can stay at this level!
 
Everything seems a mess once again

Last Result:
Download Speed: 4860 kbps (607.5 KB/sec transfer rate)
Upload Speed: 676 kbps (84.5 KB/sec transfer rate)
Latency: 214 ms
Jitter: 4 ms
Thursday, 11 June 2015 19:45

Took 10mins to actually log onto this forum
 
Everything seems a mess once again

Last Result:
Download Speed: 4860 kbps (607.5 KB/sec transfer rate)
Upload Speed: 676 kbps (84.5 KB/sec transfer rate)
Latency: 214 ms
Jitter: 4 ms
Thursday, 11 June 2015 19:45

Took 10mins to actually log onto this forum

Latency isn't looking good :(
Do you have a traceroute that you can post here?
 
Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 105-236-249-65-esr-lo.mtnbusiness.co.za [105.236
.249.65]
3 43 ms 16 ms 19 ms 41.181.51.182
4 20 ms 20 ms 19 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
5 26 ms 27 ms 27 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 203 ms 200 ms 201 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]

7 187 ms 185 ms 189 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
8 204 ms 186 ms 188 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
9 193 ms 187 ms 185 ms xe-4-1-0-135.edge5.Amsterdam1.Level3.net [212.72
.41.89]
10 * 179 ms 184 ms ae-231-3607.edge4.London1.Level3.net [4.69.166.2
5]
11 226 ms 204 ms 203 ms ae-231-3607.edge4.London1.Level3.net [4.69.166.2
5]
12 195 ms 195 ms 201 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
.222]
13 * * * Request timed out.
14 * * * Request timed out.
15 205 ms 203 ms 206 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
16 190 ms 301 ms 226 ms 132.185.255.165
17 176 ms 172 ms 171 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.

Been complaining about latency for months now, it used to be around 15ms, now is 150ms or worse.
 
Spoke too soon :(

Clearly you need to setup a committee to do the whipping

Joshuas-MacBook-Pro:~ Mac$ traceroute www.youtube.com
traceroute to youtube-ui.l.google.com (216.58.223.14), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.343 ms 1.023 ms 0.927 ms
2 * * *
3 41.181.201.93 (41.181.201.93) 61.392 ms 65.222 ms 51.347 ms
4 41.181.201.94 (41.181.201.94) 91.138 ms 92.582 ms 101.044 ms
5 tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 66.521 ms 70.707 ms 105.986 ms
6 compj-cpt-1.mtnns.net (196.44.18.2) 74.210 ms
unc-cpt-1.mtnns.net (196.44.18.8) 53.401 ms 59.218 ms
7 ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134) 51.799 ms 50.376 ms 52.607 ms
8 rb-cr-1.za--ct-cr-2.za.mtnns.net (196.44.31.69) 151.727 ms
rb-cr-2.za--jh-cr-1.za.mtnns.net (196.44.0.43) 104.708 ms 114.570 ms
9 41.181.139.99 (41.181.139.99) 138.449 ms 123.641 ms
41.181.139.109 (41.181.139.109) 158.564 ms
10 72.14.194.74 (72.14.194.74) 115.542 ms 149.872 ms 120.256 ms
11 72.14.237.239 (72.14.237.239) 118.319 ms 125.471 ms 113.574 ms
12 jnb01s07-in-f14.1e100.net (216.58.223.14) 140.614 ms 130.800 ms 130.191 ms
 
Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 105-236-249-65-esr-lo.mtnbusiness.co.za [105.236
.249.65]
3 43 ms 16 ms 19 ms 41.181.51.182
4 20 ms 20 ms 19 ms tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.1
86]
5 26 ms 27 ms 27 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 203 ms 200 ms 201 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]

7 187 ms 185 ms 189 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
8 204 ms 186 ms 188 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
9 193 ms 187 ms 185 ms xe-4-1-0-135.edge5.Amsterdam1.Level3.net [212.72
.41.89]
10 * 179 ms 184 ms ae-231-3607.edge4.London1.Level3.net [4.69.166.2
5]
11 226 ms 204 ms 203 ms ae-231-3607.edge4.London1.Level3.net [4.69.166.2
5]
12 195 ms 195 ms 201 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14
.222]
13 * * * Request timed out.
14 * * * Request timed out.
15 205 ms 203 ms 206 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
16 190 ms 301 ms 226 ms 132.185.255.165
17 176 ms 172 ms 171 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.

Been complaining about latency for months now, it used to be around 15ms, now is 150ms or worse.

I'm not sure which hop you're referring to as being 15ms. Your latency on this test seems a little erratic but ultimately mostly acceptable for EU/UK. Just the one hop over 300ms is not good, but good be an anomaly. Just remember that once you've gone onto Level 3, you've essentially left our network.
 
Spoke too soon :(

Clearly you need to setup a committee to do the whipping

Joshuas-MacBook-Pro:~ Mac$ traceroute www.youtube.com
traceroute to youtube-ui.l.google.com (216.58.223.14), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.343 ms 1.023 ms 0.927 ms
2 * * *
3 41.181.201.93 (41.181.201.93) 61.392 ms 65.222 ms 51.347 ms
4 41.181.201.94 (41.181.201.94) 91.138 ms 92.582 ms 101.044 ms
5 tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 66.521 ms 70.707 ms 105.986 ms
6 compj-cpt-1.mtnns.net (196.44.18.2) 74.210 ms
unc-cpt-1.mtnns.net (196.44.18.8) 53.401 ms 59.218 ms
7 ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134) 51.799 ms 50.376 ms 52.607 ms
8 rb-cr-1.za--ct-cr-2.za.mtnns.net (196.44.31.69) 151.727 ms
rb-cr-2.za--jh-cr-1.za.mtnns.net (196.44.0.43) 104.708 ms 114.570 ms
9 41.181.139.99 (41.181.139.99) 138.449 ms 123.641 ms
41.181.139.109 (41.181.139.109) 158.564 ms
10 72.14.194.74 (72.14.194.74) 115.542 ms 149.872 ms 120.256 ms
11 72.14.237.239 (72.14.237.239) 118.319 ms 125.471 ms 113.574 ms
12 jnb01s07-in-f14.1e100.net (216.58.223.14) 140.614 ms 130.800 ms 130.191 ms

It's difficult to have instant results with latency. A lot of the work will be make change, wait to see results. Also, rises in latency can only be picked up after they happen and then we have to make changes and monitor if the changes are effective or if more should be done, or run the risk of making things worse in a panicked effort.

The guys are under a lot of pressure and they know how much what they do affect our clients. No whipping is required, promise ;)
 
I'm not sure which hop you're referring to as being 15ms. Your latency on this test seems a little erratic but ultimately mostly acceptable for EU/UK. Just the one hop over 300ms is not good, but good be an anomaly. Just remember that once you've gone onto Level 3, you've essentially left our network.

If I run the speed test from this website, the latency sits at between 150-250ms on a cape town to cape town test, this used to be 15ms. So why is this happening. This is another thing I have been complaining about for a while with no resolution.
 
If I run the speed test from this website, the latency sits at between 150-250ms on a cape town to cape town test, this used to be 15ms. So why is this happening. This is another thing I have been complaining about for a while with no resolution.

Just curious, if you run the speedtest using Cape Town to Pretoria / Johannesburg, do you see a difference in latency?
 
I keep on saying this, and nothing gets done. I cannot spend all my time testing, testing should be done by Afrihost, and we should get the service we are paying for, not continual delaying tactics. Everyday, excuses, excuses.

I really do understand your frustration, the issue is that for example at the moment on our monitoring latencies on our network in the Cape is normal, but that doesn't rule out a localized issue. It really does help us a lot if you report any issues that you experience here, you shouldn't have to do thorough testing every single time.
 
Struggling to browse today. Loads of international sites are very slow or not loading at all.
 
Struggling to browse today. Loads of international sites are very slow or not loading at all.

International throughput did dip seriously for a few minutes, we are seeing it return to normal now. Can you test again possibly?
 
International throughput did dip seriously for a few minutes, we are seeing it return to normal now. Can you test again possibly?

Yeah, seems back to normal now. Thanks.

Edit: Spoke too soon. Broken again.
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X