Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
Got problems at my place.. Telkom recreated the port and it seemed to improve for a few minutes, like it usually does and then went back to crappy :(

Is this on Telkom/Line side or ISP side tho? After recreating port and restarting it was better
TraceRoute:
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  2.141 ms  8.498 ms  1.142 ms
[B] 2  105-236-4-129-esr-lo.mtnbusiness.co.za (105.236.4.129)  111.333 ms  212.323 ms  389.947 ms[/B]
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  582.877 ms  1274.329 ms  1564.921 ms
 4  rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146)  2237.940 ms  2408.663 ms
    rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120)  3050.368 ms
 5  jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95)  3370.326 ms
    jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42)  4031.180 ms^C

And then a few minutes later it reverts to this..
TraceRoute:
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  12.011 ms  1.486 ms  1.200 ms
[B] 2  105-236-4-129-esr-lo.mtnbusiness.co.za (105.236.4.129)  4104.581 ms  4176.963 ms  4088.098 ms[/B]
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  4303.215 ms  4148.670 ms *
 4  * * *
 5  * * *
 6  *^C
 
AfriGuy said:
It's not listed due to the factors I've mentioned in my previous post.
Click to expand...

Those factors being?

Maybe you should read through my support tickets over the past month where even your critical care admit that things aren't running as they should lately. I find it hard to believe I was the only person being effected.
 
caroper said:
Afrihost is unusable, that is why I have purchased Telkom Data and used it all month so far.
Posting the tests above took 45 min out of my day, swiching ISP's running tests etc.
That 45 min of billable time is another cost to me on top of the Telkom account cost.

I am back on Telkom now, so I can try and get some productive work done, so thanks for yet another excuse and blaming the tools rather than addressing the problem, but I have no more time to waist on running countless and pointless tests for the sake of your PR and stalling tactics.
Click to expand...

I'm not trying to point the finger at anything here, just looking at this for what it is.
When you have some time, please PM me your DSL username along with some results from speedtest.net so I can determine why your speeds are so poor.
 
Davedes said:
Those factors being?

Maybe you should read through my support tickets over the past month where even your critical care admit that things aren't running as they should lately. I find it hard to believe I was the only person being effected.
Click to expand...

AfriGuy said:
I think we've discussed the noticeboard status at length already, it's based on the severity of the issue and run on what percentage of clients is affected.
We had it updated the other day around high latency, as one example.

I'm sorry you aren't happy, but I need to stress that we're not lying, trying to blind or insult our clients in any way. I really do understand that you're upset, but throwing these accusations around makes it really challenging to engage with you.
Click to expand...

Please read through my posts, we're not admitting that things are perfect here either. So I'm not really sure where this is going?
 
krycor said:
Got problems at my place.. Telkom recreated the port and it seemed to improve for a few minutes, like it usually does and then went back to crappy :(

Is this on Telkom/Line side or ISP side tho? After recreating port and restarting it was better
TraceRoute:
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  2.141 ms  8.498 ms  1.142 ms
[B] 2  105-236-4-129-esr-lo.mtnbusiness.co.za (105.236.4.129)  111.333 ms  212.323 ms  389.947 ms[/B]
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  582.877 ms  1274.329 ms  1564.921 ms
 4  rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146)  2237.940 ms  2408.663 ms
    rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120)  3050.368 ms
 5  jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95)  3370.326 ms
    jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42)  4031.180 ms^C

And then a few minutes later it reverts to this..
TraceRoute:
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  12.011 ms  1.486 ms  1.200 ms
[B] 2  105-236-4-129-esr-lo.mtnbusiness.co.za (105.236.4.129)  4104.581 ms  4176.963 ms  4088.098 ms[/B]
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  4303.215 ms  4148.670 ms *
 4  * * *
 5  * * *
 6  *^C
Click to expand...

Holy moly, that's the highest latency I've seen in a while o.0
This looks like massive congestion or a serious problem on the exchange. Is your line with us?
 
AfriGuy said:
I'm not trying to point the finger at anything here, just looking at this for what it is.
When you have some time, please PM me your DSL username along with some results from speedtest.net so I can determine why your speeds are so poor.
Click to expand...

Ok I reread your post, and calmed down a little bit, so here is the retest on Afrihost:

197257738.png197258780.png

This time the Cape Town speed is better but that latency is ridiculous and Jhb is definitely an issue.
And you all have my Account name in PM already, I have sent it often enough, this is not a line problem or an account issue, it is an Afrihost/MTN capacity issue.
 
