Afrihost Business Uncapped Feedback

Status
Not open for further replies.
D

D3athR3aver

Active Member
Joined
Mar 9, 2014
Messages
58
juBa said:
Ive also been having extremely high pings to the EUW LoL server since last night. It averages around 450. 4mb business account.

It was 100% in the day and just went mental in the evening. I tested again this morning and its still high. Hopefully they can sort it out soon.

Only reason I got an afrihost business account is because I use to have a capped 10gig account with them and every time my other ISP had lag issues i just changed to the capped afrihost account and it was like magic, no lag, ever. period. Since I moved to the uncapped business account the magic was partially lost.
Click to expand...

I am having the same problem with LoL ping today, where it averages between 450 -800. While this makes the game virtually unplayable, it makes for great last-hitting practice in a custom game :). Really hope this gets sorted out soon.
 
J

juBa

Senior Member
Joined
Nov 24, 2011
Messages
737
D3athR3aver said:
I am having the same problem with LoL ping today, where it averages between 450 -800. While this makes the game virtually unplayable, it makes for great last-hitting practice in a custom game :). Really hope this gets sorted out soon.
Click to expand...

Very frustrating! And the ping always spikes when you're about to go into team battles and then you're left standing there like a nob not doing anything while your team dies. Report galore follows.

Im not sure what it is though, because my browsing is also very slow.
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
juBa said:
Very frustrating! And the ping always spikes when you're about to go into team battles and then you're left standing there like a nob not doing anything while your team dies. Report galore follows.

Im not sure what it is though, because my browsing is also very slow.
Click to expand...

Have you done a trace route? Could be either the account or a line issue :/

Please would you run my second tool in my signature below :)

Z

EDIT: Sorry didnt read that other users were having the same issue :/
 
Last edited:
C

coolfuze

Member
Joined
Apr 22, 2010
Messages
27
This is what I got
Your average ping was 135ms
Your maximum ping was 202ms
:(

I'm in Durban if that helps.
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
coolfuze said:
This is what I got
Your average ping was 135ms
Your maximum ping was 202ms
:(

I'm in Durban if that helps.
Click to expand...

Seems like a line fault then :(

Could you please do the following for me :)

[1] Post a detailed report from my second tool
[2] Try with another ISP to troubleshoot

Z
 
C

coolfuze

Member
Joined
Apr 22, 2010
Messages
27
I turned the router on and off and am getting better results, my luck seems to be limited to buying crap routers that need to be manually turned off and on :p But here are the results none the less.


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 27ms
Your maximum ping was 84ms

Looking at your average ping, your line seems to be running perfectly :)
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=44ms TTL=254
Reply from 105.236.14.1: bytes=32 time=35ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=27ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=27ms TTL=254
Reply from 105.236.14.1: bytes=32 time=40ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=84ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=31ms TTL=254
Reply from 105.236.14.1: bytes=32 time=23ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=49ms TTL=254
Reply from 105.236.14.1: bytes=32 time=29ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=42ms TTL=254
Reply from 105.236.14.1: bytes=32 time=47ms TTL=254
Reply from 105.236.14.1: bytes=32 time=30ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=16ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=28ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 84ms, Average = 27ms
 
2014-06-16 13:26:35,96
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
coolfuze said:
I turned the router on and off and am getting better results, my luck seems to be limited to buying crap routers that need to be manually turned off and on :p But here are the results none the less.


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 27ms
Your maximum ping was 84ms

Looking at your average ping, your line seems to be running perfectly :)
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=44ms TTL=254
Reply from 105.236.14.1: bytes=32 time=35ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=27ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=27ms TTL=254
Reply from 105.236.14.1: bytes=32 time=40ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=84ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=31ms TTL=254
Reply from 105.236.14.1: bytes=32 time=23ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=49ms TTL=254
Reply from 105.236.14.1: bytes=32 time=29ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=42ms TTL=254
Reply from 105.236.14.1: bytes=32 time=47ms TTL=254
Reply from 105.236.14.1: bytes=32 time=30ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=16ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=28ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 84ms, Average = 27ms
 
