Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
1 192.168.1.1 (192.168.1.1) 1.800 ms 0.762 ms 0.764 ms
2 105-236-5-193-esr-lo.mtnbusiness.co.za (105.236.5.193) 305.069 ms 59.995 ms 108.463 ms
These are extremely high pings. Please assist. Thanks

That points to exchange congestion.
 
Wondering as well... I'm on the old price, and getting the old bundle as is, but wasn't told what was going to happen with what, other than Afriman saying that "news is coming soon".

Everything will be confirmed soon :)
 
Also a latency problem. Have sent more than 1 mail with the below to client zone and nothing.

50 pings to the local dota 2 server (CT i think)


PING 197.80.200.1 (197.80.200.1): 56 data bytes

64 bytes from 197.80.200.1: icmp_seq=0 ttl=242 time=979.987 ms
64 bytes from 197.80.200.1: icmp_seq=1 ttl=242 time=498.596 ms
64 bytes from 197.80.200.1: icmp_seq=2 ttl=242 time=578.977 ms
64 bytes from 197.80.200.1: icmp_seq=3 ttl=242 time=566.517 ms
64 bytes from 197.80.200.1: icmp_seq=4 ttl=242 time=497.113 ms
64 bytes from 197.80.200.1: icmp_seq=5 ttl=242 time=562.521 ms
64 bytes from 197.80.200.1: icmp_seq=6 ttl=242 time=759.333 ms
64 bytes from 197.80.200.1: icmp_seq=7 ttl=242 time=627.036 ms
64 bytes from 197.80.200.1: icmp_seq=8 ttl=242 time=827.275 ms
64 bytes from 197.80.200.1: icmp_seq=9 ttl=242 time=623.683 ms
64 bytes from 197.80.200.1: icmp_seq=10 ttl=242 time=826.188 ms
64 bytes from 197.80.200.1: icmp_seq=11 ttl=242 time=693.572 ms
64 bytes from 197.80.200.1: icmp_seq=12 ttl=242 time=492.262 ms
64 bytes from 197.80.200.1: icmp_seq=13 ttl=242 time=753.796 ms
64 bytes from 197.80.200.1: icmp_seq=14 ttl=242 time=565.803 ms
64 bytes from 197.80.200.1: icmp_seq=15 ttl=242 time=817.212 ms
64 bytes from 197.80.200.1: icmp_seq=16 ttl=242 time=557.643 ms
64 bytes from 197.80.200.1: icmp_seq=17 ttl=242 time=249.297 ms
64 bytes from 197.80.200.1: icmp_seq=18 ttl=242 time=304.940 ms
64 bytes from 197.80.200.1: icmp_seq=19 ttl=242 time=318.788 ms
64 bytes from 197.80.200.1: icmp_seq=20 ttl=242 time=572.181 ms
64 bytes from 197.80.200.1: icmp_seq=21 ttl=242 time=412.680 ms
64 bytes from 197.80.200.1: icmp_seq=22 ttl=242 time=811.022 ms
64 bytes from 197.80.200.1: icmp_seq=23 ttl=242 time=772.181 ms
64 bytes from 197.80.200.1: icmp_seq=24 ttl=242 time=87.492 ms
64 bytes from 197.80.200.1: icmp_seq=25 ttl=242 time=946.947 ms
64 bytes from 197.80.200.1: icmp_seq=26 ttl=242 time=805.083 ms
64 bytes from 197.80.200.1: icmp_seq=27 ttl=242 time=277.307 ms
64 bytes from 197.80.200.1: icmp_seq=28 ttl=242 time=540.628 ms
64 bytes from 197.80.200.1: icmp_seq=29 ttl=242 time=613.245 ms
64 bytes from 197.80.200.1: icmp_seq=30 ttl=242 time=115.577 ms
64 bytes from 197.80.200.1: icmp_seq=31 ttl=242 time=344.174 ms
64 bytes from 197.80.200.1: icmp_seq=32 ttl=242 time=666.492 ms
64 bytes from 197.80.200.1: icmp_seq=33 ttl=242 time=209.493 ms
64 bytes from 197.80.200.1: icmp_seq=34 ttl=242 time=734.095 ms
64 bytes from 197.80.200.1: icmp_seq=35 ttl=242 time=931.122 ms
64 bytes from 197.80.200.1: icmp_seq=36 ttl=242 time=305.593 ms
64 bytes from 197.80.200.1: icmp_seq=37 ttl=242 time=928.339 ms
64 bytes from 197.80.200.1: icmp_seq=38 ttl=242 time=930.148 ms
64 bytes from 197.80.200.1: icmp_seq=39 ttl=242 time=301.928 ms
64 bytes from 197.80.200.1: icmp_seq=40 ttl=242 time=119.084 ms
64 bytes from 197.80.200.1: icmp_seq=41 ttl=242 time=658.365 ms
64 bytes from 197.80.200.1: icmp_seq=42 ttl=242 time=793.947 ms
64 bytes from 197.80.200.1: icmp_seq=43 ttl=242 time=661.713 ms
64 bytes from 197.80.200.1: icmp_seq=44 ttl=242 time=727.901 ms
64 bytes from 197.80.200.1: icmp_seq=45 ttl=242 time=723.105 ms
64 bytes from 197.80.200.1: icmp_seq=46 ttl=242 time=486.716 ms
64 bytes from 197.80.200.1: icmp_seq=47 ttl=242 time=987.549 ms
64 bytes from 197.80.200.1: icmp_seq=48 ttl=242 time=855.567 ms
64 bytes from 197.80.200.1: icmp_seq=49 ttl=242 time=716.692 ms
64 bytes from 197.80.200.1: icmp_seq=50 ttl=242 time=202.453 ms




