Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
AfriMan said:
Is everything else looking normal? What DNS do you use?
Click to expand...
I struggled to get Google Analytics. I am not using a lot of non-google websites, but the ones I have seem OK.
I currently have primary DNS 8.8.8.8 and secondary 196.7.7.7. I use the Google DNS as primary as I often switch to a telkom account and using automatic DNS causes issues.
 
Vorastra said:
Overall I guess Google services were most affected. However, downloading from the Amazon/Google App stores was absolutely fine. The issue is that I mostly used Google services this weekend so to me it was very noticeable.

I did not notice sites loading slower or images on said sites loading slower than usual.

BTW. Service seems to be back to normal as of this morning.

EDIT: As I post this, Google Images/Search is running extremely poorly. Tried on both Chrome and IE. ~300kbit.
Click to expand...

Glad to hear it's back to normal. It seems to be a Google thing or somehow our link to however Google does stuff locally. I couldn't say though, the experts will need to weigh in.
 
twhitehead said:
I struggled to get Google Analytics. I am not using a lot of non-google websites, but the ones I have seem OK.
I currently have primary DNS 8.8.8.8 and secondary 196.7.7.7. I use the Google DNS as primary as I often switch to a telkom account and using automatic DNS causes issues.
Click to expand...

Issue seems to be related to Google. If Facebook is fine, then I don't think it;s an international issue :(
 
Hey Guys

Gian has started a thread to explain exactly what is happening with our network. Here's the link to the thread:

http://mybroadband.co.za/vb/showthr...re-(from-Gian-Visser)?p=15519636#post15519636

Afrihost-Gian said:
Hey Guys.

Gian Visser, CEO of Afrihost here.

First, I sincerely apologise for the poor internet experience that I know some of you have been having on our DSL network.

I know that many of you have been unhappy with us, and I completely understand where you’re coming from. I’m hoping that by opening this thread, we can start discussing what is happening and what we're doing to fix it.

I hope that I can start rebuilding any trust that has been broken between us - I know you expect the best from us and I know that lately you haven't always received the pure internet joy we strive to give you.
Click to expand...

Please post your direct feedback on that thread, Gian would like to be able to personally answer as many questions as he can, but seeing as he is a very busy dude, the Afrireps will also be jumping in wherever we can with info.
 
Last edited:
AfriMan said:
Glad to hear it's back to normal. It seems to be a Google thing or somehow our link to however Google does stuff locally. I couldn't say though, the experts will need to weigh in.
Click to expand...

A Google thing that only you guys have an issue with. Poor performance is back. Watching YouTube, speed caps at ~2000kbit. Chrome and IE.

Code: 
Tracing route to youtube.co.za [173.194.65.93]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    17 ms    16 ms    16 ms  41.181.221.217
  4    16 ms    16 ms    15 ms  41.181.221.218
  5    16 ms    16 ms    16 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
  6   213 ms   213 ms   212 ms  xp-dca-1.za--xp-cr-1.za-a.mtnns.net [196.44.0.155]
  7   214 ms   213 ms   213 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  8   213 ms   213 ms   213 ms  ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
  9   228 ms   235 ms   228 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
 10   219 ms   220 ms   219 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
 11   220 ms   220 ms   220 ms  core2.ams.net.google.com [80.249.209.100]
 12   220 ms   220 ms   220 ms  209.85.240.61
 13   221 ms   220 ms   220 ms  209.85.240.138
 14   227 ms   233 ms   250 ms  216.239.46.167
 15   234 ms   240 ms   241 ms  216.239.49.28
 16     *        *        *     Request timed out.
 17   247 ms   252 ms   256 ms  ee-in-f93.1e100.net [173.194.65.93]

Trace complete.

I could've sworn tracing YouTube used to go to cache.google.com

Aren't 196.xxx.xxx.xxx block, South Africa-based?
 
Vorastra said:
A Google thing that only you guys have an issue with. Poor performance is back. Watching YouTube, speed caps at ~2000kbit. Chrome and IE.