2014-06-16 13:26:35,96
Click to expand...

Still looks a bit like line issues :/

You sure its the router? It could be that when you rebooted - you recreated your session at the exchange. You dont by any chance have any other routers to test with?

Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Okay! Someone, please! Does anyone have this issue - it seems that ANY mobile device (android/iOS) that I use, while connected to our home network, refuses to play Facebook videos!? This is while using my Afrihost account.

It's the weirdest thing, as on mobile data on the devices, it works fine? Can anyone confirm that this is isolated to me please :)

Not often that I'm the one needing help :D
Z
 
prodigyX

prodigyX

Senior Member
Joined
Mar 10, 2010
Messages
559
Zertop said:
Okay! Someone, please! Does anyone have this issue - it seems that ANY mobile device (android/iOS) that I use, while connected to our home network, refuses to play Facebook videos!? This is while using my Afrihost account.

It's the weirdest thing, as on mobile data on the devices, it works fine? Can anyone confirm that this is isolated to me please :)

Not often that I'm the one needing help :D
Z
Click to expand...

I had that problem a while ago on my Afrihost Business account and the culprit turned out to be UnoTelly :wtf:
 
C

coolfuze

Member
Joined
Apr 22, 2010
Messages
27
Testing on the other router I get this and testing on the afrihost website i get line test failed with both routers

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 20ms
Your maximum ping was 36ms

Looking at your average ping, your line seems to be running perfectly :)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report of First test
Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=36ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 36ms, Average = 20ms
 
2014-06-17  9:12:32,68


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 100ms
Your maximum ping was 163ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report of Second Test
Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=141ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=163ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=51ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=137ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=27ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=142ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=150ms TTL=254
Reply from 105.236.14.1: bytes=32 time=146ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=139ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=158ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=38ms TTL=254
Reply from 105.236.14.1: bytes=32 time=126ms TTL=254
Reply from 105.236.14.1: bytes=32 time=142ms TTL=254
Reply from 105.236.14.1: bytes=32 time=150ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 163ms, Average = 100ms
 
2014-06-17  9:17:35,59


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 107ms
Your maximum ping was 164ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report of third test
Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=103ms TTL=254
Reply from 105.236.14.1: bytes=32 time=138ms TTL=254
Reply from 105.236.14.1: bytes=32 time=138ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=141ms TTL=254
Reply from 105.236.14.1: bytes=32 time=151ms TTL=254
Reply from 105.236.14.1: bytes=32 time=164ms TTL=254
Reply from 105.236.14.1: bytes=32 time=154ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=153ms TTL=254
Reply from 105.236.14.1: bytes=32 time=137ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=75ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=142ms TTL=254
Reply from 105.236.14.1: bytes=32 time=134ms TTL=254
Reply from 105.236.14.1: bytes=32 time=132ms TTL=254
Reply from 105.236.14.1: bytes=32 time=140ms TTL=254
Reply from 105.236.14.1: bytes=32 time=133ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=155ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 164ms, Average = 107ms
 
2014-06-17  9:19:40,97
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
coolfuze said:
Testing on the other router I get this and testing on the afrihost website i get line test failed with both routers

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 20ms
Your maximum ping was 36ms

Looking at your average ping, your line seems to be running perfectly :)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report of First test
Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=36ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 36ms, Average = 20ms
 
2014-06-17  9:12:32,68


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 100ms
Your maximum ping was 163ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report of Second Test
Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=141ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=163ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=51ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=137ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=27ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=142ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=150ms TTL=254
Reply from 105.236.14.1: bytes=32 time=146ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=139ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=158ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=21ms TTL=254
Reply from 105.236.14.1: bytes=32 time=38ms TTL=254
Reply from 105.236.14.1: bytes=32 time=126ms TTL=254
Reply from 105.236.14.1: bytes=32 time=142ms TTL=254
Reply from 105.236.14.1: bytes=32 time=150ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 163ms, Average = 100ms
 
