Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Not necessarily, latency compounds, so generally the first place where latency is spotted is where the problem starts. How much latency will be compounded is unpredictable, so it's difficult to say the hop in between is producing latency to any extent.

But it does seem like there could be massive latency on the second hop based on best and worse results, it's just really difficult to assume. But since we're not seeing general latency in your region (i'm guessing you're in the North) then I guess we can assume it's not on the network :(

I tried with a LAN cable and I have the same latency problems with the ping to the router under 1ms. i have contacted Telkom about the exchange. They'll take a while to respond.

Location: PMB = Pietermaritzburg, KZN (under username :P)
 
I tried with a LAN cable and I have the same latency problems with the ping to the router under 1ms. i have contacted Telkom about the exchange. They'll take a while to respond.

Location: PMB = Pietermaritzburg, KZN (under username :P)

Oops, dunno why I thought you were in the North there :(
 
Oops, dunno why I thought you were in the North there :(

No problem, I updated my location to the full name :) By the way, speeds are absolutely brilliant for me -- just under 4mbps. It's just latency for gaming. It is definitely either the Durban IPC or my exchange, though. Can you guys check if the 033 343 exchange is having problems? Telkom is so slow
 
No problem, I updated my location to the full name :) By the way, speeds are absolutely brilliant for me -- just under 4mbps. It's just latency for gaming. It is definitely either the Durban IPC or my exchange, though. Can you guys check if the 033 343 exchange is having problems? Telkom is so slow

What does it do with a WA free account?
 
What does it do with a WA free account?

I can't test with one because I am apparently a fraudulent user. I'll contact them and see if I can get an account.

Here is a tracert from OVTR: Here we see the exchange lagging (I think -- first hop is my IP):
Code:
#	Country	Town	Lat	Lon	IP	Hostname	Latency (ms)	Dns lookup (ms)	Distance to previous node (km)
1	South Africa	(Unknown)	-29.0	24.0	105.237.249.239	105-237-249-239.access.mtnbusiness.co.za	0	0	0
2	South Africa	(Unknown)	-29.0	24.0	196.30.42.133	vl9-ah-ha-2.za.mtnbusiness.net.	454	3	0
3	South Africa	(Unknown)	-29.0	24.0	41.181.221.214	(None)	54	65	0
4	South Africa	(Unknown)	-29.0	24.0	41.181.221.213	(None)	3	55	0
5	South Africa	(Unknown)	-29.0	24.0	41.181.165.118	rb-dca-2.za--qux-b.za.mtnbusiness.net.	11	4	0
6	South Africa	(Unknown)	-29.0	24.0	196.44.31.122	rb-cr-1.za--rb-dca-2.mtnns.net.	1	2	0
7	South Africa	(Unknown)	-29.0	24.0	196.31.220.21	(None)	31	65	0
8	South Africa	(Unknown)	-29.0	24.0	196.31.63.202	(None)	3	61	0
9	South Africa	(Unknown)	-29.0	24.0	196.44.31.97	(None)	1	57	0
10	South Africa	(Unknown)	-29.0	24.0	196.30.1.39	(None)	2	129	0
11	South Africa	(Unknown)	-29.0	24.0	197.242.144.102	www.afrihost.com.	2	3	0
But here is another where the third hop seems to be the problem, but the exchange is also high:
Code:
#	Country	Town	Lat	Lon	IP	Hostname	Latency (ms)	Dns lookup (ms)	Distance to previous node (km)
1	South Africa	(Unknown)	-29.0	24.0	105.237.249.239	105-237-249-239.access.mtnbusiness.co.za	0	0	0
2	South Africa	(Unknown)	-29.0	24.0	41.181.221.214	(None)	49	83	0
3	South Africa	(Unknown)	-29.0	24.0	41.181.221.213	(None)	0	503	0
4	South Africa	(Unknown)	-29.0	24.0	196.31.220.21	(None)	1	101	0
5	South Africa	(Unknown)	-29.0	24.0	197.242.144.102	www.afrihost.com.	0	3	0

My line stats' latency is bad, too (and it seems Telkom may have changed my upload speed):
linestats.png
 
Last edited:
No problem, I updated my location to the full name :) By the way, speeds are absolutely brilliant for me -- just under 4mbps. It's just latency for gaming. It is definitely either the Durban IPC or my exchange, though. Can you guys check if the 033 343 exchange is having problems? Telkom is so slow

There is nothing listed for the exchange on Telkom's notice board :(
 
There is nothing listed for the exchange on Telkom's notice board :(

