Afrihost Business Uncapped Feedback - 2

[AfriGenie]

My account is not authenticating. It was connected but had stopped working with no throughtput. After rebooting the router, it failed to authenticate.

I'm getting reports of a few Exchange-related issues at the moment, could you please send me a PM with your ADSL username so that I can follow-up on this for you.

 

[Gatecrasher]

I'm getting reports of a few Exchange-related issues at the moment, could you please send me a PM with your ADSL username so that I can follow-up on this for you.

PM Sent.

 

[AfriGenie]

PM Sent.

Got it! Thanks.

 

[Francois Marais]

Counting... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10... Ah ***** this. AH, you are better than this...
http://www.speedtest.net/my-result/4188783983
http://www.speedtest.net/my-result/4188797662

What is wrong this time, and will we be without connection for months again. Should I get a new ISP and please don't tell me to try another account and settings and all that. I don't have time for that **** today.

 

[AfriGuy]

Counting... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10... Ah ***** this. AH, you are better than this...
http://www.speedtest.net/my-result/4188783983
http://www.speedtest.net/my-result/4188797662

What is wrong this time, and will we be without connection for months again. Should I get a new ISP and please don't tell me to try another account and settings and all that. I don't have time for that **** today.

The latency is crazy high
Would you mind posting a traceroute here please?

 

[Francois Marais]

The latency is crazy high
Would you mind posting a traceroute here please?

traceroute to google.co.za (216.58.223.35), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 0.877 ms 0.407 ms 0.373 ms
2 105-236-3-193-esr-lo.mtnbusiness.co.za (105.236.3.193) 266.914 ms 341.002 ms 333.054 ms
3 ipc-recieve-rb-3a.za.mtnbusiness.net (41.181.178.77) 302.047 ms 237.423 ms 210.757 ms
4 rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120) 237.491 ms 231.631 ms
rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 229.976 ms
5 jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 220.779 ms
jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 226.680 ms
jh-cr-2.za--rb-cr-1.za-b.mtnns.net (196.44.31.171) 238.699 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 228.650 ms 240.485 ms 229.818 ms
7 ls-cr-2.uk--rb-cr-1.za.mtnns.net (196.44.31.114) 406.200 ms 445.332 ms 498.245 ms
8 ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 397.124 ms 317.404 ms 326.629 ms
9 google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 325.291 ms 347.896 ms 340.733 ms
10 209.85.255.76 (209.85.255.76) 352.712 ms 386.495 ms 365.645 ms
11 66.249.95.9 (66.249.95.9) 408.661 ms 391.427 ms 486.328 ms
12 72.14.239.129 (72.14.239.129) 457.615 ms 351.875 ms 352.939 ms
13 jnb01s08-in-f3.1e100.net (216.58.223.35) 341.339 ms 342.432 ms 397.007 ms
Francoiss-MacBook-Air-2

 

[electrofreeze]

yes problems started again after 6pm

 

[Francois Marais]

traceroute to up.ac.za (137.215.10.70), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 0.842 ms 0.429 ms 0.373 ms
2 105-236-3-193-esr-lo.mtnbusiness.co.za (105.236.3.193) 226.418 ms 254.927 ms 302.396 ms
3 ipc-recieve-rb-1a.za.mtnbusiness.net (41.181.178.53) 342.220 ms 361.418 ms 387.851 ms
4 rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 252.621 ms 180.450 ms 107.672 ms
5 jh-cr-2.za--rb-cr-1.za-b.mtnns.net (196.44.31.171) 113.446 ms 15.144 ms
jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 18.706 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 16.328 ms 15.796 ms 13.761 ms
7 196.44.0.72 (196.44.0.72) 43.255 ms
jh-pr-1.za--jh-cr-2.za.mtnns.net (196.44.0.222) 18.180 ms
196.44.0.72 (196.44.0.72) 21.829 ms
8 tenet.jinx.net.za (196.223.14.33) 49.109 ms 23.526 ms 22.407 ms
9 te4-1-jnb1-pe1-n.tenet.ac.za (155.232.6.109) 32.796 ms 104.805 ms 68.151 ms
10 te8-1-jnb2-pe1-n.tenet.ac.za (155.232.6.78) 62.189 ms 82.033 ms 62.024 ms
11 te0-12-0-0-jnb2-p1-n.tenet.ac.za (155.232.7.157) 49.615 ms 74.901 ms 118.486 ms
12 te0-1-0-2-pta1-p1-n.tenet.ac.za (155.232.6.26) 128.500 ms 137.925 ms 188.479 ms
13 te8-4-pta1-pe1.tenet.ac.za (155.232.6.130) 180.810 ms 162.077 ms 192.799 ms
14 thermopylae-tenet.up.ac.za (137.215.99.2) 178.953 ms 193.421 ms 217.998 ms
15 linus.up.ac.za (137.215.97.20) 166.593 ms 164.035 ms 183.373 ms

 