2014-06-17  9:17:35,59


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 107ms
Your maximum ping was 164ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report of third test
Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=103ms TTL=254
Reply from 105.236.14.1: bytes=32 time=138ms TTL=254
Reply from 105.236.14.1: bytes=32 time=138ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=141ms TTL=254
Reply from 105.236.14.1: bytes=32 time=151ms TTL=254
Reply from 105.236.14.1: bytes=32 time=164ms TTL=254
Reply from 105.236.14.1: bytes=32 time=154ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=153ms TTL=254
Reply from 105.236.14.1: bytes=32 time=137ms TTL=254
Reply from 105.236.14.1: bytes=32 time=19ms TTL=254
Reply from 105.236.14.1: bytes=32 time=18ms TTL=254
Reply from 105.236.14.1: bytes=32 time=20ms TTL=254
Reply from 105.236.14.1: bytes=32 time=75ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=142ms TTL=254
Reply from 105.236.14.1: bytes=32 time=134ms TTL=254
Reply from 105.236.14.1: bytes=32 time=132ms TTL=254
Reply from 105.236.14.1: bytes=32 time=140ms TTL=254
Reply from 105.236.14.1: bytes=32 time=133ms TTL=254
Reply from 105.236.14.1: bytes=32 time=149ms TTL=254
Reply from 105.236.14.1: bytes=32 time=148ms TTL=254
Reply from 105.236.14.1: bytes=32 time=155ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 164ms, Average = 107ms
 
2014-06-17  9:19:40,97
Click to expand...

Hey Man!

