Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Is it fair to say that the Afrihost network is reaching capacity again, specifically in the south?
Support has pretty much said that they think the issues I'm having on my Business Account during this time of the evening is shaping. Seeing that you don't intend shaping business accounts unless there is strain, that can only point to strain/capacity issues.
 
Would you mind posting a traceroute to the CS:GO server?

Game server

Code:
Tracing route to 197-80-200-51.jhb.mweb.co.za [197.80.200.51]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    25 ms    49 ms    24 ms  jhb-up7.ip.adsl.co.za [169.1.5.6]
  4    23 ms    27 ms    24 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  5    26 ms    26 ms    26 ms  mweb.ixp.joburg [196.46.25.145]
  6    25 ms    25 ms    25 ms  197-80-7-111.jhb.mweb.co.za [197.80.7.111]
  7    26 ms    25 ms    26 ms  bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
  8    25 ms    24 ms    25 ms  197-80-96-30.jhb.mweb.co.za [197.80.96.30]
  9    25 ms    25 ms    25 ms  197-80-200-51.jhb.mweb.co.za [197.80.200.51]

Teamspeak:

Code:
Tracing route to 152.111.***.*** over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    26 ms    24 ms    25 ms  jhb-up7.ip.adsl.co.za [169.1.5.6]
  4    27 ms    23 ms    28 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  5    26 ms    25 ms    26 ms  mweb.ixp.joburg [196.46.25.145]
  6    51 ms    46 ms    75 ms  te0-7-0-3.vic-p-2.optinet.net [197.80.7.98]
  7    49 ms    50 ms    50 ms  te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
  8    46 ms    46 ms    46 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254]
  9    46 ms    45 ms    45 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
 10    46 ms    46 ms    47 ms  196.41.144.34
 11    47 ms    46 ms    46 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
 12    46 ms    45 ms    46 ms  152.111.***.***

Teamspeak live connection stats:

7382d6dadc.png


dd8560f52c.png


Since a few weeks ago every night it seems to be like this.
 
Is it fair to say that the Afrihost network is reaching capacity again, specifically in the south?
Support has pretty much said that they think the issues I'm having on my Business Account during this time of the evening is shaping. Seeing that you don't intend shaping business accounts unless there is strain, that can only point to strain/capacity issues.

Are you also seeing dodgey results on 169.1.5.128?

Code:
Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=92ms TTL=60
Reply from 169.1.5.128: bytes=32 time=99ms TTL=60
Reply from 169.1.5.128: bytes=32 time=95ms TTL=60
Reply from 169.1.5.128: bytes=32 time=90ms TTL=60
Reply from 169.1.5.128: bytes=32 time=61ms TTL=60
Reply from 169.1.5.128: bytes=32 time=68ms TTL=60
Reply from 169.1.5.128: bytes=32 time=64ms TTL=60
Reply from 169.1.5.128: bytes=32 time=71ms TTL=60
Reply from 169.1.5.128: bytes=32 time=85ms TTL=60
Reply from 169.1.5.128: bytes=32 time=91ms TTL=60
Reply from 169.1.5.128: bytes=32 time=97ms TTL=60
Reply from 169.1.5.128: bytes=32 time=87ms TTL=60
Reply from 169.1.5.128: bytes=32 time=109ms TTL=60
Reply from 169.1.5.128: bytes=32 time=121ms TTL=60
Reply from 169.1.5.128: bytes=32 time=57ms TTL=60
Reply from 169.1.5.128: bytes=32 time=102ms TTL=60
Reply from 169.1.5.128: bytes=32 time=85ms TTL=60
Reply from 169.1.5.128: bytes=32 time=78ms TTL=60
Reply from 169.1.5.128: bytes=32 time=67ms TTL=60
Reply from 169.1.5.128: bytes=32 time=58ms TTL=60
 
Is it fair to say that the Afrihost network is reaching capacity again, specifically in the south?
Support has pretty much said that they think the issues I'm having on my Business Account during this time of the evening is shaping. Seeing that you don't intend shaping business accounts unless there is strain, that can only point to strain/capacity issues.

I don't think that is the case. Which services are you having trouble with that lead you to think you're being shaped?
 