traceroute to dota 2 server




traceroute to 197.80.200.1 (197.80.200.1), 64 hops max, 52 byte packets

1 192.168.1.1 (192.168.1.1) 1.800 ms 0.762 ms 0.764 ms
2 105-236-5-193-esr-lo.mtnbusiness.co.za (105.236.5.193) 305.069 ms 59.995 ms 108.463 ms
3 ipc-recieve-tb-2a.mtnbusiness.net (41.181.54.86) 119.176 ms 119.520 ms 177.638 ms
4 tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 109.165 ms 110.222 ms 148.421 ms
5 * unc-cpt-1.mtnns.net (196.44.18.8) 100.482 ms 119.793 ms
6 196.44.31.106 (196.44.31.106) 85.375 ms 80.341 ms 86.895 ms
7 nl-ha-2.za--rb-cr-1.za-a.mtnns.net (196.44.0.121) 102.419 ms 109.835 ms 196.44.0.74 (196.44.0.74) 113.129 ms
8 196-28-178-141.adsl.mweb.co.za (196.28.178.141) 116.889 ms 103.497 ms 102.546 ms
9 tengig-0-7-0-3-cpt-p-2.mweb.co.za (197.84.7.2) 137.598 ms 149.504 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za (197.84.7.1) 131.385 ms
10 tengig-0-0-0-0-vic-p-2.mweb.co.za (197.84.4.35) 116.779 ms 137.969 ms 140.312 ms
11 tengig-0-0-0-0-102-vic-pe-1.mweb.co.za (197.80.7.41) 129.372 ms 122.097 ms *
12 tengig0-0-0-0.mca-pe-1.mweb.co.za (197.80.4.37) 129.671 ms 137.401 ms 138.611 ms
13 197-80-96-30.jhb.mweb.co.za (197.80.96.30) 132.835 ms 143.760 ms 125.172 ms
14 opti-jhb-vp-hosting.optinet.net (197.80.206.6) 124.502 ms 120.025 ms 115.814 ms
15 197-80-215-18.jhb.mweb.co.za (197.80.215.18) 110.617 ms * 432.555 ms


I have sent in-game screen shots to client zone.

These are extremely high pings. Please assist. Thanks

Welcome to MyBB!
Looks like there is some exchange congestion here :(
 
/fetches dictionary.
/tatoos definition on Afriguy :p

Righty-ho, will wait :)

The new bundles should be live already. Drop me a PM, and I'll check if you were one of those bundles which were already getting lower than R1,80 per GB and haven't changed.
 
Canceled my openweb to go with afrihost 100 + 100GB at the end of the month.. but this is looking worrisome!
 
So i'm screwed??

I won't lie, congestion is one of the toughest issues to deal with. We don't have an escalation process with Telkom on congestion and also Telkom's standard reply is 6 weeks to 12 months for exchanges to be upgraded.

I really hope that Telkom's planned upgrades get rolled out quickly cos we're seeing more and more clients in this position :(
 
The new bundles should be live already. Drop me a PM, and I'll check if you were one of those bundles which were already getting lower than R1,80 per GB and haven't changed.

I think you and Afriguy needs to compair notes. He said we need to wait for Gian to mail us about the bundels.
Very confusing as this was never mentioned that there will be some people not getting any exstra data.
 
My bundle didn't change but Afriman explained it very well.

I pay Rxxx for a 40mb line and 100Gb data. Take away Telkom's R795 and I am paying Rxx for 100Gb data. Even taking out any discounts between Telkom and Afrihost, I am already on a very good deal of less than R1 per Gb, so still happy.
 
My bundle didn't change but Afriman explained it very well.

I pay Rxxx for a 40mb line and 100Gb data. Take away Telkom's R795 and I am paying Rxx for 100Gb data. Even taking out any discounts between Telkom and Afrihost, I am already on a very good deal of less than R1 per Gb, so still happy.

This I understand, but what about people with less than 100GB cap that needs a bit more. Now suddenly their ADSL budget almost doubles!
 
These Authentication issues from the last couple of weeks.

I definitely understand how frustrating these issues have been. I sat at home without internet for the same times, and it was horrible. Though being without power at my house for the last 3 days has put things in perspective a little. It sucks to be me :(

We're still investigating so I can't say definitively that these authentication problems are behind us. We're working with MTN senior management and we've also put together a lot of information to try to highlight where we think the issue could be. It also makes it hard that we can't recreate the issue, but we know the symptoms, so we mostly have to wait for it to happen again so we can try to get more data.

I promise that we're working on this as high priority. All our directors are weighing in with MTN management, and we've got their full co-operation to try and find a permanent solution for this.
 
I think you and Afriguy needs to compair notes. He said we need to wait for Gian to mail us about the bundels.
Very confusing as this was never mentioned that there will be some people not getting any exstra data.

I think AfriGuy was waiting for Gian's mail to go out, but it looks like there are some delays there. The explanation I posted yesterday should pretty much cover everything.
 
This I understand, but what about people with less than 100GB cap that needs a bit more. Now suddenly their ADSL budget almost doubles!

Nobody is receiving less data or paying more than they were previously (or they shouldn't - if you are please PM me).

If your per GB rate is the same or lower than R1,80 - you stay on exactly what you already had previously.
 
I think, FOR NOW, its safe to say its sorted...

Haven't had any issues yet...

I really hope so, but we're watching the network 24 hours a day. We've also set up more sensitive monitoring systems to alert us as soon as we see there might be the slightest chance of an issue.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X