That first test looks alright?! Last two, not so much :(

Have you checked that all your phones/alarms (if needed) have ADSL filters attached? If those break, they can cause havoc on a line. They will also cause a "Test my Line" to fail.

Z
 
AfriMan

AfriMan

Afrihost Representative
Company Rep
Joined
May 24, 2012
Messages
17,239
D3athR3aver said:
It seems that my network is on the fritz again tonight. Here are the results of my Network Test which I just ran (07:14 PM)

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=461 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=474 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=429 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=429 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=451 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=43 time=752 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=43 time=675 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 7 ms
2 Request timed out *
3 Request timed out *


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms
2 Request timed out *
3 Request timed out *
4 Request timed out *
5 Request timed out *
6 Request timed out *
7 Request timed out *
8 Request timed out *
9 Request timed out *
10 Request timed out *
11 Request timed out *
12 Request timed out *
13 Request timed out *


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 173.194.34.178
Name: www.google.com
Address: 173.194.34.179
Name: www.google.com
Address: 173.194.34.180
Name: www.google.com
Address: 173.194.34.176
Name: www.google.com
Address: 173.194.34.177


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

http://www.speedtest.net/my-result/3561621931 - 2Mbps
Click to expand...

Ping to your router should never be as high 7ms, so that's already something colouring your results.

Your pings are just generally high, and that seems to point to congestion or a line fault. Since you already timing out on the second hop, that would be my guess.

Does this happen on other ISP networks?
 
AfriMan

AfriMan

Afrihost Representative
Company Rep
Joined
May 24, 2012
Messages
17,239
juBa said:
Ive also been having extremely high pings to the EUW LoL server since last night. It averages around 450. 4mb business account.

It was 100% in the day and just went mental in the evening. I tested again this morning and its still high. Hopefully they can sort it out soon.

Only reason I got an afrihost business account is because I use to have a capped 10gig account with them and every time my other ISP had lag issues i just changed to the capped afrihost account and it was like magic, no lag, ever. period. Since I moved to the uncapped business account the magic was partially lost.
Click to expand...

This definitely sucks :(

Have you run any other tests to check for latency on your general connections? If you run our network test app, you should get an idea of latency and ping on your connection.
 
AfriMan

AfriMan

Afrihost Representative
Company Rep
Joined
May 24, 2012
Messages
17,239
Zertop said:
Okay! Someone, please! Does anyone have this issue - it seems that ANY mobile device (android/iOS) that I use, while connected to our home network, refuses to play Facebook videos!? This is while using my Afrihost account.

It's the weirdest thing, as on mobile data on the devices, it works fine? Can anyone confirm that this is isolated to me please :)

Not often that I'm the one needing help :D
Z
Click to expand...

I'm not aware of any issues like this. I was playing videos via FB this weekend over my home WiFi and it seemed pretty normal.

Did the video just never load or did you get an error? Maybe the video wasn't cached locally and took longer to load?
 
C

coolfuze

Member
Joined
Apr 22, 2010
Messages
27
Zertop said:
Hey Man!

That first test looks alright?! Last two, not so much :(

Have you checked that all your phones/alarms (if needed) have ADSL filters attached? If those break, they can cause havoc on a line. They will also cause a "Test my Line" to fail.

Z
Click to expand...

Hey, I've tested my line on a brand new filter, out the box and I still get line failed, also these results.

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 132ms
Your maximum ping was 409ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=269ms TTL=254
Reply from 105.236.14.1: bytes=32 time=320ms TTL=254
Reply from 105.236.14.1: bytes=32 time=409ms TTL=254
Reply from 105.236.14.1: bytes=32 time=267ms TTL=254
Reply from 105.236.14.1: bytes=32 time=174ms TTL=254
Reply from 105.236.14.1: bytes=32 time=229ms TTL=254
Reply from 105.236.14.1: bytes=32 time=81ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=56ms TTL=254
Reply from 105.236.14.1: bytes=32 time=99ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=129ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=123ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=134ms TTL=254
Reply from 105.236.14.1: bytes=32 time=140ms TTL=254
Reply from 105.236.14.1: bytes=32 time=133ms TTL=254
Reply from 105.236.14.1: bytes=32 time=141ms TTL=254
Reply from 105.236.14.1: bytes=32 time=123ms TTL=254
Reply from 105.236.14.1: bytes=32 time=130ms TTL=254
Reply from 105.236.14.1: bytes=32 time=143ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=126ms TTL=254
Reply from 105.236.14.1: bytes=32 time=35ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 409ms, Average = 132ms
 
2014-06-17 10:56:29,31
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
coolfuze said:
Hey, I've tested my line on a brand new filter, out the box and I still get line failed, also these results.

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 132ms
Your maximum ping was 409ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.14.1 with 32 bytes of data:
Reply from 105.236.14.1: bytes=32 time=269ms TTL=254
Reply from 105.236.14.1: bytes=32 time=320ms TTL=254
Reply from 105.236.14.1: bytes=32 time=409ms TTL=254
Reply from 105.236.14.1: bytes=32 time=267ms TTL=254
Reply from 105.236.14.1: bytes=32 time=174ms TTL=254
Reply from 105.236.14.1: bytes=32 time=229ms TTL=254
Reply from 105.236.14.1: bytes=32 time=81ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=56ms TTL=254
Reply from 105.236.14.1: bytes=32 time=99ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=129ms TTL=254
Reply from 105.236.14.1: bytes=32 time=136ms TTL=254
Reply from 105.236.14.1: bytes=32 time=123ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=134ms TTL=254
Reply from 105.236.14.1: bytes=32 time=140ms TTL=254
Reply from 105.236.14.1: bytes=32 time=133ms TTL=254
Reply from 105.236.14.1: bytes=32 time=141ms TTL=254
Reply from 105.236.14.1: bytes=32 time=123ms TTL=254
Reply from 105.236.14.1: bytes=32 time=130ms TTL=254
Reply from 105.236.14.1: bytes=32 time=143ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=121ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=17ms TTL=254
Reply from 105.236.14.1: bytes=32 time=126ms TTL=254
Reply from 105.236.14.1: bytes=32 time=35ms TTL=254

Ping statistics for 105.236.14.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 409ms, Average = 132ms
 
2014-06-17 10:56:29,31
Click to expand...

Yea, doesn't look great :(

How does it perform with another account?

Z
 
Status
Not open for further replies.
Top