Afrihost New Network Feedback - Part 2

[DreamKing]

today can't download anything.

four times already, just cut off and back 4 times!!!!!!!

what the hell is going on today?

 

[AfriGuy]

today can't download anything.

four times already, just cut off and back 4 times!!!!!!!

what the hell is going on today?

Are downloads the only slow service on your end?
Not seeing any general issues.

 

[DreamKing]

Are downloads the only slow service on your end?
Not seeing any general issues.

not slow.

cut off for few seconds and back. you know some of the download files can't be interrupted, otherwise it has to download from the beginning again.

 

[AfriGuy]

not slow.

cut off for few seconds and back. you know some of the download files can't be interrupted, otherwise it has to download from the beginning again.

Oh no
Perhaps try a download manager?

 

[Icemanbrfc]

The food

well no surprise there

 

[wingnut771]

Oh no
Perhaps try a download manager?

LOL - If DreamKing's line is dropping, LOG A FAULT WITH TELKOM, not suggest software.

 

[cavedog]

Twitch has always been a problem for me for some reason. Twitch buffers but youtube 1080p not exact same stream. Streaming the league of legends EU LCS.

20Mbps adsl2+ line

Routing international server?

Okay saw now that twitch server is a US server and the youtube stream is mweb server in Durban....

 

[AfriGenie]

Twitch has always been a problem for me for some reason. Twitch buffers but youtube 1080p not exact same stream. Streaming the league of legends EU LCS.

20Mbps adsl2+ line

Routing international server?

Okay saw now that twitch server is a US server and the youtube stream is mweb server in Durban....

Yup, there are local CDNs for Google services which does speed Youtube up a lot.

 

[Vio]

Sorry to hear that
Did you manage to grab any tests to see where the latency was being introduced?

It looked like there was some sort of problem between the peer between Afrihost and adept's napafrica peer in ct.

Tonight however I am seeing the old latency problem between the second and third hop on Afrihost:
=BRAS=
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 16ms, Average = 11ms

=2nd hop=
Pinging cpt-rx2.ip.adsl.co.za [169.1.5.82] with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=33ms TTL=59
Reply from 169.1.5.82: bytes=32 time=40ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=16ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=25ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59

Ping statistics for 169.1.5.82:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 40ms, Average = 18ms

=3rd hop aka cpt-net1.ip.adsl.co.za=
Pinging 196.10.140.72 with 32 bytes of data:
Reply from 196.10.140.72: bytes=32 time=96ms TTL=59
Reply from 196.10.140.72: bytes=32 time=64ms TTL=59
Reply from 196.10.140.72: bytes=32 time=13ms TTL=59
Reply from 196.10.140.72: bytes=32 time=77ms TTL=59
Reply from 196.10.140.72: bytes=32 time=80ms TTL=59
Reply from 196.10.140.72: bytes=32 time=63ms TTL=59
Reply from 196.10.140.72: bytes=32 time=62ms TTL=59
Reply from 196.10.140.72: bytes=32 time=91ms TTL=59
Reply from 196.10.140.72: bytes=32 time=22ms TTL=59
Reply from 196.10.140.72: bytes=32 time=86ms TTL=59
Reply from 196.10.140.72: bytes=32 time=111ms TTL=59
Reply from 196.10.140.72: bytes=32 time=102ms TTL=59
Reply from 196.10.140.72: bytes=32 time=122ms TTL=59
Reply from 196.10.140.72: bytes=32 time=86ms TTL=59
Reply from 196.10.140.72: bytes=32 time=109ms TTL=59
Reply from 196.10.140.72: bytes=32 time=126ms TTL=59
Reply from 196.10.140.72: bytes=32 time=106ms TTL=59
Reply from 196.10.140.72: bytes=32 time=24ms TTL=59
Reply from 196.10.140.72: bytes=32 time=85ms TTL=59
Reply from 196.10.140.72: bytes=32 time=114ms TTL=59
Reply from 196.10.140.72: bytes=32 time=96ms TTL=59
Reply from 196.10.140.72: bytes=32 time=35ms TTL=59
Reply from 196.10.140.72: bytes=32 time=88ms TTL=59
Reply from 196.10.140.72: bytes=32 time=107ms TTL=59
Reply from 196.10.140.72: bytes=32 time=113ms TTL=59
Reply from 196.10.140.72: bytes=32 time=251ms TTL=59
Reply from 196.10.140.72: bytes=32 time=79ms TTL=59
Reply from 196.10.140.72: bytes=32 time=117ms TTL=59
Reply from 196.10.140.72: bytes=32 time=109ms TTL=59
Reply from 196.10.140.72: bytes=32 time=112ms TTL=59
Reply from 196.10.140.72: bytes=32 time=116ms TTL=59
Reply from 196.10.140.72: bytes=32 time=109ms TTL=59
Reply from 196.10.140.72: bytes=32 time=117ms TTL=59
Reply from 196.10.140.72: bytes=32 time=108ms TTL=59
Reply from 196.10.140.72: bytes=32 time=104ms TTL=59
Reply from 196.10.140.72: bytes=32 time=116ms TTL=59
Reply from 196.10.140.72: bytes=32 time=104ms TTL=59
Reply from 196.10.140.72: bytes=32 time=100ms TTL=59
Reply from 196.10.140.72: bytes=32 time=89ms TTL=59
Request timed out.

Ping statistics for 196.10.140.72:
Packets: Sent = 40, Received = 39, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 251ms, Average = 95ms

 

[cavedog]

Yup, there are local CDNs for Google services which does speed Youtube up a lot.

Quick question.

