Afrihost New Network Feedback

Status
Not open for further replies.
AfriMan said:
I think the Critical Care team are really working super hard to improve your experience. They are standing by for the results from your tests and will continue to work with you. The results you've posted here aren't consistent with what we're seeing in general on the network and we want to iron out all the possible variables so that any clients using the same configuration can also benefit.
Click to expand...

Sorry for the late reply, just got home now.

I am just frustrated, I really appreciate the CC team helping me out, it just seems like nothing is coming from it.

But as soon as I have an off day again, I will run more tests for the CC team
 
MDE said:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms 192.168.1.2
2 11 ms 18 ms 10 ms 169-0-24-1.ip.afrihost.co.za [169.0.24.1]
3 148 ms 298 ms 98 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 14 ms 16 ms 15 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 12 ms 12 ms 12 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 28 ms 13 ms 13 ms 41.164.52.40
7 34 ms 33 ms 32 ms 172.18.1.162
8 33 ms 33 ms 34 ms 72.14.194.206
9 35 ms 35 ms 42 ms 72.14.239.117
10 35 ms 49 ms 34 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
Click to expand...

Hhmm, some funky results there.
Can you ping 169.1.5.105 please?
 
Emissary_Of_Pain said:
Sorry for the late reply, just got home now.

I am just frustrated, I really appreciate the CC team helping me out, it just seems like nothing is coming from it.

But as soon as I have an off day again, I will run more tests for the CC team
Click to expand...

You're in good hands with those guys, they're honestly the best at what they do.
 
AfriGuy said:
Hhmm, some funky results there.
Can you ping 169.1.5.105 please?
Click to expand...

C:\Users\Administrator>ping 169.1.5.105

Pinging 169.1.5.105 with 32 bytes of data:
Reply from 169.1.5.105: bytes=32 time=129ms TTL=58
Reply from 169.1.5.105: bytes=32 time=81ms TTL=58
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=14ms TTL=58

Another one
Pinging 169.1.5.105 with 32 bytes of data:
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=13ms TTL=58
Reply from 169.1.5.105: bytes=32 time=250ms TTL=58

C:\Users\Administrator>ping 169.1.5.105

Pinging 169.1.5.105 with 32 bytes of data:
Reply from 169.1.5.105: bytes=32 time=245ms TTL=58
Reply from 169.1.5.105: bytes=32 time=139ms TTL=58
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=14ms TTL=58
 
Last edited:
AfriGuy said:
You're in good hands with those guys, they're honestly the best at what they do.
Click to expand...

Thanks very much.

I won't be on this thread anymore due to some correspondence I received but if I need your help I will drop you a PM if that is ok with you ?

Will also be dealing with the CC team directly as instructed.


Hope you have a great night and thanks once again for all the help you have given me.



Just some extra information, last night I twitched 100% no buffering on source all night and dota 2 pings were constantly under 30ms. This is the AH I know.
 
MDE said:
C:\Users\Administrator>ping 169.1.5.105

Pinging 169.1.5.105 with 32 bytes of data:
Reply from 169.1.5.105: bytes=32 time=129ms TTL=58
Reply from 169.1.5.105: bytes=32 time=81ms TTL=58
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=14ms TTL=58

Another one
Pinging 169.1.5.105 with 32 bytes of data:
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=13ms TTL=58
Reply from 169.1.5.105: bytes=32 time=250ms TTL=58

C:\Users\Administrator>ping 169.1.5.105

Pinging 169.1.5.105 with 32 bytes of data:
Reply from 169.1.5.105: bytes=32 time=245ms TTL=58
Reply from 169.1.5.105: bytes=32 time=139ms TTL=58
Reply from 169.1.5.105: bytes=32 time=12ms TTL=58
Reply from 169.1.5.105: bytes=32 time=14ms TTL=58
Click to expand...

Interesting. I've pasted my final results below.
Can you ping bras.afrihost.com please?

Also - do you have DNS automatically assigned?

Code: 
--- 169.1.5.105 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.958/23.143/33.189/4.973 ms
 
Emissary_Of_Pain said:
Thanks very much.

I won't be on this thread anymore due to some correspondence I received but if I need your help I will drop you a PM if that is ok with you ?

Will also be dealing with the CC team directly as instructed.


Hope you have a great night and thanks once again for all the help you have given me.



Just some extra information, last night I twitched 100% no buffering on source all night and dota 2 pings were constantly under 30ms. This is the AH I know.
Click to expand...

You're welcome to post here - but you definitely need to keep a good feedback loop going with the Critical Care guys :)
 
AfriGuy said:
Interesting. I've pasted my final results below.
Can you ping bras.afrihost.com please?

Also - do you have DNS automatically assigned?

Code: 
--- 169.1.5.105 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.958/23.143/33.189/4.973 ms
Click to expand...
C:\Users\Administrator>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),

Yes DNS is auto assigned.
 
MDE said:
C:\Users\Administrator>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),

Yes DNS is auto assigned.
Click to expand...

That's weird.
What's the experience like on another ISP?

Maybe try setting your DNS as follows, this will guarantee DNS servers in CPT:

169.1.2.1
169.1.2.2
 
AfriGuy said:
That's weird.
What's the experience like on another ISP?

Maybe try setting your DNS as follows, this will guarantee DNS servers in CPT:

169.1.2.1
169.1.2.2
Click to expand...
Via MWEB
PING bras.afrihost.com (155.239.255.250) 56(84) bytes of data.
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=1 ttl=63 time=15.2 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=2 ttl=63 time=14.9 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=3 ttl=63 time=14.8 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=4 ttl=63 time=15.3 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=5 ttl=63 time=15.1 ms

--- bras.afrihost.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 14.857/15.115/15.389/0.190 ms

Those IPs you suggested are already my DNS servers.
 
MDE said:
Via MWEB
PING bras.afrihost.com (155.239.255.250) 56(84) bytes of data.
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=1 ttl=63 time=15.2 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=2 ttl=63 time=14.9 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=3 ttl=63 time=14.8 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=4 ttl=63 time=15.3 ms
64 bytes from bras.afrihost.com (155.239.255.250): icmp_seq=5 ttl=63 time=15.1 ms

--- bras.afrihost.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 14.857/15.115/15.389/0.190 ms

Those IPs you suggested are already my DNS servers.
Click to expand...

Coolios. So we can rule out any exchange/ routing weirdness here.
Drop me a PM with your DSL username and I can take a look at a few things from my end.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X