Afrihost Business Uncapped Feedback

Status
Not open for further replies.
MagicDude4Eva said:
Here the traceroute
Click to expand...

traceroute to 206.127.146.48 (206.127.146.48), 64 hops max, 52 byte packets
1 netgear.muffin.lan (172.16.0.1) 2.967 ms 1.142 ms 1.116 ms
2 105-236-6-129-esr-lo.mtnbusiness.co.za (105.236.6.129) 358.840 ms 293.829 ms 300.675 ms << Here is your problem congested exchange....
3 ipc-recieve-jh-1a.za.mtnbusiness.net (41.181.178.5) 313.807 ms 269.427 ms 189.940 ms
4 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 212.225 ms 165.701 ms 152.794 ms
5 jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114) 133.208 ms 136.510 ms 153.637 ms
6 am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141) 357.239 ms 346.030 ms 318.357 ms
7 xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89) 336.750 ms 346.707 ms 355.350 ms
8 4.69.162.129 (4.69.162.129) 361.512 ms 376.544 ms
4.69.162.137 (4.69.162.137) 335.385 ms
9 ae-56-111.ebr1.amsterdam1.level3.net (4.69.153.185) 349.278 ms
ae-59-114.ebr1.amsterdam1.level3.net (4.69.153.197) 362.563 ms
ae-58-113.ebr1.amsterdam1.level3.net (4.69.153.193) 351.470 ms
10 ae-47-47.ebr2.dusseldorf1.level3.net (4.69.143.206) 355.532 ms
ae-48-48.ebr2.dusseldorf1.level3.net (4.69.143.210) 399.033 ms
ae-45-45.ebr2.dusseldorf1.level3.net (4.69.143.198) 391.355 ms
11 ae-21-21.ebr1.dusseldorf1.level3.net (4.69.143.181) 314.806 ms
ae-23-23.ebr1.dusseldorf1.level3.net (4.69.143.189) 353.240 ms
ae-22-22.ebr1.dusseldorf1.level3.net (4.69.143.185) 351.306 ms
12 ae-48-48.ebr3.frankfurt1.level3.net (4.69.143.178) 334.543 ms 331.555 ms
ae-45-45.ebr3.frankfurt1.level3.net (4.69.143.166) 341.779 ms
13 ae-93-93.csw4.frankfurt1.level3.net (4.69.163.14) 335.309 ms
ae-63-63.csw1.frankfurt1.level3.net (4.69.163.2) 375.833 ms 321.500 ms
14 ae-2-70.edge6.frankfurt1.level3.net (4.69.154.74) 318.873 ms
ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138) 359.192 ms
ae-1-60.edge6.frankfurt1.level3.net (4.69.154.10) 311.028 ms
15 195.16.161.58 (195.16.161.58) 498.172 ms 514.045 ms 503.822 ms
16 206-127-157-86.plaync.com (206.127.157.86) 496.578 ms 605.655 ms 662.136 ms
17 206-127-157-102.plaync.com (206.127.157.102) 580.107 ms 600.528 ms 594.065 ms
18 206-127-157-102.plaync.com (206.127.157.102) 510.618 ms !X 524.339 ms !X 506.410 ms !X
 
Hummercellc said:
Afriman,

Could you ask the powers that be, if they will be looking into line bonding.... Please Please... :D
Click to expand...

I don't think that there are any immediate plans for this type of product.
Also remember that VDSL is/ will be a cheaper options in terms of speed vs value for money :)
 
AfriGuy said:
I don't think that there are any immediate plans for this type of product.
Also remember that VDSL is/ will be a cheaper options in terms of speed vs value for money :)
Click to expand...

But at the rate Telkom are going, I will be in my grave before little old Richmond gets VDSL. :D
 
Hummercellc said:
traceroute to 206.127.146.48 (206.127.146.48), 64 hops max, 52 byte packets
1 netgear.muffin.lan (172.16.0.1) 2.967 ms 1.142 ms 1.116 ms
2 105-236-6-129-esr-lo.mtnbusiness.co.za (105.236.6.129) 358.840 ms 293.829 ms 300.675 ms << Here is your problem congested exchange....
3 ipc-recieve-jh-1a.za.mtnbusiness.net (41.181.178.5) 313.807 ms 269.427 ms 189.940 ms
...
Click to expand...

Pretty much varies - like this morning:
PHP: 
traceroute to 206.127.159.241 (206.127.159.241), 64 hops max, 52 byte packets
 1  netgear.muffin.lan (172.16.0.1)  2.531 ms  1.570 ms  1.884 ms
 2  105-236-6-129-esr-lo.mtnbusiness.co.za (105.236.6.129)  11.785 ms  10.242 ms  14.579 ms
 3  ipc-recieve-jh-2a.za.mtnbusiness.net (41.181.178.17)  14.054 ms  17.502 ms  17.149 ms
 4  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  15.599 ms  18.634 ms  13.917 ms
 5  jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114)  17.558 ms  12.863 ms  12.803 ms
 6  am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141)  204.142 ms  203.099 ms  207.164 ms
 7  xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89)  205.682 ms  239.775 ms  206.511 ms
 8  4.69.162.133 (4.69.162.133)  212.757 ms
    4.69.162.137 (4.69.162.137)  228.794 ms
    4.69.162.129 (4.69.162.129)  213.269 ms
 9  ae-59-114.ebr1.amsterdam1.level3.net (4.69.153.197)  228.377 ms
    ae-56-111.ebr1.amsterdam1.level3.net (4.69.153.185)  228.601 ms
    ae-59-114.ebr1.amsterdam1.level3.net (4.69.153.197)  229.621 ms
