Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
speeds has gone down the crapper all of a sudden

While you're welcome to query results, I really think you should start backing up your posts with some test results.
I really can't help if all of your posts look like this:

youtube is not working just showing errors

yep speeds has been down the crapper the last 2-3 weeks

browsing is very slow this side

we always use google dns as we had too much trouble with the one from ah
this is a sporadic problem the one moment everything is fine and the next moment it slows down and becomes sluggish

it is a capped account and there should be no shaping this morning was fine but now the internet is jerky again and slow

it is not only downloads that have erratic speeds even after midnight but browsing is a serious problem with pages loading half way and must be refreshed a couple of times
ii sure looks like shaping or maybe a bandwidth problem

internet is very jerky and unresponsive today

even browsing is down the crapper you have to refresh 2-3 times to get to a page

speeds are up and down even after 12pm makes me think back to the similar problems from last year

must agree things has not been good the last 2 weeks

speeds has taken a serious dive and are crappy

browsing is very erratic and slow again specially international

browsing is very erratic and slow again specially international

internet is very sluggish and intermittent browsing takes forever to load but after midnight it is all systems go whats up afrihost

browsing and latency is bad tonight

speeds and browsing are down the crapper again this evening with linux updates almost not working
 
Very possible, only way to confirm a failing modem is to test with another though.

he tested with his, and it passed. Mine failed. So i need to go to a Telkom store to get it swapped out. at least there is progress :)
 
he tested with his, and it passed. Mine failed. So i need to go to a Telkom store to get it swapped out. at least there is progress :)

Hhhmm, were you having issues though?
Before taking the plunge on a new modem, try and borrow one from a mate to see if the issues are replicated?
 
Hhhmm, were you having issues though?
Before taking the plunge on a new modem, try and borrow one from a mate to see if the issues are replicated?

yeh i intend to do just that. Only issues i have is my download speeds. with his modem he got 17mbps, with mine only 4mbps.
 
o.0
That's quite the difference!

yeh that sucks dude. Stats for nerds backs up my connection speed, as it fluctuates between 3 and 4000kbps on youtube, nothing more. In fairness though, i could stream in 720p and 1080p without a problem, but im not getting full line speed which is my issue.
 
yeh that sucks dude. Stats for nerds backs up my connection speed, as it fluctuates between 3 and 4000kbps on youtube, nothing more. In fairness though, i could stream in 720p and 1080p without a problem, but im not getting full line speed which is my issue.

Definitely an issue! Keep me posted on how the testing goes though.
 
Anybody in Durban/KZN having any issues? Lag spikes galore, jumps between 400 and 2000ms internationally. Locals also a bit shoddy.
 
Anybody in Durban/KZN having any issues? Lag spikes galore, jumps between 400 and 2000ms internationally. Locals also a bit shoddy.

Definitely no latency like that appearing from our end, is there a traceroute I can take a look at to see where this latency is being introduced?
 
Just a question, why does my tracert have * and lots of request time out

Tracing route to www.mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 63 ms 24 ms 22 ms 104.20.72.110

Trace complete.
 
Just a question, why does my tracert have * and lots of request time out

Tracing route to www.mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 63 ms 24 ms 22 ms 104.20.72.110

Trace complete.

Seems like something is wrong there, there shouldn't be this many times.
Have you tried rebooting your modem?

As a comparison, here's what my traceroute looks like - timeouts on the 2nd hop are normal, but not all the way through.

Code:
traceroute to mybroadband.co.za (104.20.71.110), 64 hops max, 52 byte packets
 1  er-8.ubnt (192.168.1.2)  0.406 ms  0.164 ms  0.141 ms
 2  * * *
 3  * cpt-up1.ip.adsl.co.za (169.1.5.105)  17.223 ms  17.291 ms
 4  cpt-up2.ip.adsl.co.za (169.1.5.106)  18.771 ms  17.063 ms  17.613 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  19.114 ms  18.366 ms  18.203 ms
 6  41.164.52.40 (41.164.52.40)  18.045 ms  18.954 ms  18.182 ms
 7  172.18.1.162 (172.18.1.162)  39.976 ms  65.171 ms  39.621 ms
 8  cloudflare.ixp.joburg (196.46.25.198)  53.105 ms  40.571 ms  40.229 ms
 9  104.20.71.110 (104.20.71.110)  40.842 ms  41.069 ms  41.516 ms
 
Murphy's law - 10 seconds after posting it normalised... Thanks Afriguy!

Hehe, that post button must have magical powers ;) Glad things seem to have normalised now.
If you do see another latency spike though, please grab a traceroute so we can see where the issues are coming in.
 
Seems like something is wrong there, there shouldn't be this many times.
Have you tried rebooting your modem?

As a comparison, here's what my traceroute looks like - timeouts on the 2nd hop are normal, but not all the way through.

Code:
traceroute to mybroadband.co.za (104.20.71.110), 64 hops max, 52 byte packets
 1  er-8.ubnt (192.168.1.2)  0.406 ms  0.164 ms  0.141 ms
 2  * * *
 3  * cpt-up1.ip.adsl.co.za (169.1.5.105)  17.223 ms  17.291 ms
 4  cpt-up2.ip.adsl.co.za (169.1.5.106)  18.771 ms  17.063 ms  17.613 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  19.114 ms  18.366 ms  18.203 ms
 6  41.164.52.40 (41.164.52.40)  18.045 ms  18.954 ms  18.182 ms
 7  172.18.1.162 (172.18.1.162)  39.976 ms  65.171 ms  39.621 ms
 8  cloudflare.ixp.joburg (196.46.25.198)  53.105 ms  40.571 ms  40.229 ms
 9  104.20.71.110 (104.20.71.110)  40.842 ms  41.069 ms  41.516 ms

