Results do look like an exchange congestion here, the 2nd hop (your exchange) generally shouldn't spike over 30ms. You say you see the same latency on the Telkom guest account?
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How often do you receive spam calls?
Afrihost Business Uncapped Feedback
- Thread starter Lino
- Start date
- Status
Results do look like an exchange congestion here, the 2nd hop (your exchange) generally shouldn't spike over 30ms. You say you see the same latency on the Telkom guest account?
isabelladol
Active Member
Yes it's the same on all accounts I've tested. I don't understand, then why did more than one Telkom tech inform me that everything was peachy at the exchange? And the reply I got from TelkomZA "As per our ADSl test tools, we checked the exchange you are attached to - Congella 4 - the utilization graph shows no errors, the Bandwidth Uplink is only operating at 14%, which means this exchange isn't being utilized during office and peak times. more than enough capacity available." Is that also bull****?
Could be a config mis-match somewhere along the line here, congestion can happen on ports due to faulty hardware.
Is your line with us? If so, we'll log a fault for you to have a tech dispatched - Telkom will definitely need to investigate this one.
Hummercellc
Expert Member
I got the same hog wash from the tarts (Telkom), They eventually conceded after many days of communication that our exchange was indeed over subscribed....
Hummercellc
Expert Member
The KZN looks quite busy today, but not sure if it would result in latency results like thisI'll follow up with the team and see what they say.
All back to normal
Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 9 ms 9 ms 9 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
3 16 ms 16 ms 16 ms 41.181.222.42
4 18 ms 18 ms 19 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]
5 22 ms 20 ms 20 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]
6 20 ms 20 ms 21 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
7 23 ms 20 ms 19 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.165.119]
8 21 ms 21 ms 21 ms 196.30.1.39
9 20 ms 20 ms 20 ms 196.31.220.21
10 20 ms 21 ms 21 ms 196.31.63.202
11 21 ms 20 ms 21 ms 196.30.42.133
12 23 ms 20 ms 22 ms cms-gm.afrihost.com [197.242.144.102]
Trace complete.
http://www.speedtest.net/my-result/3438594259
Thanks Afriguy
Last edited:
isabelladol
Active Member
Yes my line is with you, a ticket was supposedly opened on Saturday by AH support, one of the last emails I received from AH support stated:
"I have noticed a few inconsistencies. These indicate an issue on the infrastructure. I also notice that Telkom was previously dispatched, but could not detect any faults. This being said, I have included a detailed description of the issue, and requested them to investigate." Ticket reference: AH20140412-115621.
So clearly there is a mix up somewhere because AH tells me theres a problem with the infrastructure but Telkom says everything is good and well on their side.
Have you passed the results onto our team yet? Telkom will have to dispatch a tech after seeing the results.
All back to normal
Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 9 ms 9 ms 9 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
3 16 ms 16 ms 16 ms 41.181.222.42
4 18 ms 18 ms 19 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]
5 22 ms 20 ms 20 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]
6 20 ms 20 ms 21 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
7 23 ms 20 ms 19 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.165.119]
8 21 ms 21 ms 21 ms 196.30.1.39
9 20 ms 20 ms 20 ms 196.31.220.21
10 20 ms 21 ms 21 ms 196.31.63.202
11 21 ms 20 ms 21 ms 196.30.42.133
12 23 ms 20 ms 22 ms cms-gm.afrihost.com [197.242.144.102]
Trace complete.
Thanks Afriguy
Yeah this matches what our IPC traffic shows - KZN has calmed down a lot. The earlier latency looked to be related to the busyness of the IPC at the time
Hummercellc
Expert Member
Yeah this matches what our IPC traffic shows - KZN has calmed down a lot. The earlier latency looked to be related to the busyness of the IPC at the time
Any plans to add another gigabit or so of capacity?
isabelladol
Active Member
I've sent numerous tests to support, I'm hoping they've passed them onto Telkom. Last thing I want is a repeat of last time, the tech come to my house in the middle of the day and said he could find nothing wrong at the exchange and of course since it was midday I was getting pretty good speeds. So when I tested for him he said it all looked great and closed the ticket. It's really difficult to get through to someone that something is clearly wrong because it's not fixed, and after 12 months of ongoing battle with this problem I still haven't been able to get a real answer about what's going on.
Hummercellc
Expert Member
12 months is a short time for Telkom. It took 26 months for them to change 1 setting on the ME network to correct the congestion here.....
Hummercellc
Expert Member
Last edited:
isabelladol
Active Member
Drop me a PM with your line number, I'll follow up on things for you
Sent, thank you.
TEXTILE GUY
Honorary Master
Yeah this matches what our IPC traffic shows - KZN has calmed down a lot. The earlier latency looked to be related to the busyness of the IPC at the time
Thanks, this would answer the PM I sent, however, not to stir or anything, but a reply (which never happened) would have been the right thing to do.
- Status