Are you also seeing dodgey results on 169.1.5.128?

Code:
Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=92ms TTL=60
Reply from 169.1.5.128: bytes=32 time=99ms TTL=60
Reply from 169.1.5.128: bytes=32 time=95ms TTL=60
Reply from 169.1.5.128: bytes=32 time=90ms TTL=60
Reply from 169.1.5.128: bytes=32 time=61ms TTL=60
Reply from 169.1.5.128: bytes=32 time=68ms TTL=60
Reply from 169.1.5.128: bytes=32 time=64ms TTL=60
Reply from 169.1.5.128: bytes=32 time=71ms TTL=60
Reply from 169.1.5.128: bytes=32 time=85ms TTL=60
Reply from 169.1.5.128: bytes=32 time=91ms TTL=60
Reply from 169.1.5.128: bytes=32 time=97ms TTL=60
Reply from 169.1.5.128: bytes=32 time=87ms TTL=60
Reply from 169.1.5.128: bytes=32 time=109ms TTL=60
Reply from 169.1.5.128: bytes=32 time=121ms TTL=60
Reply from 169.1.5.128: bytes=32 time=57ms TTL=60
Reply from 169.1.5.128: bytes=32 time=102ms TTL=60
Reply from 169.1.5.128: bytes=32 time=85ms TTL=60
Reply from 169.1.5.128: bytes=32 time=78ms TTL=60
Reply from 169.1.5.128: bytes=32 time=67ms TTL=60
Reply from 169.1.5.128: bytes=32 time=58ms TTL=60

No that hop is ok my side.
 
I don't think that is the case. Which services are you having trouble with that lead you to think you're being shaped?

I don't think that is the case. Which services are you having trouble with that lead you to think you're being shaped?

I've been struggling with Android updates running very inconsistently. A few days ago I got no throughput between the hours of 8pm and 22pm. It's gotten better, but still very inconsistent. The speed would jump up and down between 10Kbps -> 3Mbps -> 200Kbps, etc etc.

P2P also completely dead. Getting less than 1Kb on a torrent that was full speed before 8PM.

Just switched over to Telkom account. Android update runs full speed and P2P also. Switch back to Afrihost and the Android updates again stop. It's now actually at no throughput.

Code:
ping play.google.com -n 10

Pinging play.l.google.com [216.58.223.46] with 32 bytes of data:
Reply from 216.58.223.46: bytes=32 time=36ms TTL=54
Reply from 216.58.223.46: bytes=32 time=38ms TTL=54
Reply from 216.58.223.46: bytes=32 time=41ms TTL=54
Reply from 216.58.223.46: bytes=32 time=55ms TTL=54
Reply from 216.58.223.46: bytes=32 time=48ms TTL=54
Reply from 216.58.223.46: bytes=32 time=50ms TTL=54
Reply from 216.58.223.46: bytes=32 time=55ms TTL=54

Ping statistics for 216.58.223.46:
    Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Reply from 216.58.223.46: Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 55ms, Average = 46ms
bytes=32 Control-C
^C

ping bras.afrihost.com -n 10

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 8ms, Average = 6ms
 
I don't think that is the case. Which services are you having trouble with that lead you to think you're being shaped?

Using the 1GB test account now and it also runs full speed with both Android updates and P2P. So it's the uncapped accounts being shaped. As I understand your policies business accounts will not be shaped unless really necessary. If it's necessary every evening then that points out you don't have enough capacity for these times of the day.
 
What's happened to email? Can't connect to any of my accounts either on pc or via webmail site. General fault or something on my side?
 
We're seeing issues on DSLMail - mail accounts affected are @afrihost.co.za.
Our team are working on a fix and things should be resolved soon.
 
Huge amount of Telkom outages being reported this morning.
Listed areas with known faults as follows:

023-312, 316
018-484, 468, 632, 294, 462, 290, 464, 683, 468, 786, 788, 386, 381, 384, 392, 290, 293 & more being reported
027-217
011-462, 704, 609, 976, 393
031-467, 916
012-548, 546, 565, 543, 567, 375, 244, 327, 998, 804, 346, 460 & more being reported
041-367, 368
014-597, 574, 555 & more being reported
021-913, 916, 948
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X