10  ae-47-47.ebr2.dusseldorf1.level3.net (4.69.143.206)  219.571 ms  212.064 ms
    ae-45-45.ebr2.dusseldorf1.level3.net (4.69.143.198)  226.131 ms
11  ae-24-24.ebr1.dusseldorf1.level3.net (4.69.143.193)  208.794 ms  208.870 ms  210.321 ms
12  ae-47-47.ebr3.frankfurt1.level3.net (4.69.143.174)  233.250 ms
    ae-46-46.ebr3.frankfurt1.level3.net (4.69.143.170)  213.146 ms
    ae-47-47.ebr3.frankfurt1.level3.net (4.69.143.174)  227.040 ms
13  ae-73-73.csw2.frankfurt1.level3.net (4.69.163.6)  208.120 ms
    ae-63-63.csw1.frankfurt1.level3.net (4.69.163.2)  211.151 ms
    ae-93-93.csw4.frankfurt1.level3.net (4.69.163.14)  211.423 ms
14  ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  213.680 ms
    ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  214.437 ms
    ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  214.765 ms
15  195.16.161.58 (195.16.161.58)  379.129 ms  376.786 ms  375.830 ms
16  206-127-157-86.plaync.com (206.127.157.86)  359.993 ms  358.730 ms  359.458 ms
17  206-127-157-102.plaync.com (206.127.157.102)  355.490 ms  359.499 ms  354.900 ms
18  206-127-157-102.plaync.com (206.127.157.102)  407.578 ms !X * *
19  206-127-157-102.plaync.com (206.127.157.102)  355.411 ms !X * *
20  206-127-157-102.plaync.com (206.127.157.102)  353.940 ms !X * *
21  206-127-157-102.plaync.com (206.127.157.102)  354.840 ms !X
 
MagicDude4Eva said:
Pretty much varies - like this morning:
PHP: 
traceroute to 206.127.159.241 (206.127.159.241), 64 hops max, 52 byte packets
 1  netgear.muffin.lan (172.16.0.1)  2.531 ms  1.570 ms  1.884 ms
 2  105-236-6-129-esr-lo.mtnbusiness.co.za (105.236.6.129)  11.785 ms  10.242 ms  14.579 ms
 3  ipc-recieve-jh-2a.za.mtnbusiness.net (41.181.178.17)  14.054 ms  17.502 ms  17.149 ms
 4  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  15.599 ms  18.634 ms  13.917 ms
 5  jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114)  17.558 ms  12.863 ms  12.803 ms
 6  am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141)  204.142 ms  203.099 ms  207.164 ms
 7  xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89)  205.682 ms  239.775 ms  206.511 ms
 8  4.69.162.133 (4.69.162.133)  212.757 ms
    4.69.162.137 (4.69.162.137)  228.794 ms
    4.69.162.129 (4.69.162.129)  213.269 ms
 9  ae-59-114.ebr1.amsterdam1.level3.net (4.69.153.197)  228.377 ms
    ae-56-111.ebr1.amsterdam1.level3.net (4.69.153.185)  228.601 ms
    ae-59-114.ebr1.amsterdam1.level3.net (4.69.153.197)  229.621 ms
10  ae-47-47.ebr2.dusseldorf1.level3.net (4.69.143.206)  219.571 ms  212.064 ms
    ae-45-45.ebr2.dusseldorf1.level3.net (4.69.143.198)  226.131 ms
11  ae-24-24.ebr1.dusseldorf1.level3.net (4.69.143.193)  208.794 ms  208.870 ms  210.321 ms
12  ae-47-47.ebr3.frankfurt1.level3.net (4.69.143.174)  233.250 ms
    ae-46-46.ebr3.frankfurt1.level3.net (4.69.143.170)  213.146 ms
    ae-47-47.ebr3.frankfurt1.level3.net (4.69.143.174)  227.040 ms
13  ae-73-73.csw2.frankfurt1.level3.net (4.69.163.6)  208.120 ms
    ae-63-63.csw1.frankfurt1.level3.net (4.69.163.2)  211.151 ms
    ae-93-93.csw4.frankfurt1.level3.net (4.69.163.14)  211.423 ms
14  ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  213.680 ms
    ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  214.437 ms
    ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  214.765 ms
15  195.16.161.58 (195.16.161.58)  379.129 ms  376.786 ms  375.830 ms
16  206-127-157-86.plaync.com (206.127.157.86)  359.993 ms  358.730 ms  359.458 ms
17  206-127-157-102.plaync.com (206.127.157.102)  355.490 ms  359.499 ms  354.900 ms
18  206-127-157-102.plaync.com (206.127.157.102)  407.578 ms !X * *
19  206-127-157-102.plaync.com (206.127.157.102)  355.411 ms !X * *
20  206-127-157-102.plaync.com (206.127.157.102)  353.940 ms !X * *
21  206-127-157-102.plaync.com (206.127.157.102)  354.840 ms !X
Click to expand...