Code: 
Tracing route to youtube.co.za [173.194.65.93]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    17 ms    16 ms    16 ms  41.181.221.217
  4    16 ms    16 ms    15 ms  41.181.221.218
  5    16 ms    16 ms    16 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
  6   213 ms   213 ms   212 ms  xp-dca-1.za--xp-cr-1.za-a.mtnns.net [196.44.0.155]
  7   214 ms   213 ms   213 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  8   213 ms   213 ms   213 ms  ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
  9   228 ms   235 ms   228 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
 10   219 ms   220 ms   219 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
 11   220 ms   220 ms   220 ms  core2.ams.net.google.com [80.249.209.100]
 12   220 ms   220 ms   220 ms  209.85.240.61
 13   221 ms   220 ms   220 ms  209.85.240.138
 14   227 ms   233 ms   250 ms  216.239.46.167
 15   234 ms   240 ms   241 ms  216.239.49.28
 16     *        *        *     Request timed out.
 17   247 ms   252 ms   256 ms  ee-in-f93.1e100.net [173.194.65.93]

Trace complete.

I could've sworn tracing YouTube used to go to cache.google.com

Aren't 196.xxx.xxx.xxx block, South Africa-based?
Click to expand...

It's definitely an issue that's isolated to us. Hopefully it's resolved shortly.
 
Afrihost download speeds are useless this evening, on top of that using the turbocharge feature, officially does NOTHING

*Raging and Fuming*

such poor services these last few weeks, im seriously considering changing ISP,

Ontop of all that afrihost is getting expensive, they used be competitive now its looking to me a change is necessary, I recommend others follow and show them this is UNACCEPTABLE
 
Ifrit said:
Afrihost download speeds are useless this evening, on top of that using the turbocharge feature, officially does NOTHING

*Raging and Fuming*

such poor services these last few weeks, im seriously considering changing ISP,

Ontop of all that afrihost is getting expensive, they used be competitive now its looking to me a change is necessary, I recommend others follow and show them this is UNACCEPTABLE
Click to expand...

We know that the experience has been inconsistent lately, and at worst it can be pretty horrible -when demand on the network is very high and we see increased latency. We have a plan to work through all these issues by completely revamping our network. Our CEO, Gian outlines everything here (if you have not seen this yet).

We are hoping to be able to have test account available soon for clients to start trying out the new experience, and this will offer them an alternative, but also relieve demand on the current infrastructure.

Please bear with me a little longer. I really believe this is going to be a really awesome next step. I'm waiting to get a test account myself.
 
@Afriman, i pm'd you some questions as im having and have been having slow/ non existant speeds on news (nntp)
 
Feedback as just having switched over from MWEB Uncapped 4 Mbps Premium to AFRIHOST Uncapped 4 Mbps..
Latency is quite high but strangely wouldn't describe the Internet experience as being slow...
Only problem is when using TeamViewer remotely response has a bit of lag.

http://speedtest.mybroadband.co.za/

JHB
Your Latest Results
223138233.png
Last Result:
Download Speed: 860 kbps (107.5 KB/sec transfer rate)
Upload Speed: 112 kbps (14 KB/sec transfer rate)
Latency: 665 ms
Jitter: 95 ms
7/1/2015, 4:58:17 PM

CPT
Your Latest Results
223140135.png
Last Result:
Download Speed: 842 kbps (105.3 KB/sec transfer rate)
Upload Speed: 154 kbps (19.3 KB/sec transfer rate)
Latency: 332 ms
Jitter: 336 ms
7/1/2015, 5:01:07 PM
 
TRACE ROUTES

Code: 
C:\Windows\system32>tracert speedtest.mybroadband.co.za

Tracing route to speedtest.mybroadband.co.za [196.10.98.18]
over a maximum of 30 hops:

  1     2 ms     1 ms     2 ms  ROUTER
  2    46 ms    22 ms    27 ms  105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.
3.129]
  3    39 ms    33 ms    40 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
  4    62 ms    77 ms    74 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5    49 ms    50 ms    53 ms  jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.17
1]
  6    47 ms    62 ms    60 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   221 ms   252 ms   224 ms  ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

  8   252 ms   254 ms   285 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
  9   355 ms   234 ms   284 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
 10     *        *        *     Request timed out.
 11   271 ms   255 ms   313 ms  100ge9-1.core1.lon2.he.net [72.52.92.213]
 12   231 ms   252 ms   284 ms  frogfoot-networks-pty-ltd.10gigabitethernet1-2.c