[Francois Marais]

wait, it gets better:
traceroute to google.co.za (216.58.223.35), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 0.627 ms 0.499 ms 0.389 ms
2 105-236-3-193-esr-lo.mtnbusiness.co.za (105.236.3.193) 389.450 ms 444.860 ms 504.563 ms
3 ipc-recieve-rb-3a.za.mtnbusiness.net (41.181.178.77) 551.861 ms 508.476 ms 435.397 ms
4 rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120) 425.271 ms 440.319 ms 422.133 ms
5 jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 352.570 ms 370.380 ms 308.876 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 309.482 ms 307.332 ms 309.677 ms
7 ls-cr-2.uk--rb-cr-1.za.mtnns.net (196.44.31.114) 486.353 ms 500.936 ms 505.143 ms
8 ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 457.690 ms 447.034 ms 438.499 ms
9 google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 447.626 ms 445.722 ms 446.382 ms
10 209.85.255.76 (209.85.255.76) 489.524 ms 474.755 ms 475.187 ms
11 66.249.95.9 (66.249.95.9) 475.833 ms 487.745 ms 477.266 ms
12 72.14.239.129 (72.14.239.129) 472.845 ms 457.563 ms 465.850 ms
13 jnb01s08-in-f3.1e100.net (216.58.223.35) 489.092 ms 437.146 ms 438.616 ms

 

[Francois Marais]

and with Axxess:
traceroute to google.co.za (216.58.223.35), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 0.533 ms 0.367 ms 0.342 ms
2 105-236-3-193-esr-lo.mtnbusiness.co.za (105.236.3.193) 118.918 ms 128.550 ms 130.455 ms
3 ipc-recieve-rb-3a.za.mtnbusiness.net (41.181.178.77) 119.425 ms 133.011 ms 179.336 ms
4 rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 147.729 ms
rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120) 155.533 ms
rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 138.717 ms
5 jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 194.196 ms
jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 113.141 ms
jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 148.215 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 127.113 ms 145.626 ms 140.492 ms
7 ls-cr-2.uk--rb-cr-1.za.mtnns.net (196.44.31.114) 247.425 ms 272.627 ms 248.871 ms
8 ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 241.243 ms 245.738 ms 248.691 ms
9 google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 266.420 ms 318.943 ms 259.896 ms
10 209.85.255.76 (209.85.255.76) 258.146 ms 278.883 ms 317.728 ms
11 66.249.95.9 (66.249.95.9) 325.228 ms 319.787 ms 284.835 ms
12 72.14.239.129 (72.14.239.129) 300.676 ms 384.780 ms 423.980 ms
13 jnb01s08-in-f3.1e100.net (216.58.223.35) 506.905 ms 604.112 ms 655.258 ms

 

[KoolDaffy]

My account is not authenticating. It was connected but had stopped working with no throughtput. After rebooting the router, it failed to authenticate.

Mine also having that issue periodically. Seems okay now though.

 

[AfriMan]

traceroute to google.co.za (216.58.223.35), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 0.877 ms 0.407 ms 0.373 ms
2 105-236-3-193-esr-lo.mtnbusiness.co.za (105.236.3.193) 266.914 ms 341.002 ms 333.054 ms
3 ipc-recieve-rb-3a.za.mtnbusiness.net (41.181.178.77) 302.047 ms 237.423 ms 210.757 ms
4 rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120) 237.491 ms 231.631 ms
rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 229.976 ms
5 jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 220.779 ms
jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 226.680 ms
jh-cr-2.za--rb-cr-1.za-b.mtnns.net (196.44.31.171) 238.699 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 228.650 ms 240.485 ms 229.818 ms
7 ls-cr-2.uk--rb-cr-1.za.mtnns.net (196.44.31.114) 406.200 ms 445.332 ms 498.245 ms
8 ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 397.124 ms 317.404 ms 326.629 ms
9 google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 325.291 ms 347.896 ms 340.733 ms
10 209.85.255.76 (209.85.255.76) 352.712 ms 386.495 ms 365.645 ms
11 66.249.95.9 (66.249.95.9) 408.661 ms 391.427 ms 486.328 ms
12 72.14.239.129 (72.14.239.129) 457.615 ms 351.875 ms 352.939 ms
13 jnb01s08-in-f3.1e100.net (216.58.223.35) 341.339 ms 342.432 ms 397.007 ms
Francoiss-MacBook-Air-2