Seems to point to more of an exchange issue :( Chances are the latency will jump again this afternoon when everyone comes home from work :(
If your line is with us we can log a fault for you.
 



This has been going on for a while now -

Considering cancelling at the price I am paying 10mb business uncapped.
 
requiem said:



This has been going on for a while now -

Considering cancelling at the price I am paying 10mb business uncapped.
Click to expand...

Remember that our network is currently seeing higher load than normal which may have an affect on the account. Our Engineers are running through various steps to return everything to normal.
Let's run some troubleshooting once things have been sorted out 100% on our end and we can take it from there.

Sorry about this :(
 
AfriGuy said:
Seems to point to more of an exchange issue :( Chances are the latency will jump again this afternoon when everyone comes home from work :(
If your line is with us we can log a fault for you.
Click to expand...

Need some help then - line is with Telkom. Can you get your support team to respond to my ticket LPG-306-41392 with details on how I should log the call with Telkom (i.e. resetting port or anything else?)
 
MagicDude4Eva said:
Need some help then - line is with Telkom. Can you get your support team to respond to my ticket LPG-306-41392 with details on how I should log the call with Telkom (i.e. resetting port or anything else?)
Click to expand...

Not that easy, exchange congestion is a biache - can take telkom a week to months and some people even years before they add more capacity to the exchange backhaul - read the forums lots of people sit with this problem

Best is to PM TelkomZA with traces and if you can get yours neighbors to do the same having then more evidence that there is a problem the better
 
MagicDude4Eva said:
Need some help then - line is with Telkom. Can you get your support team to respond to my ticket LPG-306-41392 with details on how I should log the call with Telkom (i.e. resetting port or anything else?)
Click to expand...

It's quite straight forward to log a fault with Telkom, you can do it online [https://secureapp.telkom.co.za/assurance/public/logafault] or by calling 10210 :)
A port reset from Telkoms end may temporarily sort the issue out - but having a fault logged is the better long term solution :)
 
nerf said:
Not that easy, exchange congestion is a biache - can take telkom a week to months and some people even years before they add more capacity to the exchange backhaul - read the forums lots of people sit with this problem
Click to expand...

Now that is puzzling - when I spoke to Telkom 4 weeks ago about plans of the exchange moving to 10mbps, they said, that they have hardly any customers on it (it's 011 467 0###) and there are no immediate plans to upgrade. So this somehow contradicts (i.e. if no customers are on it, how can it be congested?).
 
MagicDude4Eva said:
Now that is puzzling - when I spoke to Telkom 4 weeks ago about plans of the exchange moving to 10mbps, they said, that they have hardly any customers on it (it's 011 467 0###) and there are no immediate plans to upgrade. So this somehow contradicts (i.e. if no customers are on it, how can it be congested?).
Click to expand...

Basically - the people in the Telkom call center often don't seem to have a clue. I have been told a different story about my exchange every time i have called. Yes it is going to be upgraded, then no it is not, etc etc. The only reliable information i have had is from PM'ing TelkomZA, they seem to be able to get better info. BTW i have some clients on 011 467 and they are also suffering similar problems - looks like congestion to me.
 
MagicDude4Eva said:
Now that is puzzling - when I spoke to Telkom 4 weeks ago about plans of the exchange moving to 10mbps, they said, that they have hardly any customers on it (it's 011 467 0###) and there are no immediate plans to upgrade. So this somehow contradicts (i.e. if no customers are on it, how can it be congested?).
Click to expand...

It could also be an over-utilisation of the DSLAM itself. If it can only handle 10 users but there are currently 15 users connected it'll also cause issues :(
 
ramar said:
Basically - the people in the Telkom call center often don't seem to have a clue. I have been told a different story about my exchange every time i have called. Yes it is going to be upgraded, then no it is not, etc etc. The only reliable information i have had is from PM'ing TelkomZA, they seem to be able to get better info. BTW i have some clients on 011 467 and they are also suffering similar problems - looks like congestion to me.
Click to expand...

Changes in Telkom's internal systems cause mass confusion. When they upgraded lines last year, there was a lot of confusion because they updated their product descriptions before they upgraded the products themselves. So people on 384kbps line were showing as 1Mbps clients on the ADSL checker and new clients signing up were getting very different information in terms of what they could actually get. We had the same issues with VDSL earlier this year.

I can only imagine that the promised free upgrades later this year are going to cause similar mass confusion internally at Telkom and amongst wholesalers. Hopefully we'll be able to decrypt the mess on our side for our clients :)
 
Last edited:
Hummercellc said:
Afriman,

Me again, Static IP's on Capped DSL Accounts, When??? :D
Click to expand...

Static IPs are quite a niche add-on and more aimed at Business. Since they're still fairly new we can't say at this stage, but no concrete plans to allocate Static IPs to Home Uncapped/ Capped products :(
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X