Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Hummercellc said:
No, international latency still terrible at night.
MWEB network intermittently unreachable, Facebook videos buffer constantly, the only constant seems to be YouTube. Even Microsoft updates have been nonexistent these past few days.
Click to expand...

Your issue is not related to IPC capacity. :( Please continue working with our Critical Care Team.
 
wingnut771 said:
Have your problems gone away?
Click to expand...

I guess not:

Code: 
C:\Windows\System32>ping -n 100 mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=48ms TTL=118
Reply from 196.2.63.110: bytes=32 time=53ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=61ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=59ms TTL=118
Reply from 196.2.63.110: bytes=32 time=91ms TTL=118
Reply from 196.2.63.110: bytes=32 time=53ms TTL=118
Reply from 196.2.63.110: bytes=32 time=68ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=78ms TTL=118
Reply from 196.2.63.110: bytes=32 time=87ms TTL=118
Reply from 196.2.63.110: bytes=32 time=89ms TTL=118
Reply from 196.2.63.110: bytes=32 time=100ms TTL=118
Reply from 196.2.63.110: bytes=32 time=79ms TTL=118
Reply from 196.2.63.110: bytes=32 time=81ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=93ms TTL=118
Reply from 196.2.63.110: bytes=32 time=101ms TTL=118
Reply from 196.2.63.110: bytes=32 time=98ms TTL=118
Reply from 196.2.63.110: bytes=32 time=72ms TTL=118
Reply from 196.2.63.110: bytes=32 time=70ms TTL=118
Reply from 196.2.63.110: bytes=32 time=96ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=102ms TTL=118
Reply from 196.2.63.110: bytes=32 time=82ms TTL=118
Reply from 196.2.63.110: bytes=32 time=103ms TTL=118
Reply from 196.2.63.110: bytes=32 time=92ms TTL=118
Reply from 196.2.63.110: bytes=32 time=110ms TTL=118
Reply from 196.2.63.110: bytes=32 time=83ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=89ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=51ms TTL=118
Reply from 196.2.63.110: bytes=32 time=66ms TTL=118
Reply from 196.2.63.110: bytes=32 time=89ms TTL=118
Request timed out.
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=48ms TTL=118
Reply from 196.2.63.110: bytes=32 time=84ms TTL=118
Reply from 196.2.63.110: bytes=32 time=55ms TTL=118
Reply from 196.2.63.110: bytes=32 time=109ms TTL=118
Reply from 196.2.63.110: bytes=32 time=81ms TTL=118
Reply from 196.2.63.110: bytes=32 time=102ms TTL=118
Reply from 196.2.63.110: bytes=32 time=130ms TTL=118
Reply from 196.2.63.110: bytes=32 time=145ms TTL=118
Reply from 196.2.63.110: bytes=32 time=144ms TTL=118
Reply from 196.2.63.110: bytes=32 time=160ms TTL=118
Reply from 196.2.63.110: bytes=32 time=111ms TTL=118
Reply from 196.2.63.110: bytes=32 time=141ms TTL=118
Reply from 196.2.63.110: bytes=32 time=108ms TTL=118
Reply from 196.2.63.110: bytes=32 time=942ms TTL=118
Reply from 196.2.63.110: bytes=32 time=102ms TTL=118
Reply from 196.2.63.110: bytes=32 time=121ms TTL=118
Reply from 196.2.63.110: bytes=32 time=136ms TTL=118
Reply from 196.2.63.110: bytes=32 time=111ms TTL=118
Reply from 196.2.63.110: bytes=32 time=120ms TTL=118
Reply from 196.2.63.110: bytes=32 time=110ms TTL=118
Reply from 196.2.63.110: bytes=32 time=128ms TTL=118
Reply from 196.2.63.110: bytes=32 time=100ms TTL=118
Reply from 196.2.63.110: bytes=32 time=109ms TTL=118
Reply from 196.2.63.110: bytes=32 time=109ms TTL=118
Reply from 196.2.63.110: bytes=32 time=938ms TTL=118
Reply from 196.2.63.110: bytes=32 time=147ms TTL=118
Reply from 196.2.63.110: bytes=32 time=136ms TTL=118
Reply from 196.2.63.110: bytes=32 time=106ms TTL=118
Reply from 196.2.63.110: bytes=32 time=117ms TTL=118
Reply from 196.2.63.110: bytes=32 time=119ms TTL=118
Reply from 196.2.63.110: bytes=32 time=103ms TTL=118
Reply from 196.2.63.110: bytes=32 time=94ms TTL=118
Reply from 196.2.63.110: bytes=32 time=66ms TTL=118
Reply from 196.2.63.110: bytes=32 time=113ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=821ms TTL=118
Reply from 196.2.63.110: bytes=32 time=65ms TTL=118
Reply from 196.2.63.110: bytes=32 time=86ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=76ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118
Reply from 196.2.63.110: bytes=32 time=48ms TTL=118
Reply from 196.2.63.110: bytes=32 time=76ms TTL=118
Reply from 196.2.63.110: bytes=32 time=83ms TTL=118
Reply from 196.2.63.110: bytes=32 time=58ms TTL=118
Reply from 196.2.63.110: bytes=32 time=789ms TTL=118
Reply from 196.2.63.110: bytes=32 time=63ms TTL=118
Reply from 196.2.63.110: bytes=32 time=96ms TTL=118
Reply from 196.2.63.110: bytes=32 time=95ms TTL=118
Reply from 196.2.63.110: bytes=32 time=50ms TTL=118
Reply from 196.2.63.110: bytes=32 time=48ms TTL=118
Reply from 196.2.63.110: bytes=32 time=47ms TTL=118

Ping statistics for 196.2.63.110:
    Packets: Sent = 100, Received = 94, Lost = 6 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 942ms, Average = 117ms
 
Code: 
C:\Windows\System32>ping -n 100 bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=17ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=21ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=21ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=15ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=14ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64
Reply from 155.239.255.250: bytes=32 time=12ms TTL=64
Reply from 155.239.255.250: bytes=32 time=13ms TTL=64

Ping statistics for 155.239.255.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 21ms, Average = 13ms
 
AfriFella said:
Your issue is not related to IPC capacity. :( Please continue working with our Critical Care Team.
Click to expand...
How? My ticket was closed, and critical care in all honesty have done sweet nothing. They did apologise numerous times, which I guess fixes everything. I am not the only one having constant issues, look back any you will see many complaints of the exact same things over and over again. PS my ticket was closed due to a lack of feedback from myself. Like that makes sense? is critical care not there to supply me with feedback? Any who, critical care are a hopeless bunch. Got tired of the back and forth, complete waste of my time.
 
With an IS account, pings are way more consistant, but, clearly there is an issue with mweb :sick:

Code: 
C:\Windows\System32>ping -n 100 mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=45ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=45ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=890ms TTL=115
Reply from 196.2.63.110: bytes=32 time=61ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=752ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=628ms TTL=115
Reply from 196.2.63.110: bytes=32 time=42ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=549ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=45ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Request timed out.
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=49ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=54ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Request timed out.
Reply from 196.2.63.110: bytes=32 time=45ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Request timed out.
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=48ms TTL=115
Reply from 196.2.63.110: bytes=32 time=48ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Request timed out.
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Request timed out.
Reply from 196.2.63.110: bytes=32 time=47ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=46ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=163ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Request timed out.
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=954ms TTL=115
Reply from 196.2.63.110: bytes=32 time=93ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=43ms TTL=115
Reply from 196.2.63.110: bytes=32 time=44ms TTL=115

Ping statistics for 196.2.63.110:
    Packets: Sent = 100, Received = 94, Lost = 6 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 954ms, Average = 83ms
 
Some tests:

Pinging bbc.co.uk [212.58.244.22] with 32 bytes of data:
Reply from 212.58.244.22: bytes=32 time=203ms TTL=40
Reply from 212.58.244.22: bytes=32 time=211ms TTL=40
Reply from 212.58.244.22: bytes=32 time=201ms TTL=40
Reply from 212.58.244.22: bytes=32 time=218ms TTL=41

Ping statistics for 212.58.244.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 218ms, Average = 208ms

Pinging instagram.com [52.6.199.17] with 32 bytes of data:
Reply from 52.6.199.17: bytes=32 time=279ms TTL=35
Reply from 52.6.199.17: bytes=32 time=270ms TTL=35
Reply from 52.6.199.17: bytes=32 time=272ms TTL=35
Reply from 52.6.199.17: bytes=32 time=272ms TTL=35

Ping statistics for 52.6.199.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 270ms, Maximum = 279ms, Average = 273ms


Pinging facebook.com [173.252.74.68] with 32 bytes of data:
Reply from 173.252.74.68: bytes=32 time=337ms TTL=64
Reply from 173.252.74.68: bytes=32 time=350ms TTL=64
Reply from 173.252.74.68: bytes=32 time=333ms TTL=64
Reply from 173.252.74.68: bytes=32 time=340ms TTL=64

Ping statistics for 173.252.74.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 350ms, Average = 340ms

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms 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 = 18ms, Maximum = 23ms, Average = 20ms
 
Currently on my MWEB account as Afrihost is completely useless tonight. Can not even Skype to the UK. International is completely borked.
 
trace route:

Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms myrouter.Home [192.168.1.1]
2 * * * Request timed out.
3 24 ms 36 ms 28 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 20 ms 20 ms 19 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 23 ms 21 ms 28 ms 41.162.84.192
6 30 ms 32 ms 29 ms 172.18.1.162
7 28 ms 31 ms 30 ms cloudflare.ixp.joburg [196.46.25.198]
8 41 ms 29 ms 42 ms 104.20.30.244

Trace complete.
 
moedawood said:
Some tests:

Pinging bbc.co.uk [212.58.244.22] with 32 bytes of data:
Reply from 212.58.244.22: bytes=32 time=203ms TTL=40
Reply from 212.58.244.22: bytes=32 time=211ms TTL=40
Reply from 212.58.244.22: bytes=32 time=201ms TTL=40
Reply from 212.58.244.22: bytes=32 time=218ms TTL=41

Ping statistics for 212.58.244.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 218ms, Average = 208ms

Pinging instagram.com [52.6.199.17] with 32 bytes of data:
Reply from 52.6.199.17: bytes=32 time=279ms TTL=35
Reply from 52.6.199.17: bytes=32 time=270ms TTL=35
Reply from 52.6.199.17: bytes=32 time=272ms TTL=35
Reply from 52.6.199.17: bytes=32 time=272ms TTL=35

Ping statistics for 52.6.199.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 270ms, Maximum = 279ms, Average = 273ms


Pinging facebook.com [173.252.74.68] with 32 bytes of data:
Reply from 173.252.74.68: bytes=32 time=337ms TTL=64
Reply from 173.252.74.68: bytes=32 time=350ms TTL=64
Reply from 173.252.74.68: bytes=32 time=333ms TTL=64
Reply from 173.252.74.68: bytes=32 time=340ms TTL=64

Ping statistics for 173.252.74.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 350ms, Average = 340ms

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms 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 = 18ms, Maximum = 23ms, Average = 20ms
Click to expand...

Where in the country are you?
 
moedawood said:
Durban, Why?
Click to expand...

geographic location will affect your ping a bit, here's mine, in which case yours looks perfectly normal:

Code: 
C:\Windows\System32>ping facebook.com

Pinging facebook.com [69.171.230.68] with 32 bytes of data:
Reply from 69.171.230.68: bytes=32 time=331ms TTL=65
Reply from 69.171.230.68: bytes=32 time=330ms TTL=65
Reply from 69.171.230.68: bytes=32 time=329ms TTL=65
Reply from 69.171.230.68: bytes=32 time=331ms TTL=65

Ping statistics for 69.171.230.68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 329ms, Maximum = 331ms, Average = 330ms

C:\Windows\System32>ping instagram.com

Pinging instagram.com [52.22.151.190] with 32 bytes of data:
Reply from 52.22.151.190: bytes=32 time=258ms TTL=35
Reply from 52.22.151.190: bytes=32 time=256ms TTL=35
Reply from 52.22.151.190: bytes=32 time=257ms TTL=35
Reply from 52.22.151.190: bytes=32 time=256ms TTL=35

Ping statistics for 52.22.151.190:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 256ms, Maximum = 258ms, Average = 256ms

C:\Windows\System32>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.23] with 32 bytes of data:
Reply from 212.58.244.23: bytes=32 time=188ms TTL=41
Reply from 212.58.244.23: bytes=32 time=189ms TTL=41
Reply from 212.58.244.23: bytes=32 time=188ms TTL=41
Reply from 212.58.244.23: bytes=32 time=189ms TTL=41

Ping statistics for 212.58.244.23:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 188ms, Maximum = 189ms, Average = 188ms
 
Evening guys

I'll take a closer look at everyones results in detail tomorrow morning, very sorry that the KZN issue seems to be back.
For those that are affected, please complete a standard set of tests though. I'll pass on what's been posted already to our Network team.

AfriGuy said:
Area/ suburb
Account type
Local traceroute
Traceroute to affected site/ service
Ping to bras.afrihost.com
List any other affected services
DNS being used

Thanks so much guys. I know these constant tests are a pain, but it's the best way to FW this kind of info through for something actionable on our end.
Click to expand...
 
AfriGuy said:
Evening guys

I'll take a closer look at everyones results in detail tomorrow morning, very sorry that the KZN issue seems to be back.
For those that are affected, please complete a standard set of tests though. I'll pass on what's been posted already to our Network team.
Click to expand...
To be blunt, it was never fixed. This has been ongoing for over a month now. Really disappointed in Afrihost. Terrible, there are so many problems where do we start? Almost all traffic has some sort of issue.
 
NewBiks said:
Thank you for posting

I've never once had sub 200ms response times when connecting to a Twitch server.
Could you please test again around 8PM, thank you.
Click to expand...

A bit late, was catching up on the Apple event with their new phone and wide range of adapters :p

Here are my results from this evening, same test standard, account and region tested. This test was done over WiFi, whereas earlier I tested over ethernet.
I tested with this stream https://www.twitch.tv/proleaguecsgo

http://imgur.com/a/C9yoX

Stream pulled from 52.223.194.225.

Code: 
sudo mtr --report 52.223.194.225
HOST: Jeffs-Macbook.local         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- er-8.ubnt                  0.0%    10    1.3   2.1   1.0  11.0   3.1
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- cpt-up1.ip.adsl.co.za     20.0%    10   18.5  22.2  18.4  41.3   8.0
  4.|-- cpt-up2.ip.adsl.co.za      0.0%    10   19.5  22.0  18.5  38.1   6.2
  5.|-- cpt-net1.ip.adsl.co.za     0.0%    10   18.8  19.3  17.8  21.3   1.1
  6.|-- 41.164.52.40               0.0%    10   18.8  20.4  18.7  24.5   2.1
  7.|-- if-ae-7-0.tcore2.klt-cape  0.0%    10   80.4  71.2  51.0  92.8  13.7
  8.|-- if-ae-2-2.tcore1.klt-cape  0.0%    10  210.7 214.4 208.8 238.2   8.6
  9.|-- if-ae-5-20.tcore2.pv9-lis  0.0%    10  214.6 219.6 197.0 247.4  16.4
 10.|-- if-ae-2-2.tcore1.pv9-lisb  0.0%    10  204.7 205.6 193.0 226.6   8.6
 11.|-- if-ae-1-3.tcore1.sv8-high  0.0%    10  204.3 219.5 202.5 247.2  15.0
 12.|-- if-ae-2-2.tcore2.sv8-high  0.0%    10  200.8 206.1 195.9 218.5   7.1
 13.|-- if-ae-11-2.tcore1.l78-lon 10.0%    10  201.2 201.0 194.1 205.1   3.8
 14.|-- if-ae-17-2.tcore1.ldn-lon  0.0%    10  202.2 203.8 194.4 216.5   6.3
 15.|-- 195.219.83.186             0.0%    10  200.8 207.3 196.8 221.1   7.4
 16.|-- ae-3.r02.londen05.uk.bb.g  0.0%    10  207.0 204.2 190.1 215.8   7.0
 17.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0

Code: 
traceroute to 52.223.194.225 (52.223.194.225), 64 hops max, 52 byte packets
 1  er-8.ubnt (192.168.1.2)  9.270 ms  0.989 ms  0.904 ms
 2  * * *
 3  * cpt-up1.ip.adsl.co.za (169.1.5.105)  19.159 ms  19.482 ms
 4  cpt-up2.ip.adsl.co.za (169.1.5.106)  18.706 ms  18.606 ms  19.017 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  18.413 ms  18.590 ms  17.864 ms
 6  41.164.52.40 (41.164.52.40)  18.765 ms  20.711 ms  77.745 ms
 7  if-ae-7-0.tcore2.klt-cape-town.as6453.net (41.206.165.25)  102.281 ms  66.633 ms  73.648 ms
 8  if-ae-5-30.tcore2.pv9-lisbon.as6453.net (80.231.159.85)  212.351 ms
    if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.129)  211.971 ms
    if-ae-2-2.tcore1.klt-cape-town.as6453.net (41.206.164.253)  219.864 ms
 9  if-ae-5-40.tcore2.pv9-lisbon.as6453.net (80.231.159.89)  214.838 ms
    if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5)  204.203 ms
    if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.129)  215.057 ms