AfriGuy said:
Please read through my posts, we're not admitting that things are perfect here either. So I'm not really sure where this is going?
Click to expand...

Please explain how you determine what percentage of clients are being affected?

This is going in the direction of their have been hundreds of post about the same issues many of your clients are experiencing yet "the network is running like a bomb"
 
AfriGuy said:
There shouldn't be such big discrepancies in terms of throughput here though, this definitely isn't normal nor widespread across the region. Without pointing fingers either, but I've seen feedback in this thread that the MyBB speedtest has been a little erratic as of late. Does your overall experience fall in line with the results you've pasted here?

Would you mind running some tests over on speedtest.net too please?
Here's one from my place. Wynberg, CPT.

4361378734.png


EDIT: Yeah, definitely something weird happening on the MyBB speedtest. Compare to what I've pasted above
197255798.png
Click to expand...

Again this issue between the speed differences of Mybroadband speed test and Speedtest.net only affects Afrihost clients.

Just shows you how stuffed up is the "No shaping" policy
 
ID_10_T said:
Again this issue between the speed differences of Mybroadband speed test and Speedtest.net only affects Afrihost clients.

Just shows you how stuffed up is the "No shaping" policy
Click to expand...

I must say that it doesn't only affect Afrihost. I ran the tests across Web Africa, crystal web, Afrihost and telkom. Only telkom is getting low pings and full speed on the my BB speed test.
 
caroper said:
Ok I reread your post, and calmed down a little bit, so here is the retest on Afrihost:

View attachment 216328View attachment 216330

This time the Cape Town speed is better but that latency is ridiculous and Jhb is definitely an issue.
And you all have my Account name in PM already, I have sent it often enough, this is not a line problem or an account issue, it is an Afrihost/MTN capacity issue.
Click to expand...

Have you looked at my results I pasted though? Running the MyBB test app shows entirely different results and isn't a reflection on my line.
Please past a test from speedtest.net and advise on your overall throughput on the line based on downloads.
 
ID_10_T said:
Again this issue between the speed differences of Mybroadband speed test and Speedtest.net only affects Afrihost clients.

Just shows you how stuffed up is the "No shaping" policy
Click to expand...

Not from what I've seen, according to posts around the forum Telkom accounts seem to work as a true reflection.
Shaping has nothing to do with these tests.
 
krycor said:
Got problems at my place.. Telkom recreated the port and it seemed to improve for a few minutes, like it usually does and then went back to crappy :(

Is this on Telkom/Line side or ISP side tho? After recreating port and restarting it was better
TraceRoute:
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  2.141 ms  8.498 ms  1.142 ms
[B] 2  105-236-4-129-esr-lo.mtnbusiness.co.za (105.236.4.129)  111.333 ms  212.323 ms  389.947 ms[/B]
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  582.877 ms  1274.329 ms  1564.921 ms
 4  rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146)  2237.940 ms  2408.663 ms
    rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120)  3050.368 ms
 5  jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95)  3370.326 ms
    jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42)  4031.180 ms^C

And then a few minutes later it reverts to this..
TraceRoute:
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  12.011 ms  1.486 ms  1.200 ms
[B] 2  105-236-4-129-esr-lo.mtnbusiness.co.za (105.236.4.129)  4104.581 ms  4176.963 ms  4088.098 ms[/B]
 3  ipc-recieve-rb-4a.za.mtnbusiness.net (41.181.178.89)  4303.215 ms  4148.670 ms *
 4  * * *
 5  * * *
 6  *^C
Click to expand...

Using my FNB Connect account (Thank for a goodness I get 3GB freebie). I didnt resync this time, just changed password..
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  2.531 ms  1.414 ms  1.335 ms
 2  41.183.22.1 (41.183.22.1)  11.432 ms  11.170 ms  10.986 ms
 3  41.183.141.25 (41.183.141.25)  13.556 ms  15.663 ms  13.571 ms
 4  41.183.132.69 (41.183.132.69)  25.474 ms  14.577 ms  25.542 ms
 5  41.183.132.82 (41.183.132.82)  18.590 ms  15.132 ms  14.255 ms
 6  google.jb1.napafrica.net (196.46.25.166)  42.970 ms  45.179 ms  44.662 ms
 7  72.14.237.239 (72.14.237.239)  23.522 ms  26.483 ms  32.981 ms
^Z

