Afrihost New Network Feedback - Part 2

[AfriGuy]

It is no about the latency i was running this on my ipad with wifi
it is aboue user get assign to different pop in Cape Town you not answer the question

I don't see a specific question?
If you're asking if there are multiple routers and routes in the region, the answer is yes.

 

[Hummercellc]

I'll query this with our network team, although I'm not aware of any peering issues.
Could just be how the routers communicate with each other.

Afrihost Account

PING afrihost.com (104.20.30.244) from 169.0.XXX.XXX: 56 data bytes
64 bytes from 104.20.30.244: icmp_seq=0 ttl=48 time=190.030 ms
64 bytes from 104.20.30.244: icmp_seq=1 ttl=48 time=189.328 ms
64 bytes from 104.20.30.244: icmp_seq=2 ttl=48 time=188.951 ms
64 bytes from 104.20.30.244: icmp_seq=3 ttl=47 time=188.518 ms
64 bytes from 104.20.30.244: icmp_seq=4 ttl=47 time=188.963 ms
64 bytes from 104.20.30.244: icmp_seq=5 ttl=48 time=188.018 ms
64 bytes from 104.20.30.244: icmp_seq=6 ttl=48 time=189.289 ms
64 bytes from 104.20.30.244: icmp_seq=7 ttl=48 time=189.057 ms
64 bytes from 104.20.30.244: icmp_seq=8 ttl=47 time=189.090 ms
64 bytes from 104.20.30.244: icmp_seq=9 ttl=47 time=188.888 ms

--- afrihost.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 188.018/189.013/190.030/0.497 ms

Mweb Account

PING afrihost.com (104.20.31.244) from 197.81.XXX.XXX: 56 data bytes
64 bytes from 104.20.31.244: icmp_seq=0 ttl=55 time=30.305 ms
64 bytes from 104.20.31.244: icmp_seq=1 ttl=55 time=30.411 ms
64 bytes from 104.20.31.244: icmp_seq=2 ttl=55 time=30.363 ms
64 bytes from 104.20.31.244: icmp_seq=3 ttl=55 time=30.152 ms
64 bytes from 104.20.31.244: icmp_seq=4 ttl=55 time=30.210 ms
64 bytes from 104.20.31.244: icmp_seq=5 ttl=55 time=29.591 ms
64 bytes from 104.20.31.244: icmp_seq=6 ttl=55 time=30.451 ms
64 bytes from 104.20.31.244: icmp_seq=7 ttl=55 time=29.983 ms
64 bytes from 104.20.31.244: icmp_seq=8 ttl=55 time=29.686 ms
64 bytes from 104.20.31.244: icmp_seq=9 ttl=55 time=29.762 ms

--- afrihost.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 29.591/30.091/30.451/0.301 ms

 

[VindicatoR]

How are things looking this morning? Has there been any change?

I have a spare WA account that I was using, I'm at work now and haven't tried it again. Will do so when I get home.

 

[AfriGuy]

Afrihost Account


Mweb Account

Thanks, checking it out with our team.

 

[AfriGuy]

I have a spare WA account that I was using, I'm at work now and haven't tried it again. Will do so when I get home.

Keep us posted

 

[Unhappy1]

Keep us posted

There was certainly an improvement latency wise last night, im not sure about downloads as i was gaming all night.

 

[AfriGuy]

There was certainly an improvement latency wise last night, im not sure about downloads as i was gaming all night.

That's awesome news!! Great to hear we're taking some steps forward here

 

[Icemanbrfc]

That's awesome news!! Great to hear we're taking some steps forward here

I keep thinking today is Wednesday

 

[AfriGuy]

I keep thinking today is Wednesday

Soon™
Patience, young padawan

 

[Icemanbrfc]

Soon™
Patience, young padawan

Im going to change my username to Young Padawan

 

[AfriGuy]

Im going to change my username to Young Padawan

 

[Icemanbrfc]

 

[Icemanbrfc]

Done

 

[AfriGuy]

Done

//uploads.tapatalk-cdn.com/20160906/f3058933ff06437d3022e88ed264889d.jpg

Haha, much win!!

 

[Icemanbrfc]

Haha, much win!!

im off now, meetings are calling

Chat later, have a good one

 

[AfriGuy]

im off now, meetings are calling

Chat later, have a good one

Cheers dude

 

[moedawood]

Did a port reset:

PING bras.afrihost.com (155.239.255.250): 56 data bytes

64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=32.090 ms

64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=23.779 ms

64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=19.289 ms

64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=40.671 ms

64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=61.511 ms

64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=26.616 ms

64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=19.726 ms

64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=19.843 ms

64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=23.628 ms

64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=20.094 ms

64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=21.901 ms

64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=22.400 ms

64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=45.085 ms

64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=19.353 ms

64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=21.568 ms

64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=18.979 ms

64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=44.109 ms

64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=47.755 ms

64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=44.751 ms

64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=44.580 ms

64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=54.421 ms

64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=45.453 ms

64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=46.875 ms

64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=25.164 ms

64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=19.263 ms

64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=130.386 ms

64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=20.497 ms

64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=134.981 ms


--- 155.239.255.250 ping statistics ---
28 packets transmitted, 28 received, 0.00% packet loss
round-trip min / avg / max = 18.979 / 39.099 / 134.981 ms

I logged a fault with Telkom. Should've done that right?

 

[AfriGuy]

Did a port reset:

-snip

--- 155.239.255.250 ping statistics ---
28 packets transmitted, 28 received, 0.00% packet loss
round-trip min / avg / max = 18.979 / 39.099 / 134.981 ms

I logged a fault with Telkom. Should've done that right? ��

Seems to have helped a bit, but latency still looks to be spiking up.
As the experience is the same regardless of ISP, having the fault logged was the right move

 

[NewBiks]

Even YT is crawling now

http://puu.sh/r1OEy/17c571cb5b.png

I'm in talks with CC but this is starting to get bad.

 

[AfriGuy]

Even YT is crawling now

http://puu.sh/r1OEy/17c571cb5b.png

I'm in talks with CC but this is starting to get bad.

Not looking good I'm sure our Critical Care guys will have your query fixed up.
Perhaps try and get the source IP to see where your content is being pulled from?