From all the traces you've posted this looks to me like congestion on your local exchange. Remember that you're second hop is still on Telkom's infrastructure, before actually entering the MTN network. So this means that you're latency increases somewhere between your router and the last point in Telkom's network (probably the BRAS or BNG).

 

[Francois Marais]

Well seems it started working again last night. Will see when I return if it is still useless or not.

 

[b1scu1t]

So I've been in a massive mission with Telkom and still my problems persist which started in July 2014.
On I think 8 Feb I made a complaint on HelloPeter which finally got someones attention, after I reported the problem on 1 Feb and didn't hear anything from Telkom.
Made another complaint at the end of February after the USELESS tech was just wasting everyone's time.
Pitches up, checks something out, tells me the line is F***ing around and then leaves and only comes back days later to repeat the process. He sat here trying to log into his Telkom account almost 10 TIMES but couldn't remember his login details couldn't write my cellphone number down correctly and also couldn't get my Telkom line number correct, phoning and asking for reports of a different number [facepalm]

Telkom was here yesterday, changing stuff at the exchange, at some main box as well as changing the line connecting my house to the nearest pole. SNR went up a little but my latency issues STILL persist.

Still got over 1200ms latency last night with a whole lot of time out issues.

Another tech phoned once and asked about congestion and said they moved my line to another group of ports only standing at 16% capacity.

I just don't get HOW can this be BEYOND impossible to fix I've lost online studying work due to time outs and this we started playing Battlefield competitively and these issues has caused so many problems We can forget about placing in DGL summer leg Disconnected from two rounds last Sunday causing us to lose the rounds...

ANY ideas what can cause latency issues such as this that looks similar to exchange congestion?

 

[AfriGenie]

So I've been in a massive mission with Telkom and still my problems persist which started in July 2014.
On I think 8 Feb I made a complaint on HelloPeter which finally got someones attention, after I reported the problem on 1 Feb and didn't hear anything from Telkom.
Made another complaint at the end of February after the USELESS tech was just wasting everyone's time.
Pitches up, checks something out, tells me the line is F***ing around and then leaves and only comes back days later to repeat the process. He sat here trying to log into his Telkom account almost 10 TIMES but couldn't remember his login details couldn't write my cellphone number down correctly and also couldn't get my Telkom line number correct, phoning and asking for reports of a different number [facepalm]

Telkom was here yesterday, changing stuff at the exchange, at some main box as well as changing the line connecting my house to the nearest pole. SNR went up a little but my latency issues STILL persist.

Still got over 1200ms latency last night with a whole lot of time out issues.

Another tech phoned once and asked about congestion and said they moved my line to another group of ports only standing at 16% capacity.

I just don't get HOW can this be BEYOND impossible to fix I've lost online studying work due to time outs and this we started playing Battlefield competitively and these issues has caused so many problems We can forget about placing in DGL summer leg Disconnected from two rounds last Sunday causing us to lose the rounds...

ANY ideas what can cause latency issues such as this that looks similar to exchange congestion?

Those are some painful latencies...

If there is damage on the ADSL line or even on your Port at the Exchange you would definitely see a significant jump in latency as well.

Would it be possible to post a traceroute to Afrihost.com and Google.com?

That would give a bit more detail than a normal ping.

 

[b1scu1t]

Those are some painful latencies...

If there is damage on the ADSL line or even on your Port at the Exchange you would definitely see a significant jump in latency as well.

Would it be possible to post a traceroute to Afrihost.com and Google.com?

That would give a bit more detail than a normal ping.

I'll post a traceroute when it happens again tonight. But that's the weird thing I'm trying to figure out.
If it's damage somewhere, wouldn't I have unstable and high latency all the time?
If not and this is damage, well then I'll just keep on logging faults and complaints on hellopeter LOL... I'll keep them busy until they replace whatever needs to be replaced