Damn I hope it isn't a line issue. That would suck.
YouTube video showing lag spikes in accordance with gameplay (should be available in 1080p60):
[video=youtube;b_ShkgKdW9c]https://www.youtube.com/watch?v=b_ShkgKdW9c[/video]

EDIT: I took apart my grey box that the line connects to and one of the wires had snapped a little bit. Ping seems okay now... The telkom dude came and had a look at it the other day -.- guess he maybe bent the copper a bit much? Oh well. In any case, pings to international are about 230. Little high, but better than 4000. :) Still spikes to ~240ms here and there.
 
Last edited:
Tracing route to youtube.com [74.125.233.0]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.0.1
2 181 ms 112 ms 166 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.
1]
3 217 ms 335 ms 313 ms 41.181.221.214
4 385 ms 470 ms 466 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.
5.118]
5 649 ms * 337 ms xp-dca-1.za--xp-cr-1.za-a.mtnns.net [196.4
5]
6 324 ms 304 ms 341 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0
7 401 ms 536 ms 684 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.3

8 669 ms 559 ms 598 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.
7]
9 609 ms 653 ms 647 ms google-peering-ls-pr-2.uk.mtnns.net [209.2
13]
10 691 ms 542 ms 975 ms 209.85.255.76
11 526 ms 451 ms 416 ms 66.249.95.9
12 593 ms 581 ms 615 ms 72.14.237.239
13 579 ms 520 ms 795 ms jnb01s07-in-f0.1e100.net [74.125.233.0]
 
Tracing route to youtube.com [74.125.233.0]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.0.1
2 181 ms 112 ms 166 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.
1]
3 217 ms 335 ms 313 ms 41.181.221.214
4 385 ms 470 ms 466 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.
5.118]
5 649 ms * 337 ms xp-dca-1.za--xp-cr-1.za-a.mtnns.net [196.4
5]
6 324 ms 304 ms 341 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0
7 401 ms 536 ms 684 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.3

8 669 ms 559 ms 598 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.
7]
9 609 ms 653 ms 647 ms google-peering-ls-pr-2.uk.mtnns.net [209.2
13]
10 691 ms 542 ms 975 ms 209.85.255.76
11 526 ms 451 ms 416 ms 66.249.95.9
12 593 ms 581 ms 615 ms 72.14.237.239
13 579 ms 520 ms 795 ms jnb01s07-in-f0.1e100.net [74.125.233.0]

Your exchange is rekt, dude. No simple trick will help that. Contact Telkom and ask them to look at it or your line.

---
My mate on Axxess gets 17ms to Dota servers. I get anywhere between 60ms and 189ms.
 
Your exchange is rekt, dude. No simple trick will help that. Contact Telkom and ask them to look at it or your line.

---
My mate on Axxess gets 17ms to Dota servers. I get anywhere between 60ms and 189ms.

Thanks .... bud.

I had a chat with AH support via mail today .... I hope they have contacted Telkom
 
Damn I hope it isn't a line issue. That would suck.
YouTube video showing lag spikes in accordance with gameplay (should be available in 1080p60):
[video=youtube;b_ShkgKdW9c]https://www.youtube.com/watch?v=b_ShkgKdW9c[/video]

EDIT: I took apart my grey box that the line connects to and one of the wires had snapped a little bit. Ping seems okay now... The telkom dude came and had a look at it the other day -.- guess he maybe bent the copper a bit much? Oh well. In any case, pings to international are about 230. Little high, but better than 4000. :) Still spikes to ~240ms here and there.

That's not cool. Most people wouldn't be confident to take little those little boxes apart, luckily you thought to do that.

230ms is generally a little high for UK/EU, we like to see sub-200ms, but would be excellent for US traffic. I'd need to see the full trace to tell you more though.
 
Tracing route to youtube.com [74.125.233.0]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.0.1
2 181 ms 112 ms 166 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.
1]
3 217 ms 335 ms 313 ms 41.181.221.214
4 385 ms 470 ms 466 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.
5.118]
5 649 ms * 337 ms xp-dca-1.za--xp-cr-1.za-a.mtnns.net [196.4
5]
6 324 ms 304 ms 341 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0
7 401 ms 536 ms 684 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.3

8 669 ms 559 ms 598 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.
7]
9 609 ms 653 ms 647 ms google-peering-ls-pr-2.uk.mtnns.net [209.2
13]
10 691 ms 542 ms 975 ms 209.85.255.76
11 526 ms 451 ms 416 ms 66.249.95.9
12 593 ms 581 ms 615 ms 72.14.237.239
13 579 ms 520 ms 795 ms jnb01s07-in-f0.1e100.net [74.125.233.0]