ore1.lon2.he.net [216.66.84.134]
 13   305 ms   230 ms   226 ms  jhb-br-r2-gi0-0-3906.frogfoot.net [41.85.1.83]
 14   244 ms   229 ms   265 ms  jhb-cor-sw1-vlan3902.frogfoot.net [41.85.0.99]
 15   436 ms   431 ms   422 ms  teraco.co.za [41.206.220.141]
 16   435 ms   413 ms   426 ms  196.10.98.18.teraco.co.za [196.10.98.18]

Trace complete.

Google Services are an Improvement over MWEB for sure..

Code: 
C:\Windows\system32>tracert www.google.co.za

Tracing route to www.google.co.za [66.8.14.26]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  ROUTER
  2    23 ms    37 ms    31 ms  105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.
3.129]
  3    55 ms    41 ms    50 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    25 ms    34 ms    46 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    38 ms    58 ms    27 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6    33 ms    54 ms    41 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7    36 ms    38 ms    48 ms  cache.google.com [66.8.14.26]

Trace complete.
 
PING..

Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>ping -t www.google.co.za

Pinging www.google.co.za [66.8.14.16] with 32 bytes of data:
Reply from 66.8.14.16: bytes=32 time=47ms TTL=58
Reply from 66.8.14.16: bytes=32 time=23ms TTL=58
Reply from 66.8.14.16: bytes=32 time=46ms TTL=58
Reply from 66.8.14.16: bytes=32 time=19ms TTL=58
Reply from 66.8.14.16: bytes=32 time=22ms TTL=58
Reply from 66.8.14.16: bytes=32 time=35ms TTL=58
Reply from 66.8.14.16: bytes=32 time=88ms TTL=58
Reply from 66.8.14.16: bytes=32 time=70ms TTL=58
Reply from 66.8.14.16: bytes=32 time=28ms TTL=58
Reply from 66.8.14.16: bytes=32 time=32ms TTL=58
Reply from 66.8.14.16: bytes=32 time=23ms TTL=58
Reply from 66.8.14.16: bytes=32 time=65ms TTL=58
Reply from 66.8.14.16: bytes=32 time=60ms TTL=58
Reply from 66.8.14.16: bytes=32 time=75ms TTL=58
Reply from 66.8.14.16: bytes=32 time=26ms TTL=58
Reply from 66.8.14.16: bytes=32 time=30ms TTL=58
Reply from 66.8.14.16: bytes=32 time=98ms TTL=58
Reply from 66.8.14.16: bytes=32 time=23ms TTL=58
Reply from 66.8.14.16: bytes=32 time=21ms TTL=58
Reply from 66.8.14.16: bytes=32 time=145ms TTL=58
Reply from 66.8.14.16: bytes=32 time=24ms TTL=58
Reply from 66.8.14.16: bytes=32 time=46ms TTL=58
Reply from 66.8.14.16: bytes=32 time=107ms TTL=58
Reply from 66.8.14.16: bytes=32 time=88ms TTL=58

Ping statistics for 66.8.14.16:
    Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 145ms, Average = 51ms
Control-C
^C
C:\Windows\system32>ping -t www.gmail.com

Pinging googlemail.l.google.com [216.58.223.5] with 32 bytes of data:
Reply from 216.58.223.5: bytes=32 time=61ms TTL=53
Reply from 216.58.223.5: bytes=32 time=114ms TTL=53
Reply from 216.58.223.5: bytes=32 time=124ms TTL=53
Reply from 216.58.223.5: bytes=32 time=27ms TTL=53
Reply from 216.58.223.5: bytes=32 time=69ms TTL=53
Reply from 216.58.223.5: bytes=32 time=81ms TTL=53
Reply from 216.58.223.5: bytes=32 time=53ms TTL=53
Reply from 216.58.223.5: bytes=32 time=93ms TTL=53
Reply from 216.58.223.5: bytes=32 time=74ms TTL=53
Reply from 216.58.223.5: bytes=32 time=22ms TTL=53
Reply from 216.58.223.5: bytes=32 time=65ms TTL=53
Reply from 216.58.223.5: bytes=32 time=42ms TTL=53
Reply from 216.58.223.5: bytes=32 time=45ms TTL=53
Reply from 216.58.223.5: bytes=32 time=55ms TTL=53
Reply from 216.58.223.5: bytes=32 time=77ms TTL=53
Reply from 216.58.223.5: bytes=32 time=63ms TTL=53
Reply from 216.58.223.5: bytes=32 time=48ms TTL=53
Reply from 216.58.223.5: bytes=32 time=56ms TTL=53
Reply from 216.58.223.5: bytes=32 time=109ms TTL=53
Reply from 216.58.223.5: bytes=32 time=59ms TTL=53
Reply from 216.58.223.5: bytes=32 time=50ms TTL=53
Reply from 216.58.223.5: bytes=32 time=41ms TTL=53
Reply from 216.58.223.5: bytes=32 time=67ms TTL=53
Reply from 216.58.223.5: bytes=32 time=46ms TTL=53

