- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
Unfortunately notBut they will escalate it to the next tier of support and they will do it
Ah, still seems like it may be a quicker option than phoning in!
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your stance on AI?
Afrihost Business Uncapped Feedback - 2
- Thread starter The_Unbeliever
- Start date
- Status
Ah, still seems like it may be a quicker option than phoning in!
ghostR
Executive Member
- Joined
- Feb 11, 2015
- Messages
- 6,142
- Reaction score
- 39
Definitely!
Dianysis
Expert Member
- Joined
- Oct 30, 2014
- Messages
- 2,048
- Reaction score
- 87
No worries! Seems there are widely differing opinions on the matter.
While I am rocking the boat - any further news from Telkom regarding the fault at my exchange?
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
Just got an update, Telkom isn't able to provide us with an ETA yet, looks like they are going to need to replace an entire card on the DSLAM.
Dianysis
Expert Member
- Joined
- Oct 30, 2014
- Messages
- 2,048
- Reaction score
- 87
Just got an update, Telkom isn't able to provide us with an ETA yet, looks like they are going to need to replace an entire card on the DSLAM.
That means that since December 2014 (when the faulty card was first discovered by the technician) diddley-skwat has been done.
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
That means that since December 2014 (when the faulty card was first discovered by the technician) diddley-skwat has been done.
Wow... That would be horrible... The fault report indicates that the faulty card was discovered in March... Even that is bad enough. But December...
Hummercellc
Expert Member
Afrihost when will the freaking fault be fixed? 7 months of erratic latency.... I don't care who's fault it is, just fix it! It is only affecting MTN DSL accounts all other ISPS are fine....
Azure Wrath
Active Member
- Joined
- Oct 26, 2011
- Messages
- 51
- Reaction score
- 0
Having high ping on LoL again :/
C:\Users\Desktop>tracert riot.de
Tracing route to riot.de [188.40.93.11]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 119 ms 124 ms 129 ms 41.181.54.85
4 114 ms 109 ms 113 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
5 139 ms 144 ms 144 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
6 130 ms 127 ms 122 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 316 ms 276 ms 273 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
8 235 ms 260 ms 242 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
9 219 ms 221 ms 228 ms linx-1.init7.net [195.66.224.175]
10 326 ms 331 ms 320 ms r1muc1.core.init7.net [77.109.128.229]
11 332 ms 328 ms 325 ms r1nue2.core.init7.net [77.109.128.230]
12 314 ms 318 ms 326 ms gw-hetzner-nue2.init7.net [82.197.163.30]
13 321 ms 316 ms 320 ms core11.hetzner.de [213.239.203.137]
14 327 ms 324 ms 326 ms core22.hetzner.de [213.239.245.226]
15 353 ms 344 ms 352 ms juniper2.rz10.hetzner.de [213.239.245.46]
16 359 ms 358 ms 361 ms hos-tr4.ex3k7.rz10.hetzner.de [213.239.227.232]
17 340 ms 345 ms 349 ms static.11.93.40.188.clients.your-server.de [188.
40.93.11]
Trace complete.
C:\Users\Desktop>tracert riot.de
Tracing route to riot.de [188.40.93.11]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 119 ms 124 ms 129 ms 41.181.54.85
4 114 ms 109 ms 113 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
5 139 ms 144 ms 144 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
6 130 ms 127 ms 122 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 316 ms 276 ms 273 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
8 235 ms 260 ms 242 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
9 219 ms 221 ms 228 ms linx-1.init7.net [195.66.224.175]
10 326 ms 331 ms 320 ms r1muc1.core.init7.net [77.109.128.229]
11 332 ms 328 ms 325 ms r1nue2.core.init7.net [77.109.128.230]
12 314 ms 318 ms 326 ms gw-hetzner-nue2.init7.net [82.197.163.30]
13 321 ms 316 ms 320 ms core11.hetzner.de [213.239.203.137]
14 327 ms 324 ms 326 ms core22.hetzner.de [213.239.245.226]
15 353 ms 344 ms 352 ms juniper2.rz10.hetzner.de [213.239.245.46]
16 359 ms 358 ms 361 ms hos-tr4.ex3k7.rz10.hetzner.de [213.239.227.232]
17 340 ms 345 ms 349 ms static.11.93.40.188.clients.your-server.de [188.
40.93.11]
Trace complete.
ghostR
Executive Member
- Joined
- Feb 11, 2015
- Messages
- 6,142
- Reaction score
- 39
Can you run a tracert to 155.239.255.250 and post it here
Azure Wrath
Active Member
- Joined
- Oct 26, 2011
- Messages
- 51
- Reaction score
- 0
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Desktop>tracert 155.239.255.250
Tracing route to 155.239.255.250 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.0.2
2 26 ms 26 ms 25 ms 155.239.255.250
Trace complete.
ghostR
Executive Member
- Joined
- Feb 11, 2015
- Messages
- 6,142
- Reaction score
- 39
Can confirm your exchange is not at fault here and the issue is currently lying on afrihost's side.
Azure Wrath
Active Member
- Joined
- Oct 26, 2011
- Messages
- 51
- Reaction score
- 0
I'll use my webafrica trial account when the issue arises again. Pinging riot.de now gives me better results again :/ I hate problems that are difficult to replicate
Looks like your connecting from the South, over peak period, so we definitely did see a rise in latency. We are still working to improve overall performance and client experience during that peak window
I'll use my webafrica trial account when the issue arises again. Pinging riot.de now gives me better results again :/ I hate problems that are difficult to replicate
I'm glad you have an interim solution and we'll definitely keep working on improving this. We have seen some improvement where we've managed to bring down demand, but we're still seeing Uncapped P2P traffic slipping through
Latency should have normalised by then so that's a little unusual. Did you run any tests at the time? My reports show latency in the South normalising around 22:20 so I would expect most users to experience the same close to that time
Interesting. Might be great if you could actually explain what you are testing for here and how everyone can benefit from this?
I'm really sorry that you are still battling with this. Maybe we can bring the MyBB Telkom Rep in on this. We're not getting much joy from our side trying to escalate this so far
Did you send through the last batch of tests for the Critical Care guy working on this?
ghostR
Executive Member
- Joined
- Feb 11, 2015
- Messages
- 6,142
- Reaction score
- 39
Sure, You know on tracerts, When the second hop doesn't respond to ICMP ?
That IP is (to explain it simply) an IP at the new BRAS/BNG's, So a customer wouldn't break out onto the ISP network, Testing the local Telkom Infrastructure only (ie. Exchange Congestion, Packet loss, Line issues etc)
Sure, You know on tracerts, When the second hop doesn't respond to ICMP ?
That IP is (to explain it simply) an IP at the new BRAS/BNG's, So a customer wouldn't break out onto the ISP network, Testing the local Telkom Infrastructure only (ie. Exchange Congestion, Packet loss, Line issues etc)
Do you have a list of those BRAS/BNG IP's? Might be very helpful to our support team to be able to provide client's with this information to be able to troubleshoot better
- Status