Afrihost New Network Feedback

Status
Not open for further replies.
This company is so full of bullsh*t. There's clearly a problem affecting their whole network for a while and yet nothing is done, and when you contact their customer service line, the representatives try and reset your personal line, as if the problem has something to do with you. Never once acknowledging or even suggesting that they are to blame >:(
^This

My last support ticket regarding this was a port reset lol
 
im getting heavy packet loss, i logged a ticket and they fixed it last night, but it started happening again??? was it a terrible idea to move back to AH seeing as i have been with them for a month now.

I moved because all i heard was good things??
 
im getting heavy packet loss, i logged a ticket and they fixed it last night, but it started happening again??? was it a terrible idea to move back to AH seeing as i have been with them for a month now.

I moved because all i heard was good things??

All things were good :/
 
Happened when they moved from IS to MTN, happened when their new MTN overlords neglected their IPConnect provisions, happening now after the move to Echo.
 
Getting massive packet loss on capped and uncapped afrihost accounts.
 
Yeah something is afoot, speedtest reports line running at full speed with ok ping, but the net is painfully slow!
 
Funny how I don't experience issues when everyone else is, and do experience issues when no one else is.

No issues atm for me.
 
All right here, seems to be mostly Jo'burg that's having an issue.
Code:
Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=201ms TTL=45
Reply from 194.183.128.94: bytes=32 time=199ms TTL=45
Reply from 194.183.128.94: bytes=32 time=197ms TTL=45
Reply from 194.183.128.94: bytes=32 time=198ms TTL=45
Reply from 194.183.128.94: bytes=32 time=196ms TTL=45
Reply from 194.183.128.94: bytes=32 time=197ms TTL=45
Reply from 194.183.128.94: bytes=32 time=200ms TTL=45
Reply from 194.183.128.94: bytes=32 time=196ms TTL=45
Reply from 194.183.128.94: bytes=32 time=197ms TTL=45
Reply from 194.183.128.94: bytes=32 time=200ms TTL=45
Reply from 194.183.128.94: bytes=32 time=196ms TTL=45
Reply from 194.183.128.94: bytes=32 time=292ms TTL=45
Reply from 194.183.128.94: bytes=32 time=197ms TTL=45
Reply from 194.183.128.94: bytes=32 time=198ms TTL=45
Reply from 194.183.128.94: bytes=32 time=196ms TTL=45
Reply from 194.183.128.94: bytes=32 time=198ms TTL=45
Reply from 194.183.128.94: bytes=32 time=197ms TTL=45

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

EDIT: Just had a league game, good for periods of time and then 1/2s of extreme lag, 1kms+
Doesn't show up on tracert/ping
 
Last edited:
and Durban:

Code:
C:\Users\wingnut>ping -n 20 [url]www.vienna.at[/url]

Pinging [url]www.vienna.at[/url] [194.183.128.94] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 194.183.128.94: bytes=32 time=206ms TTL=39
Reply from 194.183.128.94: bytes=32 time=205ms TTL=39
Reply from 194.183.128.94: bytes=32 time=206ms TTL=39
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 194.183.128.94: bytes=32 time=206ms TTL=40
Request timed out.
Reply from 194.183.128.94: bytes=32 time=206ms TTL=40
Reply from 194.183.128.94: bytes=32 time=205ms TTL=40
Reply from 194.183.128.94: bytes=32 time=206ms TTL=40
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 194.183.128.94:
    Packets: Sent = 20, Received = 7, Lost = 13 (65% loss),
Approximate round trip times in milli-seconds:
    Minimum = 205ms, Maximum = 206ms, Average = 205ms

C:\Users\wingnut>tracert [url]www.vienna.at[/url]

Tracing route to [url]www.vienna.at[/url] [194.183.128.94]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    16 ms    14 ms    14 ms  dbn-up2.ip.adsl.co.za [169.1.5.162]
  3    15 ms    15 ms    14 ms  dbn-in1.ip.adsl.co.za [169.1.5.204]
  4    14 ms    14 ms    14 ms  41.162.84.192
  5    24 ms    22 ms    23 ms  172.18.1.162
  6     *        *        *     Request timed out.
  7   197 ms   223 ms   197 ms  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.20
6.178.2]
  8     *      166 ms   165 ms  if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6
]
  9   187 ms   187 ms   187 ms  if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [8
0.231.158.1]
 10   187 ms   190 ms   184 ms  if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.
159.85]
 11   188 ms   189 ms   187 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.1
58.5]
 12   183 ms   183 ms   183 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.2
31.158.30]
 13   191 ms   191 ms   191 ms  if-ae-19-2.tcore2.L78-London.as6453.net [80.231.
138.22]
 14   185 ms   186 ms   185 ms  if-ae-15-2.tcore2.LDN-London.as6453.net [80.231.
131.118]
 15   189 ms   189 ms   188 ms  80.231.62.6
 16     *        *        *     Request timed out.
 17   204 ms   204 ms   204 ms  de-fra04a-rc1-ae26-0.aorta.net [84.116.132.18]
 18   213 ms   211 ms   212 ms  ch-otf01b-ra1-et-8-3-0-0.aorta.net [84.116.134.2
29]
 19   209 ms   209 ms   209 ms  84.116.203.254
 20   211 ms   210 ms   207 ms  62.179.24.26
 21     *        *        *     Request timed out.
 22     *      202 ms   201 ms  service.tele.net [194.183.128.94]

Trace complete.
 
DSL Latency & Packet Loss Low Impact 16:46, 09 Apr 2016


Clients may experience packet and increased latency, affecting international sites/ services. Local sites should not be affected.
Our team are aware and urgently working on a fix.
Apologies for the inconvenience caused.


-AH
 
What annoyed me is the fact when I logged a ticket the immediate response in about 5mins was blaming my exchange.........
 
Dont panic folks, AH techies/Support is on top of it.

I logged a detailed report AND referred AH Support to this thread ..............

And here is the reply:

Quote: "Thanks for the mail.

Firstly we would like to apologize for the inconvenience and the experience you having with our connection.
Please note that we have refreshed the connection session and managed to reset the line.
Please reboot the router at your earliest convenience and check with your connection.

Thanks"

Apparently a line reset and connection refresh is all that we need :wtf:

Sadly, I will have to request another round of this miracle cure, as my problem is not resolved :p

High levels of packet loss and latency is indeed the recipe for "Pure Internet Joy"
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X