Capped accounts allow for 1 month roll over. If I add a Afrihost Plus+ account does the double data on a capped account roll over for a month too or only the base data from the account?

 

[Hummercellc]

Quick question.

Capped accounts allow for 1 month roll over. If I add a Afrihost Plus+ account does the double data on a capped account roll over for a month too or only the base data from the account?

Yes, mine rolls over...

 

[krustyrsa]

Still going strong , happy to report no issues from my side.

 

[Devo1]

@ AfriGuy

My line seems to be fixed (touch wood). Telkom phoned me and said it was a network fault.

Things looking good now.

Just hope it lasts.

Upgrading my line speed soon.

 

[AfriGenie]

Quick question.

Capped accounts allow for 1 month roll over. If I add a Afrihost Plus+ account does the double data on a capped account roll over for a month too or only the base data from the account?

All of the data will roll-over.

 

[AfriGenie]

Still going strong , happy to report no issues from my side.
View attachment 374411

Sweeeeeet!

 

[AfriGenie]

@ AfriGuy

My line seems to be fixed (touch wood). Telkom phoned me and said it was a network fault.

Things looking good now.

Just hope it lasts.

Upgrading my line speed soon.

Excellent! Which DSL line speed are you thinking of upgrading to?

 

[AfriGenie]

It looked like there was some sort of problem between the peer between Afrihost and adept's napafrica peer in ct.

Tonight however I am seeing the old latency problem between the second and third hop on Afrihost:
=BRAS=
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 16ms, Average = 11ms

=2nd hop=
Pinging cpt-rx2.ip.adsl.co.za [169.1.5.82] with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=33ms TTL=59
Reply from 169.1.5.82: bytes=32 time=40ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=16ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=25ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59

Ping statistics for 169.1.5.82:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 40ms, Average = 18ms

=3rd hop aka cpt-net1.ip.adsl.co.za=
Pinging 196.10.140.72 with 32 bytes of data:
Reply from 196.10.140.72: bytes=32 time=96ms TTL=59
Reply from 196.10.140.72: bytes=32 time=64ms TTL=59
Reply from 196.10.140.72: bytes=32 time=13ms TTL=59
Reply from 196.10.140.72: bytes=32 time=77ms TTL=59
Reply from 196.10.140.72: bytes=32 time=80ms TTL=59
Reply from 196.10.140.72: bytes=32 time=63ms TTL=59
Reply from 196.10.140.72: bytes=32 time=62ms TTL=59
Reply from 196.10.140.72: bytes=32 time=91ms TTL=59
Reply from 196.10.140.72: bytes=32 time=22ms TTL=59
Reply from 196.10.140.72: bytes=32 time=86ms TTL=59
Reply from 196.10.140.72: bytes=32 time=111ms TTL=59
Reply from 196.10.140.72: bytes=32 time=102ms TTL=59
Reply from 196.10.140.72: bytes=32 time=122ms TTL=59
Reply from 196.10.140.72: bytes=32 time=86ms TTL=59
Reply from 196.10.140.72: bytes=32 time=109ms TTL=59
Reply from 196.10.140.72: bytes=32 time=126ms TTL=59
Reply from 196.10.140.72: bytes=32 time=106ms TTL=59
Reply from 196.10.140.72: bytes=32 time=24ms TTL=59
Reply from 196.10.140.72: bytes=32 time=85ms TTL=59
Reply from 196.10.140.72: bytes=32 time=114ms TTL=59
Reply from 196.10.140.72: bytes=32 time=96ms TTL=59
Reply from 196.10.140.72: bytes=32 time=35ms TTL=59
Reply from 196.10.140.72: bytes=32 time=88ms TTL=59
Reply from 196.10.140.72: bytes=32 time=107ms TTL=59
Reply from 196.10.140.72: bytes=32 time=113ms TTL=59
Reply from 196.10.140.72: bytes=32 time=251ms TTL=59
Reply from 196.10.140.72: bytes=32 time=79ms TTL=59
Reply from 196.10.140.72: bytes=32 time=117ms TTL=59
Reply from 196.10.140.72: bytes=32 time=109ms TTL=59
Reply from 196.10.140.72: bytes=32 time=112ms TTL=59
Reply from 196.10.140.72: bytes=32 time=116ms TTL=59
Reply from 196.10.140.72: bytes=32 time=109ms TTL=59
Reply from 196.10.140.72: bytes=32 time=117ms TTL=59
Reply from 196.10.140.72: bytes=32 time=108ms TTL=59
Reply from 196.10.140.72: bytes=32 time=104ms TTL=59
Reply from 196.10.140.72: bytes=32 time=116ms TTL=59
Reply from 196.10.140.72: bytes=32 time=104ms TTL=59
Reply from 196.10.140.72: bytes=32 time=100ms TTL=59
Reply from 196.10.140.72: bytes=32 time=89ms TTL=59
Request timed out.

Ping statistics for 196.10.140.72:
Packets: Sent = 40, Received = 39, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 251ms, Average = 95ms

That doesn't look good. I'm going to PM you a SAIX-based test account, would you mind switching to that and seeing if there is any difference.

 

[linkinpark]

Afrihost email support has really degraded, my ticket is going around in circles with different support technicians asking me generic questions I've already replied to in the same ticket...
Time to move my ADSL line to another ISP. Any recommendations?

 

[AfriGenie]

Afrihost email support has really degraded, my ticket is going around in circles with different support technicians asking me generic questions I've already replied to in the same ticket...
Time to move my ADSL line to another ISP. Any recommendations?

That's not good to hear!

If you can PM me the ticket ID I can check what's going on.

 

[linkinpark]

PM'd, thanks