10  if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5)  212.188 ms  219.248 ms  203.438 ms
11  if-ae-1-3.tcore1.sv8-highbridge.as6453.net (80.231.158.30)  220.086 ms  326.816 ms  206.214 ms
12  if-ae-11-2.tcore1.l78-london.as6453.net (80.231.139.42)  193.988 ms
    if-ae-19-2.tcore2.l78-london.as6453.net (80.231.138.22)  203.358 ms
    if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1)  201.799 ms
13  if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130)  296.177 ms
    if-ae-2-2.tcore1.l78-london.as6453.net (80.231.131.2)  213.499 ms
    if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130)  198.441 ms
14  if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130)  198.417 ms  197.691 ms
    195.219.83.186 (195.219.83.186)  303.965 ms
15  ae-3.r02.londen05.uk.bb.gin.ntt.net (129.250.2.119)  237.919 ms  207.503 ms
    195.219.83.186 (195.219.83.186)  219.789 ms
16  ae-3.r02.londen05.uk.bb.gin.ntt.net (129.250.2.119)  222.359 ms  214.738 ms  216.666 ms
17  213.130.47.82 (213.130.47.82)  200.705 ms !X *  252.529 ms !X
 
Hummercellc said:
To be blunt, it was never fixed. This has been ongoing for over a month now. Really disappointed in Afrihost. Terrible, there are so many problems where do we start? Almost all traffic has some sort of issue.
Click to expand...