Ping statistics for 216.58.223.5:
    Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 124ms, Average = 64ms
Control-C
^C
C:\Windows\system32>ping -t www.speedtest.mybroadband.co.za

Pinging www.speedtest.mybroadband.co.za [196.10.98.18] with 32 bytes of data:
Reply from 196.10.98.18: bytes=32 time=442ms TTL=48
Reply from 196.10.98.18: bytes=32 time=456ms TTL=48
Reply from 196.10.98.18: bytes=32 time=460ms TTL=48
Reply from 196.10.98.18: bytes=32 time=491ms TTL=48
Reply from 196.10.98.18: bytes=32 time=426ms TTL=48
Reply from 196.10.98.18: bytes=32 time=407ms TTL=48
Reply from 196.10.98.18: bytes=32 time=470ms TTL=48
Reply from 196.10.98.18: bytes=32 time=414ms TTL=48
Reply from 196.10.98.18: bytes=32 time=417ms TTL=48
Reply from 196.10.98.18: bytes=32 time=474ms TTL=48
Reply from 196.10.98.18: bytes=32 time=401ms TTL=48
Reply from 196.10.98.18: bytes=32 time=430ms TTL=48
Reply from 196.10.98.18: bytes=32 time=413ms TTL=48
Reply from 196.10.98.18: bytes=32 time=425ms TTL=48
Reply from 196.10.98.18: bytes=32 time=437ms TTL=48
Reply from 196.10.98.18: bytes=32 time=411ms TTL=48
Reply from 196.10.98.18: bytes=32 time=412ms TTL=48
Reply from 196.10.98.18: bytes=32 time=437ms TTL=48
Reply from 196.10.98.18: bytes=32 time=417ms TTL=48
Reply from 196.10.98.18: bytes=32 time=457ms TTL=48
Reply from 196.10.98.18: bytes=32 time=414ms TTL=48
Reply from 196.10.98.18: bytes=32 time=419ms TTL=48
Reply from 196.10.98.18: bytes=32 time=405ms TTL=48
Reply from 196.10.98.18: bytes=32 time=429ms TTL=48
Reply from 196.10.98.18: bytes=32 time=425ms TTL=48
Reply from 196.10.98.18: bytes=32 time=441ms TTL=48
Reply from 196.10.98.18: bytes=32 time=408ms TTL=48
Reply from 196.10.98.18: bytes=32 time=433ms TTL=48
Reply from 196.10.98.18: bytes=32 time=453ms TTL=48
Reply from 196.10.98.18: bytes=32 time=413ms TTL=48
Reply from 196.10.98.18: bytes=32 time=438ms TTL=48
Reply from 196.10.98.18: bytes=32 time=437ms TTL=48
Reply from 196.10.98.18: bytes=32 time=400ms TTL=48
Reply from 196.10.98.18: bytes=32 time=513ms TTL=48
Reply from 196.10.98.18: bytes=32 time=436ms TTL=48
Reply from 196.10.98.18: bytes=32 time=410ms TTL=48
Reply from 196.10.98.18: bytes=32 time=433ms TTL=48
Reply from 196.10.98.18: bytes=32 time=414ms TTL=48
Reply from 196.10.98.18: bytes=32 time=428ms TTL=48
Reply from 196.10.98.18: bytes=32 time=425ms TTL=48
Reply from 196.10.98.18: bytes=32 time=436ms TTL=48
Reply from 196.10.98.18: bytes=32 time=405ms TTL=48
Reply from 196.10.98.18: bytes=32 time=446ms TTL=48

Ping statistics for 196.10.98.18:
    Packets: Sent = 43, Received = 43, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 400ms, Maximum = 513ms, Average = 431ms
Control-C
^C
C:\Windows\system32>ping -t www.mybroadband.co.za