My SNR went up yesterday after they replaced the line leading to my house. At about 14.7dB now. I NEVER get any disconnects but the latency problems is inconsistent. It doesn't always happen at exactly the same times of the day. It surely looks like it's related to the total traffic usage in the area because it mostly happens after hours and stops when more people go to sleep.
But Telkom keeps saying it's not congested cause the group of ports I was moved to is only at 16% capacity... Whether this is true or not, I wouldn't know. I don't know enough about those things to challenge them or ask questions

 

[AfriGenie]

I'll post a traceroute when it happens again tonight. But that's the weird thing I'm trying to figure out.
If it's damage somewhere, wouldn't I have unstable and high latency all the time?
If not and this is damage, well then I'll just keep on logging faults and complaints on hellopeter LOL... I'll keep them busy until they replace whatever needs to be replaced

My SNR went up yesterday after they replaced the line leading to my house. At about 14.7dB now. I NEVER get any disconnects but the latency problems is inconsistent. It doesn't always happen at exactly the same times of the day. It surely looks like it's related to the total traffic usage in the area because it mostly happens after hours and stops when more people go to sleep.
But Telkom keeps saying it's not congested cause the group of ports I was moved to is only at 16% capacity... Whether this is true or not, I wouldn't know. I don't know enough about those things to challenge them or ask questions

If it only happens in the early evening, it is more likely to be congestion than anything else, and to say that the card you are connected to is only at 16% can be slightly misleading, as the actual Exchange can very easily be congested even if the card has open slots.

My apologies for not being able to give you an exact idea, but he traceroute will help a lot in determining the cause of the latency.

 

[b1scu1t]

If it only happens in the early evening, it is more likely to be congestion than anything else, and to say that the card you are connected to is only at 16% can be slightly misleading, as the actual Exchange can very easily be congested even if the card has open slots.

My apologies for not being able to give you an exact idea, but he traceroute will help a lot in determining the cause of the latency.

It's most often between about 9-11:30pm during the weekdays and on rarely on saturdays but sometimes on sundays after about 2pm.

I didn't fully understand everything about the cards but what I tried to figure out, asking the tech a bunch of questions is that he phoned about the capacity at 2pm when everything is perfectly fine... how about phoning at 10pm when I actually have problems?

This is pretty much the only place I can think of where someone isn't gonna lie to me in order to save money so I appreciate ANY opinions and advice.

Will update later tonight if the problem pops up

 

[AfriMan]

It's most often between about 9-11:30pm during the weekdays and on rarely on saturdays but sometimes on sundays after about 2pm.

I didn't fully understand everything about the cards but what I tried to figure out, asking the tech a bunch of questions is that he phoned about the capacity at 2pm when everything is perfectly fine... how about phoning at 10pm when I actually have problems?

This is pretty much the only place I can think of where someone isn't gonna lie to me in order to save money so I appreciate ANY opinions and advice.

Will update later tonight if the problem pops up

Telkom do have specialised units that can monitor your line over a 24 hour period for issues like this, especially intermittent connectivity. However, as far as congestion goes, that is also a regular report that receive on exchanges and their utilisation (separate from the percentage of ports available). But I guess the thing is they need to see what you are seeing in order to be convinced that there is an issue and the issue is what they think it is.

I don't think we'll ever get a tech to call you at 10pm though, but they can monitor overnight and call you the next day with feedback.

 

[Gavin107]

I have business uncapped Afrihost. In general it is a good experience.

But, what does it mean if the latency is reasonable (18ms to 197.242.144.102 and 216ms to 8.8.8.8); SAIX speedtest local to Rosebank (from Durban) is about 3.5Mbs on a 4Mps line; but all international downloads are painfully slow (over 2 hours now to extract a mere 9Mb from a Microsoft update service to load a SQL server patch).

It has been like this most of today - rebooted router. Mac etc. Is this my setup, exchange congestion or something on the Afrihost/MTN link to international services. Mybroadband speedtest showing international downloads today are on average 300kps (always slower than uploads today). Rdio streaming has been practically useless since about 7:30am and I use this as an test to see if there is something awry.

But local speeds are fine. Where is the congestion - what does an increasingly frustrated business DSL user do? How to report this? Nothing appears on the main Afrihost site to indicate a problem; everything is "running like a bomb".

I don't have the inclination to go to the help desk and go through the painful diagnostic process that focuses on my line (which I think is OK), and I am forced to live from day to day in anticipation. Tomorrow it might be perfect, or not.