It was fixed, along with the CloudFlare latency. I'll need to touch base with our team tomorrow for further updates.
As discussed earlier though, you need to continue to communicate with Critical Care - the ticket was closed (automatically) as we received no response from yourself.
 
AfriGuy said:
It was fixed, along with the CloudFlare latency. I'll need to touch base with our team tomorrow for further updates.
As discussed earlier though, you need to continue to communicate with Critical Care - the ticket was closed (automatically) as we received no response from yourself.
Click to expand...
OK next time I will reply with a period just to keep the ticket open while critical care twiddle their thumbs. I was told to await feedback which I never got. Now it is my fault? This entire process and constant denial is really pushing my buttons. It feels like I am the one who is in the wrong and I am the one who is causing the problems. Fix your network please.
 
AfriGuy said:
A bit late, was catching up on the Apple event with their new phone and wide range of adapters

Here are my results from this evening, same test standard, account and region tested. This test was done over WiFi, whereas earlier I tested over ethernet.
I tested with this stream https://www.twitch.tv/proleaguecsgo

http://imgur.com/a/C9yoX

Stream pulled from 52.223.194.225.

Code: 
sudo mtr --report 52.223.194.225
HOST: Jeffs-Macbook.local         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- er-8.ubnt                  0.0%    10    1.3   2.1   1.0  11.0   3.1
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- cpt-up1.ip.adsl.co.za     20.0%    10   18.5  22.2  18.4  41.3   8.0
  4.|-- cpt-up2.ip.adsl.co.za      0.0%    10   19.5  22.0  18.5  38.1   6.2
  5.|-- cpt-net1.ip.adsl.co.za     0.0%    10   18.8  19.3  17.8  21.3   1.1
  6.|-- 41.164.52.40               0.0%    10   18.8  20.4  18.7  24.5   2.1
  7.|-- if-ae-7-0.tcore2.klt-cape  0.0%    10   80.4  71.2  51.0  92.8  13.7
  8.|-- if-ae-2-2.tcore1.klt-cape  0.0%    10  210.7 214.4 208.8 238.2   8.6
  9.|-- if-ae-5-20.tcore2.pv9-lis  0.0%    10  214.6 219.6 197.0 247.4  16.4
 10.|-- if-ae-2-2.tcore1.pv9-lisb  0.0%    10  204.7 205.6 193.0 226.6   8.6
 11.|-- if-ae-1-3.tcore1.sv8-high  0.0%    10  204.3 219.5 202.5 247.2  15.0
 12.|-- if-ae-2-2.tcore2.sv8-high  0.0%    10  200.8 206.1 195.9 218.5   7.1
 13.|-- if-ae-11-2.tcore1.l78-lon 10.0%    10  201.2 201.0 194.1 205.1   3.8
 14.|-- if-ae-17-2.tcore1.ldn-lon  0.0%    10  202.2 203.8 194.4 216.5   6.3
 15.|-- 195.219.83.186             0.0%    10  200.8 207.3 196.8 221.1   7.4
 16.|-- ae-3.r02.londen05.uk.bb.g  0.0%    10  207.0 204.2 190.1 215.8   7.0
 17.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0

