-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is the ultimate French toast topping?
Afrihost New Network Feedback
- Thread starter AfriMan
- Start date
- Status
HEEEEEEELP!!!! 
ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
HEEEEEEELP!!!!
ping bras.afrihost.com
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Odd.
Can you ping anything else?
ping www.google.co.za
Pinging www.google.co.za [197.80.128.25] with 32 bytes of data:
Reply from 197.80.128.25: bytes=32 time=120ms TTL=54
Reply from 197.80.128.25: bytes=32 time=132ms TTL=54
Reply from 197.80.128.25: bytes=32 time=117ms TTL=54
Reply from 197.80.128.25: bytes=32 time=109ms TTL=54
Ping statistics for 197.80.128.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 132ms, Average = 119ms
Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=27ms TTL=59
Reply from 169.1.1.1: bytes=32 time=23ms TTL=59
Reply from 169.1.1.1: bytes=32 time=32ms TTL=59
Reply from 169.1.1.1: bytes=32 time=16ms TTL=59
Ping statistics for 169.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 32ms, Average = 24ms
ping www.google.co.za
Pinging www.google.co.za [197.80.128.25] with 32 bytes of data:
Reply from 197.80.128.25: bytes=32 time=216ms TTL=54
Reply from 197.80.128.25: bytes=32 time=18ms TTL=54
Reply from 197.80.128.25: bytes=32 time=28ms TTL=54
Reply from 197.80.128.25: bytes=32 time=18ms TTL=54
Ping statistics for 197.80.128.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 216ms, Average = 70ms
Johnatan56
Honorary Master
Are you on WiFi or Ethernet? If you are on WiFi, can you try this test again using an Ethernet cable?
but
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Negative - ethernet.
I'm quite stumped here.
Can you ping over 50 requests to 169.1.1.1? No idea why the latency is jumping around so much.
Speeds all over the place today
Last Result:
Download Speed: 8681 kbps (1085.1 KB/sec transfer rate)
Upload Speed: 803 kbps (100.4 KB/sec transfer rate)
Latency: 378 ms
11/13/2015, 4:26:58 PM
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms 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 = 8ms, Maximum = 9ms, Average = 8ms
Last Result:
Download Speed: 3631 kbps (453.9 KB/sec transfer rate)
Upload Speed: 298 kbps (37.3 KB/sec transfer rate)
Latency: 228 ms
11/13/2015, 4:29:44 PM
Latency is really high on speed test.
Last Result:
Download Speed: 8681 kbps (1085.1 KB/sec transfer rate)
Upload Speed: 803 kbps (100.4 KB/sec transfer rate)
Latency: 378 ms
11/13/2015, 4:26:58 PM
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms 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 = 8ms, Maximum = 9ms, Average = 8ms
Last Result:
Download Speed: 3631 kbps (453.9 KB/sec transfer rate)
Upload Speed: 298 kbps (37.3 KB/sec transfer rate)
Latency: 228 ms
11/13/2015, 4:29:44 PM
Latency is really high on speed test.
Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=27ms TTL=59
Reply from 169.1.1.1: bytes=32 time=40ms TTL=59
Reply from 169.1.1.1: bytes=32 time=32ms TTL=59
Reply from 169.1.1.1: bytes=32 time=91ms TTL=59
Reply from 169.1.1.1: bytes=32 time=10ms TTL=59
Reply from 169.1.1.1: bytes=32 time=13ms TTL=59
Reply from 169.1.1.1: bytes=32 time=20ms TTL=59
Reply from 169.1.1.1: bytes=32 time=18ms TTL=59
Reply from 169.1.1.1: bytes=32 time=60ms TTL=59
Reply from 169.1.1.1: bytes=32 time=13ms TTL=59
Reply from 169.1.1.1: bytes=32 time=80ms TTL=59
Reply from 169.1.1.1: bytes=32 time=25ms TTL=59
Reply from 169.1.1.1: bytes=32 time=22ms TTL=59
Reply from 169.1.1.1: bytes=32 time=34ms TTL=59
Reply from 169.1.1.1: bytes=32 time=35ms TTL=59
Reply from 169.1.1.1: bytes=32 time=18ms TTL=59
Reply from 169.1.1.1: bytes=32 time=24ms TTL=59
Reply from 169.1.1.1: bytes=32 time=42ms TTL=59
Reply from 169.1.1.1: bytes=32 time=38ms TTL=59
Reply from 169.1.1.1: bytes=32 time=45ms TTL=59
Reply from 169.1.1.1: bytes=32 time=45ms TTL=59
Reply from 169.1.1.1: bytes=32 time=37ms TTL=59
Reply from 169.1.1.1: bytes=32 time=17ms TTL=59
Reply from 169.1.1.1: bytes=32 time=41ms TTL=59
Reply from 169.1.1.1: bytes=32 time=33ms TTL=59
Reply from 169.1.1.1: bytes=32 time=37ms TTL=59
Reply from 169.1.1.1: bytes=32 time=43ms TTL=59
Reply from 169.1.1.1: bytes=32 time=37ms TTL=59
Reply from 169.1.1.1: bytes=32 time=41ms TTL=59
Reply from 169.1.1.1: bytes=32 time=65ms TTL=59
Reply from 169.1.1.1: bytes=32 time=30ms TTL=59
Reply from 169.1.1.1: bytes=32 time=39ms TTL=59
Reply from 169.1.1.1: bytes=32 time=74ms TTL=59
Reply from 169.1.1.1: bytes=32 time=82ms TTL=59
Reply from 169.1.1.1: bytes=32 time=41ms TTL=59
Reply from 169.1.1.1: bytes=32 time=43ms TTL=59
Reply from 169.1.1.1: bytes=32 time=36ms TTL=59
Reply from 169.1.1.1: bytes=32 time=55ms TTL=59
Reply from 169.1.1.1: bytes=32 time=44ms TTL=59
Reply from 169.1.1.1: bytes=32 time=58ms TTL=59
Reply from 169.1.1.1: bytes=32 time=54ms TTL=59
Reply from 169.1.1.1: bytes=32 time=37ms TTL=59
Reply from 169.1.1.1: bytes=32 time=34ms TTL=59
Reply from 169.1.1.1: bytes=32 time=47ms TTL=59
Reply from 169.1.1.1: bytes=32 time=40ms TTL=59
Reply from 169.1.1.1: bytes=32 time=53ms TTL=59
Reply from 169.1.1.1: bytes=32 time=36ms TTL=59
Reply from 169.1.1.1: bytes=32 time=29ms TTL=59
Reply from 169.1.1.1: bytes=32 time=36ms TTL=59
Reply from 169.1.1.1: bytes=32 time=39ms TTL=59
Ping statistics for 169.1.1.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 91ms, Average = 39ms
Igor III
Well-Known Member
- Joined
- Oct 5, 2015
- Messages
- 222
- Reaction score
- 12
*sighs*
Seeing that I was still having a hard time on my AH account, I eventually got a WA back up account (also capped) and switched over to WA last week Thursday, just to make sure that the latency I am getting is not related to my hardware and/or Telkom DSL line (something I have been having a hard time with to get the AH folk to accept).
Needless to say, for the past week I have been experiencing pure internet joy - albeit not via AH, but with WA. Torrents and gaming was bliss!
As the AH CC team are involved with my problem on the AH network, I decided to take the plunge and switch from my WA account to AH for this weekend. LOL, hardly on the AH network and gaming is an absolute nightmare.
I have to be brutally honest here, it is starting to be extremely difficult for me to remain with AH ......... not only due to the latency problem, but also when I consider the "latest" great news from AH. It would appear that if you are a client that have a capped account under 100GB/month, they don't care about your business anymore, as the midnight to 06:00 am deal does not apply to you
For the record.....WA caters for the lower bandwidth clients, via giving them less free data during midnight and 06:00 am than the big users. Which seems fair, as everyone is getting a piece of the "free" pie.
Please tell me what tests you still want me to run, as I am slowly getting to the end of my patience with my AH latency problem. I have thus far ran tests and passed results over ad nauseum and am yet to see anything positive from the AH guys (other than the "please run the following tests for us")
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Igor III>ping 95.172.91.23 -t
Pinging 95.172.91.23 with 32 bytes of data:
~ snip
Ping statistics for 95.172.91.23:
Packets: Sent = 227, Received = 227, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 3352ms, Average = 479ms
Control-C
^C
C:\Users\Igor III>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Igor III>ping bras.afrihost.com -t
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
~ snip
Ping statistics for 155.239.255.250:
Packets: Sent = 210, Received = 209, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 37ms, Average = 10ms
Control-C
^C
C:\Users\Igor III>
Seeing that I was still having a hard time on my AH account, I eventually got a WA back up account (also capped) and switched over to WA last week Thursday, just to make sure that the latency I am getting is not related to my hardware and/or Telkom DSL line (something I have been having a hard time with to get the AH folk to accept).
Needless to say, for the past week I have been experiencing pure internet joy - albeit not via AH, but with WA. Torrents and gaming was bliss!
As the AH CC team are involved with my problem on the AH network, I decided to take the plunge and switch from my WA account to AH for this weekend. LOL, hardly on the AH network and gaming is an absolute nightmare.
I have to be brutally honest here, it is starting to be extremely difficult for me to remain with AH ......... not only due to the latency problem, but also when I consider the "latest" great news from AH. It would appear that if you are a client that have a capped account under 100GB/month, they don't care about your business anymore, as the midnight to 06:00 am deal does not apply to you
For the record.....WA caters for the lower bandwidth clients, via giving them less free data during midnight and 06:00 am than the big users. Which seems fair, as everyone is getting a piece of the "free" pie.Please tell me what tests you still want me to run, as I am slowly getting to the end of my patience with my AH latency problem. I have thus far ran tests and passed results over ad nauseum and am yet to see anything positive from the AH guys (other than the "please run the following tests for us")
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Igor III>ping 95.172.91.23 -t
Pinging 95.172.91.23 with 32 bytes of data:
~ snip
Ping statistics for 95.172.91.23:
Packets: Sent = 227, Received = 227, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 3352ms, Average = 479ms
Control-C
^C
C:\Users\Igor III>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Igor III>ping bras.afrihost.com -t
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
~ snip
Ping statistics for 155.239.255.250:
Packets: Sent = 210, Received = 209, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 37ms, Average = 10ms
Control-C
^C
C:\Users\Igor III>
Very up and down
What's the experience like on another ISP?
I dont have another account to swop to. Too faithful I fear...
*sighs*
Seeing that I was still having a hard time on my AH account, I eventually got a WA back up account (also capped) and switched over to WA last week Thursday, just to make sure that the latency I am getting is not related to my hardware and/or Telkom DSL line (something I have been having a hard time with to get the AH folk to accept).
Needless to say, for the past week I have been experiencing pure internet joy - albeit not via AH, but with WA. Torrents and gaming was bliss!
As the AH CC team are involved with my problem on the AH network, I decided to take the plunge and switch from my WA account to AH for this weekend. LOL, hardly on the AH network and gaming is an absolute nightmare.
I have to be brutally honest here, it is starting to be extremely difficult for me to remain with AH ......... not only due to the latency problem, but also when I consider the "latest" great news from AH. It would appear that if you are a client that have a capped account under 100GB/month, they don't care about your business anymore, as the midnight to 06:00 am deal does not apply to you
Please tell me what tests you still want me to run, as I am slowly getting to the end of my patience with my AH latency problem. I have thus far ran tests and passed results over ad nauseum and am yet to see anything positive from the AH guys (other than the "please run the following tests for us")
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Igor III>ping 95.172.91.23 -t
Pinging 95.172.91.23 with 32 bytes of data:
~ snip
Ping statistics for 95.172.91.23:
Packets: Sent = 227, Received = 227, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 3352ms, Average = 479ms
Control-C
^C
C:\Users\Igor III>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Igor III>ping bras.afrihost.com -t
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
~ snip
Ping statistics for 155.239.255.250:
Packets: Sent = 210, Received = 209, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 37ms, Average = 10ms
Control-C
^C
C:\Users\Igor III>
Very sorry to hear about the issues here
Latency is all over the place here - have you been in touch with our Critical Care team?
Any idea why my latency is so bad?
Seems to be a general theme. Also struggling my side. East Rand area.
Igor III
Well-Known Member
- Joined
- Oct 5, 2015
- Messages
- 222
- Reaction score
- 12
Very sorry to hear about the issues here
Latency is all over the place here - have you been in touch with our Critical Care team?
Yep - I passed them similar test results last week before my switch to WA (showing rampant latency on the AH account) and after the switch ran exactly the same tests on my WA account and passed the results on to the CC team as well (this time reflecting a near perfect connection).
I was told that the results would be passed on to the AH network guys for review ............ and that is kinda where it died off
A day or two ago, CC contacted me and asked about my connection - I told them it was awesome, albeit on the WA account
and that I am somewhat reluctant to switch back to my AH account, as my gaming was Ace and torrents were flying Anyways, being comitted to resolving the problem, I did commit to switch back to AH and run some tests ....... the results you saw in my previous post (I also passed it on to the CC folk, as the ticket is still open).
- Status