Doesn't look too good from the exchange there. It could also be a line fault, but the inconsistency to me suggest exchange problems :(
 
Thanks .... bud.

I had a chat with AH support via mail today .... I hope they have contacted Telkom

It's very difficult to take exchange congestion problems forward, as we manage the line and not the exchange. But let's hope it's a line fault (sounds weird to say that) because that we can take forward and push for resolution :(
 
It's very difficult to take exchange congestion problems forward, as we manage the line and not the exchange. But let's hope it's a line fault (sounds weird to say that) because that we can take forward and push for resolution :(

No - point taken.

I did say before that Telkom are fiddling in the area too - just so long as a fault has been logged for the sake of completeness.
 
seeing as my TwitchTV is still not giving me more than 50kb/s

any progress on this?

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\xxx>tracert video40.lhr02.justin.tv

Tracing route to video40.lhr02.justin.tv [192.16.71.184]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router [192.168.2.1]
2 20 ms 20 ms 30 ms 105-236-5-1-esr-lo.mtnbusiness.co.za [105.236.5.
1]
3 21 ms 22 ms 20 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 21 ms 20 ms 20 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
5 21 ms 21 ms 48 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 165 ms 166 ms 166 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]

7 * 165 ms 164 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * ^C
C:\Users\xxx>tracert video40.lhr02.justin.tv

Tracing route to video40.lhr02.justin.tv [192.16.71.184]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router [192.168.2.1]
2 20 ms 20 ms 19 ms 105-236-5-1-esr-lo.mtnbusiness.co.za [105.236.5.
1]
3 22 ms 23 ms 27 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 43 ms 26 ms 21 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
5 22 ms 20 ms 21 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 165 ms 214 ms 166 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]

7 164 ms 168 ms 172 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
8 * * * Request timed out.
9 * ^C
C:\Users\xxx>
 
That's not cool. Most people wouldn't be confident to take little those little boxes apart, luckily you thought to do that.

230ms is generally a little high for UK/EU, we like to see sub-200ms, but would be excellent for US traffic. I'd need to see the full trace to tell you more though.

Sub-200? Is that even physically possible? Sometimes I used to get ~190ms on Telkom, but they have a different network route to MTN's. US traffic is usually 360+ms

Tracert using OVTR:
Code:
#	Country	Town	Lat	Lon	IP	Hostname	Latency (ms)	Dns lookup (ms)	Distance to previous node (km)
1	South Africa	(Unknown)	-29.0	24.0	105.210.37.165	105.210.37.165	0	0	0
2	South Africa	(Unknown)	-29.0	24.0	41.181.221.213	(None)	53	52	0
3	South Africa	(Unknown)	-29.0	24.0	41.181.165.118	rb-dca-2.za--qux-b.za.mtnbusiness.net.	43	50	0
4	South Africa	(Unknown)	-29.0	24.0	41.181.221.214	(None)	1	50	0
5	South Africa	(Unknown)	-29.0	24.0	196.44.0.155	xp-dca-1.za--xp-cr-1.za-a.mtnns.net.	102	54	0
6	South Africa	(Unknown)	-29.0	24.0	196.44.0.42	jh-cr-1.za--rb-cr-2.za.mtnns.net.	3	51	0
7	United Kingdom	(Unknown)	51.5	-0.13000488	132.185.254.109	ae0.er01.telhc.bbc.co.uk.	3	50	9267
8	United Kingdom	London	51.514206	-0.09309387	195.66.224.103	bbc-linx.pr01.thdow.bbc.co.uk.	3	49	3
9	United Kingdom	(Unknown)	51.5	-0.13000488	132.185.255.149	(None)	1	52	3
10	United Kingdom	Tadworth	51.283295	-0.23330688	212.58.244.18	fmt-vip72.telhc.bbc.co.uk.	2	49	25

Windows Tracert:
Code:
Tracing route to bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3    56 ms    95 ms    46 ms  41.181.221.213
  4    46 ms    45 ms    45 ms  41.181.221.214
  5    45 ms    71 ms    42 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
  6   244 ms   244 ms   244 ms  xp-dca-1.za--xp-cr-1.za-a.mtnns.net [196.44.0.15
5]
  7   273 ms   244 ms   257 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  8   243 ms   244 ms   244 ms  ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
  9   272 ms   238 ms   237 ms  ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
 10   244 ms   244 ms   243 ms  bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13   239 ms   239 ms   240 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
 14   240 ms   240 ms   238 ms  132.185.255.149
 15   247 ms   244 ms   244 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X