Afrihost Business Uncapped Feedback

Status
Not open for further replies.
AfriGuy said:
I've just gone through your PM and will be checking things out for you tonight. This definitely isn't the norm with our Business accounts.
Click to expand...

Hi Afriguy, please do, as i just checked with my FNB account that i have and international is full LINE speed. getting 6.4mbps... and i disconnected and reconnected again on afrihost on the same server get 1.5mbps...
 
When I put the fault reference number I received from Critical Care into Telkom's fault tracker system it says:

The Fault Reference number entered does not exist.

How do I track that something is being done, given that 2 Telkom technicians have been to my house and failed to fix the problem. This is probably because the fault is at the exchange and/or beyond. My line and connection to the exchange are in good order I am told.

20% packet loss is a rather glaring fault.

At present I am paying R900pm for a product that is only useful for browsing (as long as the website isn't too complex)

How do I get assurance that the fault has been identified by Telkom and actions are being taken to fix it?

EDIT: I found my fault reference by trying to report my number. It just say "Open". Great tracker.
 
Last edited:
Gatecrasher said:
When I put the fault reference number I received from Critical Care into Telkom's fault tracker system it says:

The Fault Reference number entered does not exist.

How do I track that something is being done, given that 2 Telkom technicians have been to my house and failed to fix the problem. This is probably because the fault is at the exchange and/or beyond. My line and connection to the exchange are in good order I am told.

20% packet loss is a rather glaring fault.

At present I am paying R900pm for a product that is only useful for browsing (as long as the website isn't too complex)

How do I get assurance that the fault has been identified by Telkom and actions are being taken to fix it?

EDIT: I found my fault reference by trying to report my number. It just say "Open". Great tracker.
Click to expand...

We're not 100% sure how Telkom differentiates faults on their systems, but we know that we can't see voice line faults logged, and we also can't edit faults logged directly with Telkom with updates or feedback.

Please keep Critical Care up to date with any progress you receive, and we'll also check in with you with whatever feedback we get on our side :(
 
Thanks for the feedback guys. My current ISP says they restrict certain http websites because there's not enough bandwidth in the pool so when downloading from there I don't get my full speed, only after midnight till 6am do they remove restrictions (which is when I get my full speed - on those specific websites).
 
Supreme Element said:
anyone else getting disconnected every hour on the new hour? seems to be happening to me every hour since yesterday that I noticed.
Click to expand...

@AfriMan,

I have been experiencing the same problem as Supreme Element, I have had to restart my router several times today, apart from this issue been loving Afrihost thus far...Any feedback with regards to the issue above AfriMan?
 
JesseG said:
@AfriMan,

I have been experiencing the same problem as Supreme Element, I have had to restart my router several times today, apart from this issue been loving Afrihost thus far...Any feedback with regards to the issue above AfriMan?
Click to expand...

Same here. It's not as frequent as every hour, but for a few days now I've been rebooting my router a ridiculous number of times.
 
I'm getting latency of 240ms to World of Warcraft servers in Europe. Is this normal? I was getting 170-190ms on IS.

This is the traceroute to the server in question.
Code: 
Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.10.250
  2    10 ms    10 ms    10 ms  105-236-6-193-esr-lo.mtnbusiness.co.za [105.236.6.193]
  3    16 ms    15 ms    16 ms  ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
  4    17 ms    16 ms    37 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    17 ms    17 ms    17 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6    17 ms    16 ms    16 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7   230 ms   230 ms   231 ms  ct-cr-2.za--ct-cr-1.za.mtnns.net [196.44.31.35]
  8   243 ms   230 ms   230 ms  ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
  9   228 ms   206 ms   206 ms  ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
 10   206 ms   206 ms   206 ms  195.50.122.181
 11   223 ms   222 ms   222 ms  4.69.166.6
 12   206 ms   206 ms   207 ms  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
 13   221 ms   221 ms   221 ms  ldn-b5-link.telia.net [213.248.96.37]
 14   264 ms   207 ms   206 ms  ldn-bb1-link.telia.net [213.155.136.74]
 15   234 ms   231 ms   230 ms  prs-bb1-link.telia.net [213.155.134.34]
 16   238 ms   238 ms   238 ms  ffm-bb1-link.telia.net [80.91.245.102]
 17   240 ms   240 ms   247 ms  ffm-b10-link.telia.net [213.155.134.135]
 18     *        *        *     Request timed out.
 19  ^C

I saw a post from a while ago where someone does a traceroute to London on the MTN Business network and gets very low latency of ~145ms:
Tinuva said:
Ambo, I've seen altencies of ~145ms from Cape Town to London using WACS, and ~150ms using SAT3 if it is between 2 datacentres.

With ADSL one has to add a bit more, so can expect ~160ms via SAT3 and I would guess ~155ms via WACS.


MTN-Business CT to London:
Code: 
lg2.cpt1.za#trace ares.hero.za.net

Type escape sequence to abort.
Tracing the route to ares.hero.za.net (85.119.82.167)

  1 vlan810.hr3.cpt1.za.mtnbusiness.net (196.7.3.121) 0 msec 0 msec 0 msec
  2 ge8-0-0.gw1.cpt1.za.mtnbusiness.net (196.30.176.33) 0 msec 4 msec 0 msec
  3 196.7.21.14 0 msec 0 msec 4 msec
  4 tb-cr-1.za--tb-cr-2.za-a.mtn.net (196.44.31.158) 0 msec 0 msec 0 msec
  5 tb-cr-2.za--tb-cr-1.za-a.mtnns.net (196.44.31.5) 4 msec 4 msec 0 msec
  6 ls-cr-1.uk--tb-cr-2.za.mtnns.net (196.44.31.241) 156 msec 144 msec 172 msec
  7 ls-pr-2.uk--ls-cr-1.uk-a.mtn.net (209.212.111.203) 148 msec 148 msec 212 msec
  8 339.xe-7-0-1.mpr1.lhr1.uk.above.net (213.152.230.89) 144 msec 144 msec 148 msec
  9 linx-gw-a.jump.net.uk (195.66.224.34) 144 msec 144 msec 144 msec
 10 bellini.bitfolk.com (85.119.80.17) 160 msec 156 msec 160 msec
 11 ares.hero.za.net (85.119.82.167) 144 msec 144 msec 148 msec

Not a solid traceroute, but it shows some of the lowest latencies I have seen from CT to London.
Click to expand...

Am I unlikely to see this sort of latency? Will the latency ever drop to below 200ms?
 
efitol said:
I'm getting latency of 240ms to World of Warcraft servers in Europe. Is this normal? I was getting 170-190ms on IS.

This is the traceroute to the server in question.
Code: 
Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.10.250
  2    10 ms    10 ms    10 ms  105-236-6-193-esr-lo.mtnbusiness.co.za [105.236.6.193]
  3    16 ms    15 ms    16 ms  ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
  4    17 ms    16 ms    37 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    17 ms    17 ms    17 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6    17 ms    16 ms    16 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7   230 ms   230 ms   231 ms  ct-cr-2.za--ct-cr-1.za.mtnns.net [196.44.31.35]
  8   243 ms   230 ms   230 ms  ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
  9   228 ms   206 ms   206 ms  ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
 10   206 ms   206 ms   206 ms  195.50.122.181
 11   223 ms   222 ms   222 ms  4.69.166.6
 12   206 ms   206 ms   207 ms  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
 13   221 ms   221 ms   221 ms  ldn-b5-link.telia.net [213.248.96.37]
 14   264 ms   207 ms   206 ms  ldn-bb1-link.telia.net [213.155.136.74]
 15   234 ms   231 ms   230 ms  prs-bb1-link.telia.net [213.155.134.34]
 16   238 ms   238 ms   238 ms  ffm-bb1-link.telia.net [80.91.245.102]
 17   240 ms   240 ms   247 ms  ffm-b10-link.telia.net [213.155.134.135]
 18     *        *        *     Request timed out.
 19  ^C

I saw a post from a while ago where someone does a traceroute to London on the MTN Business network and gets very low latency of ~145ms:


Am I unlikely to see this sort of latency? Will the latency ever drop to below 200ms?
Click to expand...

Afriman/Afriguy, any comment on this?
 
efitol said:
Afriman/Afriguy, any comment on this?
Click to expand...

Cape Town routing looks OK, you are in Gautengeleng it seems, wild guess different routing.

Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 4 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 6 ms 5 ms 5 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 7 ms 6 ms 6 ms 41.181.184.28
5 7 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 7 ms 6 ms 6 ms 196.44.31.106
7 150 ms 170 ms 149 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 150 ms 167 ms 150 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
9 151 ms 149 ms 150 ms 195.50.122.181
10 173 ms 173 ms 173 ms 4.69.166.30
11 * * * Request timed out.
12 150 ms 149 ms 150 ms ldn-b5-link.telia.net [213.248.92.81]
13 151 ms 216 ms 150 ms ldn-bb1-link.telia.net [213.155.132.194]
14 158 ms 157 ms 219 ms prs-bb1-link.telia.net [213.155.134.34]
15 167 ms 166 ms 190 ms ffm-bb1-link.telia.net [80.91.245.102]
16 166 ms 190 ms 165 ms ffm-b10-link.telia.net [80.91.251.248]
17 * * * Request timed out.
 
jannier said:
Cape Town routing looks OK, you are in Gautengeleng it seems, wild guess different routing.

Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 4 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 6 ms 5 ms 5 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 7 ms 6 ms 6 ms 41.181.184.28
5 7 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 7 ms 6 ms 6 ms 196.44.31.106
7 150 ms 170 ms 149 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 150 ms 167 ms 150 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
9 151 ms 149 ms 150 ms 195.50.122.181
10 173 ms 173 ms 173 ms 4.69.166.30
11 * * * Request timed out.
12 150 ms 149 ms 150 ms ldn-b5-link.telia.net [213.248.92.81]
13 151 ms 216 ms 150 ms ldn-bb1-link.telia.net [213.155.132.194]
14 158 ms 157 ms 219 ms prs-bb1-link.telia.net [213.155.134.34]
15 167 ms 166 ms 190 ms ffm-bb1-link.telia.net [80.91.245.102]
16 166 ms 190 ms 165 ms ffm-b10-link.telia.net [80.91.251.248]
17 * * * Request timed out.
Click to expand...

Wow, that is quite a huge improvement over mine... I'm in Polokwane, Limpopo. Would that explain a 80ms increase in latency though?
 
AfriMan said:
Please keep Critical Care up to date with any progress you receive, and we'll also check in with you with whatever feedback we get on our side :(
Click to expand...

I have kept Critical Care up to date, but there is no further feedback and absolutely no progress.
 
Just an update:

Packet Loss to 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
Code: 
>ping 105.236.8.129 -l 4096 -n 100

Pinging 105.236.8.129 with 4096 bytes of data:
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=77ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=106ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=94ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=233ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=409ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=896ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=733ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1100ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=792ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=82ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=216ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=87ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=107ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=93ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=81ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=106ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=84ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=303ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=599ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=890ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=108ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=253ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=180ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=77ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=107ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=93ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=77ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=88ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=175ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=312ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=681ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=991ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=82ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=538ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=730ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=93ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=298ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=155ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=82ms TTL=254
Request timed out.
Code: 
Ping statistics for 105.236.8.129:
    Packets: Sent = 100, Received = 84, Lost = 16 (16% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 1100ms, Average = 183ms

Speed Test:


4MB Uncapped Buisness
Line Synch: 10Mb/s
 
Last edited:
Gatecrasher said:
I have kept Critical Care up to date, but there is no further feedback and absolutely no progress.
Click to expand...

I am in the same boat as you. Two weeks later.....

Test conducted on 01 July 2013 06:42:40 PM

Download Speed: 183 kbps (22.9 KB/sec transfer rate)

Upload Speed: 418 kbps (52.3 KB/sec transfer rate)

Latency: 48 ms
 
Just signed up for a 1mb business uncapped and have to say it was flying compared to mweb .... constant 130KB, while with mweb it maxed out at 110KB and usually fluctuated from 30KB up to 110KB.
I only hope that it will be maintained, and will deteriorate over time.
For now though, I thought I would give Afrihost props for a very good account that performs as they say... unshaped :)
 
Last night I downloaded a NZB file and it came down at a steady 850Kb/s. A 5gb file took about 2hrs (maybe longer, maybe shorter)
 
lucifir said:
Just signed up for a 1mb business uncapped and have to say it was flying compared to mweb .... constant 130KB, while with mweb it maxed out at 110KB and usually fluctuated from 30KB up to 110KB.
I only hope that it will be maintained, and will deteriorate over time.
For now though, I thought I would give Afrihost props for a very good account that performs as they say... unshaped :)
Click to expand...

I'm also happy with my 1Mbps business uncapped and its better than the home offering. My issues are more speed so will go back to 2Mbps (was trying to save money by downgrading)
 
efitol said:
Wow, that is quite a huge improvement over mine... I'm in Polokwane, Limpopo. Would that explain a 80ms increase in latency though?
Click to expand...

Yes you will take a different route then us, I don't know how it is done, I think they route where the capacity is available, either on WACS or EASSY.
Between Cape Town and Johannesburg the latency is an extra 30 odd miliseconds.
 
Gatecrasher said:
I have kept Critical Care up to date, but there is no further feedback and absolutely no progress.
Click to expand...

Was advised by Telkom that all should be well now. But it is not. It is exactly the same. (Perhaps slightly worse.)
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X