Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
AfriGuy said:
I'm confident that they won't fail, we've learnt a lot recently and implementing changes to where we've dropped the ball previously.
Click to expand...

Not sure about that. Unless there's a fundamental flaw with the current network design, there's ZERO reason why AH shouldn't be able to rectify. Clearly though AH hasn't been able to rectify meaning that the current network has passed tipping point and is not recoverable.

Oh - please share this view with Gian. Not sure what happened to him. Haven't checked the other thread today however he was pretty absent recently.
 
steel_dog said:
Down South local is fine. Running at 18.25mbps down.
International is stuffed.
- US East Coast [Towerstream] - 4mbps - http://www.speedtest.net/my-result/4484700102
- UK London [Seacom] - 6.7mbps - http://www.speedtest.net/my-result/4484711705

Any news Afripeeps? Or has everyone given up on this network in favor of the POC ones?
:wtf:

Code: 
Tracing route to seacom.co.uk [109.123.75.100]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  home.gateway.home.gateway [192.168.1.254]
  2    10 ms    10 ms    13 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
  3    13 ms    14 ms    12 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
  4    13 ms     *       18 ms  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
  5    13 ms    11 ms     *     unc-cpt-1.mtnns.net [196.44.18.8]
  6   192 ms   192 ms   199 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
  7   194 ms   193 ms   194 ms  ls-cr-2.uk--jh-cr-1.za.mtnns.net [196.44.31.114]
  8   195 ms   199 ms   195 ms  ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
  9   194 ms     *      194 ms  linx-226.as13213.net [195.66.236.19]
 10   195 ms   213 ms   196 ms  83.170.70.230
 11   193 ms   289 ms   197 ms  dc5.as13213.net [83.170.70.134]
 12     *        *      194 ms  www.seacom.co.uk [109.123.75.100]

Trace complete.
Click to expand...

We're still working on providing the best possible experience for clients on the current network.
 
steel_dog said:
Not sure about that. Unless there's a fundamental flaw with the current network design, there's ZERO reason why AH shouldn't be able to rectify. Clearly though AH hasn't been able to rectify meaning that the current network has passed tipping point and is not recoverable.

Oh - please share this view with Gian. Not sure what happened to him. Haven't checked the other thread today however he was pretty absent recently.
Click to expand...

I'm sure he'll reply to the thread soon, he's massively busy.
 
steel_dog said:
Would be nice to have someone respond directly to my point - paraphrasing - it seems that the current network is not recoverable?
Click to expand...

Current status in a nut shell:

It is broken, the boss is buying a new one, but he can't decide which colour to get..............
 
steel_dog said:
Would be nice to have someone respond directly to my point - paraphrasing - it seems that the current network is not recoverable?
Click to expand...

Not necessarily, we've implemented a bunch of tweaks and will continue to do so.
Long term though, a fix for the high latency and additional demand is to implement one of the two POCs.
 
AfriGuy said:
Not necessarily, we've implemented a bunch of tweaks and will continue to do so.
Long term though, a fix for the high latency and additional demand is to implement one of the two POCs.
Click to expand...
Do any of these fixes involve buying more IPC bandwidth?

I presume you aren't just implementing stricter 'management'?
 
AntiGanda said:
Do any of these fixes involve buying more IPC bandwidth?

I presume you aren't just implementing stricter 'management'?
Click to expand...

I doubt we're looking at buying more capacity as this stage, but I'm personally not aware of the exact details of what's being done.
 
caroper said:
Current status in a nut shell:

It is broken, the boss is buying a new one, but he can't decide which colour to get..............
Click to expand...