And a few minutes later..
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  1.554 ms  1.190 ms  1.075 ms
 2  41.183.22.1 (41.183.22.1)  11.062 ms  11.465 ms  11.499 ms
 3  41.183.141.25 (41.183.141.25)  13.793 ms  14.101 ms  14.351 ms
 4  41.183.132.69 (41.183.132.69)  23.412 ms  17.841 ms  35.440 ms
 5  * 41.183.132.82 (41.183.132.82)  15.011 ms  14.121 ms
 6  google.jb1.napafrica.net (196.46.25.166)  35.185 ms  32.746 ms  28.522 ms
 7  72.14.237.239 (72.14.237.239)  20.603 ms  17.222 ms  17.507 ms


So wtf is u with the MTN ESR ???

Telkom Line ADSL, 2Mbps, Afrihost big capped account. 012 656 XXXX

Note sure if maybe that esr is just suffering it its a local/regional one?
 
Last edited:
Davedes said:
Please explain how you determine what percentage of clients are being affected?

This is going in the direction of their have been hundreds of post about the same issues many of your clients are experiencing yet "the network is running like a bomb"
Click to expand...

To repeat what's been discussed already, we have a team that decides what gets posted. And it's based on factors, metrics and trends. I get that you want everything posted on the noticeboard, we try and keep it as concise as possible. I don't think you need to look at this as us trying to hide any issues from clients.
 
krycor said:
Using my FNB Connect account (Thank for a goodness I get 3GB freebie). I didnt resync this time, just changed password..
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  2.531 ms  1.414 ms  1.335 ms
 2  41.183.22.1 (41.183.22.1)  11.432 ms  11.170 ms  10.986 ms
 3  41.183.141.25 (41.183.141.25)  13.556 ms  15.663 ms  13.571 ms
 4  41.183.132.69 (41.183.132.69)  25.474 ms  14.577 ms  25.542 ms
 5  41.183.132.82 (41.183.132.82)  18.590 ms  15.132 ms  14.255 ms
 6  google.jb1.napafrica.net (196.46.25.166)  42.970 ms  45.179 ms  44.662 ms
 7  72.14.237.239 (72.14.237.239)  23.522 ms  26.483 ms  32.981 ms
^Z

And a few minutes later..
Code: 
traceroute google.com
traceroute to google.com (216.58.223.14), 64 hops max, 52 byte packets
 1  10.0.0.1 (10.0.0.1)  1.554 ms  1.190 ms  1.075 ms
 2  41.183.22.1 (41.183.22.1)  11.062 ms  11.465 ms  11.499 ms
 3  41.183.141.25 (41.183.141.25)  13.793 ms  14.101 ms  14.351 ms
 4  41.183.132.69 (41.183.132.69)  23.412 ms  17.841 ms  35.440 ms
 5  * 41.183.132.82 (41.183.132.82)  15.011 ms  14.121 ms
 6  google.jb1.napafrica.net (196.46.25.166)  35.185 ms  32.746 ms  28.522 ms
 7  72.14.237.239 (72.14.237.239)  20.603 ms  17.222 ms  17.507 ms


So wtf is u with the MTN ESR ???
Click to expand...

Now that's a weird one.
Drop me a PM with your line number and any other results you've run - I'll check this out from my end :)

Just a note, that we cannot control nor own the hardware on the 2nd hop. Traffic breaks out to our IPC after that.
 
AfriGuy said:
To repeat what's been discussed already, we have a team that decides what gets posted. And it's based on factors, metrics and trends. I get that you want everything posted on the noticeboard, we try and keep it as concise as possible. I don't think you need to look at this as us trying to hide any issues from clients.
Click to expand...

Lol ok.

Simple question that requires a simple yes or no.

Are there capacity issues at the moment?
 
ID_10_T said:
Again this issue between the speed differences of Mybroadband speed test and Speedtest.net only affects Afrihost clients.

Just shows you how stuffed up is the "No shaping" policy
Click to expand...

Very true, if two accounts are tested against the same test server it is the relative performance that counts, not the server involved, as any errors induced by the server should effect both accounts equally.

Have the Network Engineers optimised the Routing to OOLKA? Who knows, but with all the Damage Control and Head Hiding going on at Afrihost right now It would not surprise me one bit.
 
caroper said:
Very true, if two accounts are tested against the same test server it is the relative performance that counts, not the server involved, as any errors induced by the server should effect both accounts equally.

Have the Network Engineers optimised the Routing to OOLKA? Who knows, but with all the Damage Control and Head Hiding going on at Afrihost right now It would not surprise me one bit.
Click to expand...

I think you're straying a bit here. The MyBB test also uses Ookla, so I fail to see how we've optimised something to reflect false results.

Could you run some real world results? Some streaming, downloads etc.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X