Pinging www.mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=55ms TTL=49
Reply from 197.242.89.170: bytes=32 time=55ms TTL=49
Reply from 197.242.89.170: bytes=32 time=77ms TTL=49
Reply from 197.242.89.170: bytes=32 time=56ms TTL=49
Reply from 197.242.89.170: bytes=32 time=77ms TTL=49
Reply from 197.242.89.170: bytes=32 time=50ms TTL=49
Reply from 197.242.89.170: bytes=32 time=50ms TTL=49
Reply from 197.242.89.170: bytes=32 time=54ms TTL=49
Reply from 197.242.89.170: bytes=32 time=55ms TTL=49
Reply from 197.242.89.170: bytes=32 time=63ms TTL=49
Reply from 197.242.89.170: bytes=32 time=72ms TTL=49
Reply from 197.242.89.170: bytes=32 time=60ms TTL=49
Reply from 197.242.89.170: bytes=32 time=83ms TTL=49
Reply from 197.242.89.170: bytes=32 time=41ms TTL=49
Reply from 197.242.89.170: bytes=32 time=90ms TTL=49
Reply from 197.242.89.170: bytes=32 time=82ms TTL=49
Reply from 197.242.89.170: bytes=32 time=87ms TTL=49
Reply from 197.242.89.170: bytes=32 time=59ms TTL=49
Reply from 197.242.89.170: bytes=32 time=83ms TTL=49
Reply from 197.242.89.170: bytes=32 time=75ms TTL=49
Reply from 197.242.89.170: bytes=32 time=56ms TTL=49
Reply from 197.242.89.170: bytes=32 time=48ms TTL=49
Reply from 197.242.89.170: bytes=32 time=129ms TTL=49

Ping statistics for 197.242.89.170:
    Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 41ms, Maximum = 129ms, Average = 67ms
Control-C
^C
C:\Windows\system32>ping -t www.afrihost.com

Pinging www.afrihost.com [41.181.185.18] with 32 bytes of data:
Reply from 41.181.185.18: bytes=32 time=34ms TTL=57
Reply from 41.181.185.18: bytes=32 time=25ms TTL=57
Reply from 41.181.185.18: bytes=32 time=27ms TTL=57
Reply from 41.181.185.18: bytes=32 time=47ms TTL=57
Reply from 41.181.185.18: bytes=32 time=63ms TTL=57
Reply from 41.181.185.18: bytes=32 time=92ms TTL=57
Reply from 41.181.185.18: bytes=32 time=183ms TTL=57
Reply from 41.181.185.18: bytes=32 time=29ms TTL=57
Reply from 41.181.185.18: bytes=32 time=30ms TTL=57
Reply from 41.181.185.18: bytes=32 time=73ms TTL=57
Reply from 41.181.185.18: bytes=32 time=27ms TTL=57
Reply from 41.181.185.18: bytes=32 time=34ms TTL=57
Reply from 41.181.185.18: bytes=32 time=51ms TTL=57
Reply from 41.181.185.18: bytes=32 time=75ms TTL=57
Reply from 41.181.185.18: bytes=32 time=27ms TTL=57
Reply from 41.181.185.18: bytes=32 time=39ms TTL=57
Reply from 41.181.185.18: bytes=32 time=30ms TTL=57
Reply from 41.181.185.18: bytes=32 time=32ms TTL=57
Reply from 41.181.185.18: bytes=32 time=50ms TTL=57
Reply from 41.181.185.18: bytes=32 time=71ms TTL=57
Reply from 41.181.185.18: bytes=32 time=30ms TTL=57
Reply from 41.181.185.18: bytes=32 time=40ms TTL=57
Reply from 41.181.185.18: bytes=32 time=49ms TTL=57

Ping statistics for 41.181.185.18:
    Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 183ms, Average = 50ms
Control-C
^C
C:\Windows\system32>
 
Morning everyone

We are aware that latency in the South was pretty awful yesterday, especially around midday and then again in the evening. The East seemed to be pretty poor from the morning up until just before 6pm.

The network team are looking into this to see if anything can be done to improve this on our side. We'll definitely want to keep latency as tight as possible in the coming days at least until we can start having clients test our POC networks, which should also relieve pressure on the current network and reduce demand and latency.

If I get any further updates, I will post up here.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X