Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Is there something wrong with the userCP?

When going to "Change to Another Package" under my current data account it just shows this:

AfriCP.png
 
I still have 280 ping LoL EuW.
pings are normal though.
Code: 
Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=206ms TTL=45
Reply from 194.183.128.94: bytes=32 time=206ms TTL=45
Reply from 194.183.128.94: bytes=32 time=202ms TTL=45
Reply from 194.183.128.94: bytes=32 time=201ms TTL=45

Ping statistics for 194.183.128.94:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 201ms, Maximum = 206ms, Average = 203ms
 
AfriMan said:
We're definitely looking into this and I'm confident the guys will get it sorted :)
Click to expand...

And the latency shot up again, getting over 300ms.
seems like it usually happens around about 4:30pm or just before.
Lasts till about 1-2am.
 
@AH, would you say 9504 Downstream CRC errors in 6 Hours and 15 min is a fault?
 
Last edited:
Johnatan56 said:
I still have 280 ping LoL EuW.
pings are normal though.
Code: 
Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=206ms TTL=45
Reply from 194.183.128.94: bytes=32 time=206ms TTL=45
Reply from 194.183.128.94: bytes=32 time=202ms TTL=45
Reply from 194.183.128.94: bytes=32 time=201ms TTL=45

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

I tried pinging that IP address - 194.183.128.94
Got this result:
Pinging 194.183.128.94 with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=198ms TTL=42
Reply from 194.183.128.94: bytes=32 time=198ms TTL=42
Reply from 194.183.128.94: bytes=32 time=198ms TTL=42
Reply from 194.183.128.94: bytes=32 time=198ms TTL=42

Ping statistics for 194.183.128.94:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 198ms, Average = 198ms.

Then I tired the usual server IPs

Pinging 185.40.65.1 with 32 bytes of data:

Reply from 185.40.65.1: bytes=32 time=267ms TTL=41
Reply from 185.40.65.1: bytes=32 time=275ms TTL=41
Reply from 185.40.65.1: bytes=32 time=275ms TTL=42
Reply from 185.40.65.1: bytes=32 time=279ms TTL=42

Ping statistics for 185.40.65.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 279ms, Average = 274ms

and

Pinging 162.249.72.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 162.249.72.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
Just an update guys, we've logged the issue with Mweb for the latency on their network, we'll keep you updated as we receive news.
 
Still getting a lovely 300ms to any european servers, been like this for the last 4 days :) Go Afrihost! :whistle:
 
Can someone explain this to me:

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

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *       11 ms     9 ms  jhb-up7.ip.adsl.co.za [169.1.5.6]
  4    12 ms    10 ms    12 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  5    11 ms    11 ms    11 ms  mweb.ixp.joburg [196.46.25.145]
  6    53 ms    55 ms    61 ms  201.bu-ether5.vic-pe-2.optinet.net [197.80.7.71]
  7    15 ms    11 ms    11 ms  197-81-226-81.jhb.mweb.co.za [197.81.226.81]
  8    11 ms    15 ms    11 ms  197-81-226-61.jhb.mweb.co.za [197.81.226.61]
  9    18 ms    18 ms    16 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 10    10 ms    11 ms    11 ms  197-81-229-17.jhb.mweb.co.za [197.81.229.17]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Showing timeouts to BTgames.co.za yet the webpage loads in seconds?
 
Rickster said:
Can someone explain this to me:

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

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *       11 ms     9 ms  jhb-up7.ip.adsl.co.za [169.1.5.6]
  4    12 ms    10 ms    12 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  5    11 ms    11 ms    11 ms  mweb.ixp.joburg [196.46.25.145]
  6    53 ms    55 ms    61 ms  201.bu-ether5.vic-pe-2.optinet.net [197.80.7.71]
  7    15 ms    11 ms    11 ms  197-81-226-81.jhb.mweb.co.za [197.81.226.81]
  8    11 ms    15 ms    11 ms  197-81-226-61.jhb.mweb.co.za [197.81.226.61]
  9    18 ms    18 ms    16 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 10    10 ms    11 ms    11 ms  197-81-229-17.jhb.mweb.co.za [197.81.229.17]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Showing timeouts to BTgames.co.za yet the webpage loads in seconds?
Click to expand...

You generally get results like that went routers and switches are configured to not response ICMP traffic. The site could even be hosted behind a firewall that blocks ICMP traffic entirely.
 
I'm seeing a ~20-30ms jitter on local latency to quake live tonight on Afrihost. No jitter on competing ISPs that I use.
 
Vio said:
I'm seeing a ~20-30ms jitter on local latency to quake live tonight on Afrihost. No jitter on competing ISPs that I use.
Click to expand...

Which Quake Live Server are you playing on at the moment?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X