Yeah, been having this problem since I got the new router . Tp link w8980. Can firewall interfere tracert results?
 
Yeah, been having this problem since I got the new router . Tp link w8980. Can firewall interfere tracert results?

It may do, any special setups running on the router?
What DNS servers do you have configured?
 
And Again the routing of YouTube and Google is going international, this time to London -LHR
Router is on Automatic so using the DNS that is assigned by ISP.
169.1.1.4 169.1.1.9

The routing of the Google DNS servers go Local, but not the routing to Google search anhd YouTube.
I have switched acounts between VOX & Afrihost, did a "FlushDNS, Rebooted Router, Rebooted PC, nothing has any affect on the routing.

PS C:\Windows\system32> ping 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=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms 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 = 21ms, Maximum = 21ms, Average = 21ms
PS C:\Windows\system32> 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 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 24 ms 22 ms 22 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 23 ms 23 ms 22 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 23 ms 22 ms 22 ms 41.164.52.40
6 54 ms 48 ms 44 ms 172.18.1.162
7 60 ms 61 ms 59 ms 72.14.194.206
8 44 ms 44 ms 44 ms 72.14.239.117
9 44 ms 44 ms 44 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

PS C:\Windows\system32> tracert 8.8.4.4

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 23 ms 22 ms 25 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 25 ms 22 ms 22 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 23 ms 23 ms 22 ms 41.164.52.40
6 44 ms 43 ms 46 ms 172.18.1.162
7 51 ms 53 ms 52 ms 72.14.194.206
8 45 ms 44 ms 47 ms 72.14.239.35
9 44 ms 44 ms 44 ms google-public-dns-b.google.com [8.8.4.4]

Trace complete.
PS C:\Windows\system32> tracert youtube.co.za

Tracing route to youtube.co.za [172.217.23.46]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 23 ms 22 ms 22 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 23 ms 22 ms 23 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 22 ms 22 ms 22 ms 41.164.52.40
6 44 ms 44 ms 43 ms 172.18.1.162
7 44 ms 45 ms 44 ms 72.14.194.206
8 205 ms 204 ms 204 ms 72.14.234.161
9 183 ms 183 ms 183 ms 209.85.247.30
10 201 ms 201 ms 202 ms 216.239.48.113
11 205 ms 205 ms 205 ms 108.170.235.107
12 205 ms 205 ms 205 ms lhr35s02-in-f14.1e100.net [172.217.23.46]

Trace complete.
PS C:\Windows\system32> tracert youtube.com

Tracing route to youtube.com [172.217.23.46]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 24 ms 22 ms 22 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 23 ms 22 ms 22 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 23 ms 22 ms 23 ms 41.164.52.40
6 46 ms 44 ms 45 ms 172.18.1.162
7 49 ms 45 ms 44 ms 72.14.194.206
8 204 ms 204 ms 205 ms 72.14.234.161
9 183 ms 184 ms 183 ms 209.85.247.30
10 202 ms 202 ms 202 ms 216.239.48.113
11 205 ms 205 ms 205 ms 108.170.235.107
12 205 ms 1136 ms 392 ms lhr35s02-in-f14.1e100.net [172.217.23.46]

Trace complete.
PS C:\Windows\system32> tracert google.co.za

Tracing route to google.co.za [172.217.23.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 752 ms 454 ms 66 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 25 ms 24 ms 24 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 22 ms 23 ms 22 ms 41.164.52.40
6 43 ms 43 ms 43 ms 172.18.1.162
7 44 ms 43 ms 44 ms 72.14.194.206
8 203 ms 204 ms 204 ms 72.14.234.161
9 186 ms 186 ms 186 ms 72.14.238.244
10 202 ms 202 ms 203 ms 216.239.54.243
11 205 ms 205 ms 205 ms 108.170.233.199
12 201 ms 201 ms 201 ms lhr35s01-in-f3.1e100.net [172.217.23.3]

Trace complete.
PS C:\Windows\system32> tracert google.com

Tracing route to google.com [172.217.23.46]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 23 ms 22 ms 22 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 23 ms 24 ms 22 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 23 ms 22 ms 23 ms 41.164.52.40
6 44 ms 43 ms 44 ms 172.18.1.162
7 49 ms 46 ms 44 ms 72.14.194.206
8 204 ms 204 ms 204 ms 72.14.234.161
9 184 ms 183 ms 188 ms 209.85.247.30
10 202 ms 202 ms 202 ms 216.239.48.113
11 205 ms 206 ms 205 ms 108.170.235.107
12 205 ms 204 ms 205 ms lhr35s02-in-f14.1e100.net [172.217.23.46]

Trace complete.
 
And Again the routing of YouTube and Google is going international, this time to London -LHR
Router is on Automatic so using the DNS that is assigned by ISP.
169.1.1.4 169.1.1.9

The routing of the Google DNS servers go Local, but not the routing to Google search anhd YouTube.
I have switched acounts between VOX & Afrihost, did a "FlushDNS, Rebooted Router, Rebooted PC, nothing has any affect on the routing.

-snip

Trace complete.

Hi

The DNS resolution doesn't really matter in this case, content is still, or should be pulled, from a local cache/ CDN.
What's displayed here? Remember to edit your public IP before posting.

http://redirector.c.youtube.com/report_mapping

EDIT:Also, please include a video and resolution that you're specifically battling with.
 
Last edited:
Hi

The DNS resolution doesn't really matter in this case, content is still, or should be pulled, from a local cache/ CDN.
What's displayed here? Remember to edit your public IP before posting.

http://redirector.c.youtube.com/report_mapping

EDIT:Also, please include a video and resolution that you're specifically battling with.

169.1.xx.xxx => afrihostza-cpt1 (169.1.73.0/24)
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X