Just to confirm....yes it is broken...unusable at the moment cant do business like this!
 
Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.2 -    0 |   70 |   70 |    1 |    1 |   14 |    1 |
|                   No response from host -  100 |   13 |    0 |    0 |    0 |    0 |    0 |
|                          41.181.221.213 -    0 |   69 |   69 |   59 |  126 | 1523 |  161 |
|                          41.181.221.214 -    0 |   70 |   70 |   79 |  103 |  184 |   92 |
|   rb-dca-2.za--qux-b.za.mtnbusiness.net -    0 |   69 |   69 |   57 |   78 |  122 |   64 |
|          rb-dca-2.za--rb-cr-1.mtnns.net -    0 |   70 |   70 |   61 |   82 |  115 |   72 |
|      jh-cr-2.za--rb-cr-1.za-a.mtnns.net -    0 |   69 |   69 |   58 |   90 |  139 |  120 |
|     jh-dca-2.za--jh-cr-2.za-a.mtnns.net -    0 |   69 |   69 |   61 |   84 |  137 |   99 |
|                        cache.google.com -    0 |   69 |   69 |   79 |  106 |  144 |  114 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

It was fine around 5PM. Back to the dumps.
 
Hey Afrihost: f*@@ you.

Bunch of inept thieves.

More packet losses tonight, this is unbearable.

This message was typed with my middle fingers.
 
yes... 50% packet loss to our Arma server.... it did sort of stabilize eventually... but made gaming ***.

Alt tabbed to quickly ping:

Code: 
C:\Users\Mark>PING 197.221.37.99

Pinging 197.221.37.99 with 32 bytes of data:
Reply from 197.221.37.99: bytes=32 time=11ms TTL=115
Request timed out.
Reply from 197.221.37.99: bytes=32 time=10ms TTL=115
Request timed out.

Ping statistics for 197.221.37.99:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 11ms, Average = 10ms

Code: 
C:\Users\Mark>ping 197.221.37.99

Pinging 197.221.37.99 with 32 bytes of data:
Reply from 197.221.37.99: bytes=32 time=11ms TTL=115
Request timed out.
Reply from 197.221.37.99: bytes=32 time=13ms TTL=115
Reply from 197.221.37.99: bytes=32 time=10ms TTL=115

Ping statistics for 197.221.37.99:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 13ms, Average = 11ms
 
Rather Pathetic
so what you guys saying is you not buying more IPC.
you just going to tweak the network, steal a little here to put there and throttle and shape certain protocols so it runs fine.
what a JOKE!!
:mad::mad:
 
dee4dog said:
Just to confirm....yes it is broken...unusable at the moment cant do business like this!
Click to expand...

I don't think it's correct to say the network, MTN's network is actually pretty good when we have the right capacity at our disposal. However, we've just realised that, for our needs, we need to build a network from the ground up that is designed for the kind of experience that we want to deliver.

Once more users are moved over to test the new networks, I would be pretty confident that those who remain on MTN during that period will get the same awesome experience we've seen over the last 3 years when things have been working well.
 
giggity said:
Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.2 -    0 |   70 |   70 |    1 |    1 |   14 |    1 |
|                   No response from host -  100 |   13 |    0 |    0 |    0 |    0 |    0 |
|                          41.181.221.213 -    0 |   69 |   69 |   59 |  126 | 1523 |  161 |
|                          41.181.221.214 -    0 |   70 |   70 |   79 |  103 |  184 |   92 |
|   rb-dca-2.za--qux-b.za.mtnbusiness.net -    0 |   69 |   69 |   57 |   78 |  122 |   64 |
|          rb-dca-2.za--rb-cr-1.mtnns.net -    0 |   70 |   70 |   61 |   82 |  115 |   72 |
|      jh-cr-2.za--rb-cr-1.za-a.mtnns.net -    0 |   69 |   69 |   58 |   90 |  139 |  120 |
|     jh-dca-2.za--jh-cr-2.za-a.mtnns.net -    0 |   69 |   69 |   61 |   84 |  137 |   99 |
|                        cache.google.com -    0 |   69 |   69 |   79 |  106 |  144 |  114 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

It was fine around 5PM. Back to the dumps.
Click to expand...

Latency in the North and South seemed to be decent according to graphs, but the East didn't look so great around midday (which seems to be the peak window for that region). Speeds still seemed to be less than great, from reports from clients, but latency should have been pretty solid :(
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X