Code: 
traceroute to 52.223.194.225 (52.223.194.225), 64 hops max, 52 byte packets
 1  er-8.ubnt (192.168.1.2)  9.270 ms  0.989 ms  0.904 ms
 2  * * *
 3  * cpt-up1.ip.adsl.co.za (169.1.5.105)  19.159 ms  19.482 ms
 4  cpt-up2.ip.adsl.co.za (169.1.5.106)  18.706 ms  18.606 ms  19.017 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  18.413 ms  18.590 ms  17.864 ms
 6  41.164.52.40 (41.164.52.40)  18.765 ms  20.711 ms  77.745 ms
 7  if-ae-7-0.tcore2.klt-cape-town.as6453.net (41.206.165.25)  102.281 ms  66.633 ms  73.648 ms
 8  if-ae-5-30.tcore2.pv9-lisbon.as6453.net (80.231.159.85)  212.351 ms
    if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.129)  211.971 ms
    if-ae-2-2.tcore1.klt-cape-town.as6453.net (41.206.164.253)  219.864 ms
 9  if-ae-5-40.tcore2.pv9-lisbon.as6453.net (80.231.159.89)  214.838 ms
    if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5)  204.203 ms
    if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.129)  215.057 ms
10  if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5)  212.188 ms  219.248 ms  203.438 ms
11  if-ae-1-3.tcore1.sv8-highbridge.as6453.net (80.231.158.30)  220.086 ms  326.816 ms  206.214 ms
12  if-ae-11-2.tcore1.l78-london.as6453.net (80.231.139.42)  193.988 ms
    if-ae-19-2.tcore2.l78-london.as6453.net (80.231.138.22)  203.358 ms
    if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1)  201.799 ms
13  if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130)  296.177 ms
    if-ae-2-2.tcore1.l78-london.as6453.net (80.231.131.2)  213.499 ms
    if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130)  198.441 ms
14  if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130)  198.417 ms  197.691 ms
    195.219.83.186 (195.219.83.186)  303.965 ms
15  ae-3.r02.londen05.uk.bb.gin.ntt.net (129.250.2.119)  237.919 ms  207.503 ms
    195.219.83.186 (195.219.83.186)  219.789 ms
16  ae-3.r02.londen05.uk.bb.gin.ntt.net (129.250.2.119)  222.359 ms  214.738 ms  216.666 ms
17  213.130.47.82 (213.130.47.82)  200.705 ms !X *  252.529 ms !X
Click to expand...
Are all those adapters included in the box with the new iphone? Or do you have to buy them?
 
Holy cow. Afrihost doubled all of my data, not just the normal data. 1.2TB! :o

29494773966_43366ccf0d_b.jpg


Afrihost, you might want to update your Total Data Remaining circle, as it can't fit 1065GB. :p
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X