Afrihost Capped DSL Feedback

Johnatan56 said:
By same place you mean?
Code: 
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 6ms, Average = 6ms
Code: 
Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1]
  2     *        *        *     Request timed out.
  3    93 ms    84 ms    70 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4   144 ms   146 ms   147 ms  169-1-21-66.ip.afrihost.co.za [169.1.21.66]
  5   133 ms     *      119 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6   136 ms   140 ms   138 ms  ^C
Click to expand...

:(

Thanks.

How is your throughput looking at the moment?
 
AfriGenie said:
:(

Thanks.

How is your throughput looking at the moment?
Click to expand...
Bad. Less than 1.8 Mbps.
permanent buffer.jpg
permanent buffering.
Notice the view count.

Then I left it for two minutes to see if it improved:
I left it for a bit.png
 
Last edited:
AfriFella said:
Was this the only video you had trouble with? Just checked it out and it's not a very popular video (in terms of views) and the likelihood of it not being cached on our network yet is fairly high. You might have noticed better performance streaming it for a second time. Happy to continue testing it if you're still having trouble on Youtube, though. :)
Click to expand...

What difference if it's cached or not? You only cache stuff to save on int transport, should still work if you have enough int capacity! AH = NOOBS!
 
squish0601 said:
Everything. As usual.
Bad latency and terrible throughput.
Was perfect till 20h00
Click to expand...

Sorry to hear that. :( Could you please send me some test results if it happens again? I'd love to pass it onto our Network Team.
 
AfriFella said:
Sorry to hear that. :( Could you please send me some test results if it happens again? I'd love to pass it onto our Network Team.
Click to expand...

Erm I already gave them at least three times already. I'm pretty sure you can just point them at where the latency increases and get them to upgrade it.
 
Not nice tonight…Cape Town 4mb capped shaped

http://netgauge.ookla.com/share/623374819.png

C:\Windows\system32>tracert afrihost.com

Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 220 ms * 397 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 215 ms 208 ms 229 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 * 351 ms 263 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 208 ms 206 ms 176 ms 41.164.52.40
7 238 ms 183 ms 161 ms 172.18.1.164
8 205 ms 216 ms * cloudflare.ixp.joburg [196.60.8.198]
9 243 ms 182 ms 241 ms 104.20.30.244

Trace complete.

C:\Windows\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=118ms TTL=63
Reply from 155.239.255.250: bytes=32 time=207ms TTL=63
Reply from 155.239.255.250: bytes=32 time=198ms TTL=63
Reply from 155.239.255.250: bytes=32 time=214ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 214ms, Average = 184ms
 
Nikkel said:
Not nice tonight…Cape Town 4mb capped shaped

http://netgauge.ookla.com/share/623374819.png

C:\Windows\system32>tracert afrihost.com

Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 220 ms * 397 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 215 ms 208 ms 229 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 * 351 ms 263 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 208 ms 206 ms 176 ms 41.164.52.40
7 238 ms 183 ms 161 ms 172.18.1.164
8 205 ms 216 ms * cloudflare.ixp.joburg [196.60.8.198]
9 243 ms 182 ms 241 ms 104.20.30.244

Trace complete.

C:\Windows\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=118ms TTL=63
Reply from 155.239.255.250: bytes=32 time=207ms TTL=63
Reply from 155.239.255.250: bytes=32 time=198ms TTL=63
Reply from 155.239.255.250: bytes=32 time=214ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 214ms, Average = 184ms
Click to expand...

Ugh!

It looks like the latency is starting on your DSL line or Exchange from those results. Do we manage your DSL line? If we do, PM me your DSL Line number and I'll see if a Port Recreate helps.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X