Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Getting a concentrator not reachable error. Im pming you my details. Please check out the issue.
 
caroper said:
I am using the "Get from ISP" setting for DNS.
Just switched over to Telkom account to make sure it is not the line.
Although I am not getting close to what I had on Afrihost this afternoon, I am getting 250KBs rather than 50KBs.
Considering Telkom is shaped vs Afrihost unshaped that could explain it, it is a P2P stream.
So if there is no capacity Issue and I still can't stream in the evenings, then Afrihost has still not fixed the issue that caused me to leave.
Click to expand...

Please post some test results.
Regarding streaming, I'll need a video URL and resolution you're viewing at.
 
jmacc said:
Afrihost DNS servers are too unreliable. We have tried numerous times to use your servers but these servers are plagued by outages, stale records and inconsistencies. Google's DNS servers offers a stable reliable service. Why do you guys shape traffic on capped accounts when you advertise that capped accounts are not shaped?
Click to expand...

Shouldn't be the case, our new network came along with a new set of DNS servers and there have been no widespread issues.
What kind of issues have you been experiencing?

Capped accounts are unshaped.
 
Rickster said:
This normal?

PS C:\WINDOWS\system32> tracert 197.84.209.21

Tracing route to 197-84-209-21.cpt.mweb.co.za [197.84.209.21]
over a maximum of 30 hops:

1 1 ms 4 ms 4 ms 192.168.0.1
2 * * * Request timed out.
3 27 ms 25 ms 24 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 28 ms 26 ms 33 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 26 ms 26 ms 25 ms mweb.ixp.joburg [196.46.25.145]
6 49 ms 47 ms 74 ms te0-7-0-3.vic-p-2.optinet.net [197.80.7.98]
7 49 ms 47 ms 47 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
8 46 ms 45 ms 45 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 47 ms 45 ms 44 ms 196.28.178.66
10 45 ms 44 ms 44 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
11 45 ms 70 ms 44 ms 197-84-209-21.cpt.mweb.co.za [197.84.209.21]
Click to expand...

Looks fine to me.
 
Youtube not working Afrihost. Telkom seems fine.
****! 3 days and I am looking for a new ISP.
 
Brother is struggling to update his xbox one over a wired connection, not sure how to test that.
 
So, YouTube was totally dead just now - no images loaded or video (and sometimes not even the stylesheet). Drive also behaved weirdly.

I ended up having to flush my router's DNS resolver cache as well as my PC cache. Instant fix when the new IPs were pulled.

Seems the TTL on these entries are set to 30 minutes (if I look at all the googlevideo.com entries in my cache), and somehow a bad batch must have been dished out by Afrihost's DNS. (I'm sure if I left things for 30 minutes, it would have fixed itself.)

Wonder why this happened?

Still does not explain the patchy performance on older lesser watched videos though - tried watching one now again and it doesn't even start playing. https://youtu.be/TCJcrhFbKLY is one example. (Yeah, another obscure vid for your collection! :-))
 
Hey AfriGuy

At 8:30pm today my connection went haywire for about 30 minutes and hasn't recovered :(
I started disconnecting non stop, I tried resetting multiple times but it took about half an hour for the disconnects to stop.

www.afrihost.com.jpg

But now I'm getting this. Ever since those disconnects my ping has been raised by 100 across the board. Local and international speeds are appalling and I have crazy packet loss too. I keep disconnecting from TS and online games.

afrihost.com.png2.jpg

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 100 ms 99 ms * dbn-up2.ip.adsl.co.za [169.1.5.174]
4 95 ms * 93 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 94 ms 96 ms * 41.162.84.192
6 107 ms 95 ms 105 ms 172.18.1.162
7 103 ms 103 ms * cloudflare.ixp.joburg [196.46.25.198]
8 102 ms 113 ms * 104.20.31.244
9 114 ms 102 ms 108 ms 104.20.31.244

Trace complete.

ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=90ms TTL=63
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 90ms, Average = 90ms

Please help :(
 
Forgot to mention, before all this happened I had a stable ping of 10 to afrihost.com. My connection has been fine until 8:30pm today.
 
AfriGuy said:
Shouldn't be the case, our new network came along with a new set of DNS servers and there have been no widespread issues.
What kind of issues have you been experiencing?

Capped accounts are unshaped.
Click to expand...

Like I've said, Afrihost DNS servers experience outages, stale records and have inconsistent databases. One simple example is when users get name resolution errors in their browsers. When you switch back to Google DNS on the router, browsing functionality returns. This happened recently. Capped accounts are definitely shaped, especially when it comes to updates. There is no doubt about this. If I update a system and the update takes hours to complete as opposed to the same update being downloaded manually within 10 minutes using a browser, common sense dictates that this is not normal behavior. In addition, when you have an update struggling to download via Afrihost's network and you change to another ISP, things normalize and the update download completes almost instantly. If you open task manager on a Windows machine or Activity monitor on a MAC and you go to the network interface you can clearly see how Afrihost throttles the connection. Once again if I switch ISPs the connection runs at full speed all the time. This happens every time major/size-able updates are released by Microsoft or Apple. Obviously the Afrihost network is under strain during these periods. The problem is - why do I pay for an unshaped service and then Afrihost shapes my connection. To say that Afrihost does not do shaping on a capped account is simply not true.
 
Last edited:
AfriGuy said:
Please post some test results.
Regarding streaming, I'll need a video URL and resolution you're viewing at.
Click to expand...

Well I did post my test results, the Telkom account was 5 times faster than the Afrihost account, but only a quarter of the speed that Afrihost was before 6PM. I can't give a URL, as I pointed out it is a P2P stream, but the stream key is acestream://2288397a21c4933d2359f19f54daa4101e297a48 if you have a player suitable to stream it.
It is a SD stream, I didn't even attempt an HD stream if Afrihost was unable to start the SD one.
 
AfriGuy said:
It also saves us a bunch of traffic.
Mind posting what's displayed here, along with your DNS setup please?

http://redirector.c.youtube.com/report_mapping
Click to expand...

... => afrihostza-cpt1 (169.1.147.0/24)
However routing changed since the tracert yesterday. Attached below. Not hitting the cache.
DNS - 169.1.1.1 and 169.1.1.10

Code: 
Tracing route to www.youtube.com [216.58.201.46]
over a maximum of 30 hops:

  1     4 ms     1 ms     3 ms  modem.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    15 ms    15 ms    16 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    18 ms    15 ms    15 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    35 ms    15 ms    13 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    15 ms    14 ms    14 ms  41.164.52.40
  7    36 ms    37 ms    38 ms  172.18.1.162
  8    35 ms    36 ms    35 ms  72.14.194.206
  9   200 ms   195 ms   195 ms  66.249.95.8
 10   196 ms   197 ms   196 ms  209.85.255.77
 11   201 ms   199 ms   197 ms  216.239.41.17
 12   196 ms   195 ms   196 ms  72.14.234.131
 13   197 ms   198 ms   198 ms  youtu.be [216.58.201.46]

Trace complete.
 
Icemanbrfc said:
Okay so i have another technician at my place, who seems rather clued up compared to the ones that came before. Says could be my modem that is failing, because he is picking up a metallic noise (whatever that means) Also says that maybe my surround sound and Xbox power supplies are causing issues or interference
Click to expand...

Hahaha... maybe they should take off their tinfoil hat and stick it on the modem.
Kinda had my fill of Telkom conspiracy theories about client modems :p
;)
 
steel_dog said:
... => afrihostza-cpt1 (169.1.147.0/24)
However routing changed since the tracert yesterday. Attached below. Not hitting the cache.
DNS - 169.1.1.1 and 169.1.1.10

Code: 
Tracing route to www.youtube.com [216.58.201.46]
over a maximum of 30 hops:

  1     4 ms     1 ms     3 ms  modem.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    15 ms    15 ms    16 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    18 ms    15 ms    15 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    35 ms    15 ms    13 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    15 ms    14 ms    14 ms  41.164.52.40
  7    36 ms    37 ms    38 ms  172.18.1.162
  8    35 ms    36 ms    35 ms  72.14.194.206
  9   200 ms   195 ms   195 ms  66.249.95.8
 10   196 ms   197 ms   196 ms  209.85.255.77
 11   201 ms   199 ms   197 ms  216.239.41.17
 12   196 ms   195 ms   196 ms  72.14.234.131
 13   197 ms   198 ms   198 ms  youtu.be [216.58.201.46]

Trace complete.
Click to expand...

Code: 
C:\WINDOWS\system32>tracert youtube.com

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

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1]
  2     1 ms     1 ms     1 ms  home.gateway.pace.net [192.168.1.1]
  3     *        *        *     Request timed out.
  4    23 ms    22 ms    22 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  5    25 ms    23 ms    25 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  6    25 ms    22 ms    25 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  7    23 ms    23 ms    23 ms  41.164.52.40
  8    44 ms    44 ms    44 ms  172.18.1.162
  9    59 ms    44 ms    45 ms  72.14.194.206
 10   203 ms   203 ms   202 ms  72.14.234.161
 11   206 ms   205 ms   204 ms  209.85.246.59
 12   205 ms   206 ms   205 ms  108.170.232.99
 13   206 ms   205 ms   205 ms  lhr25s10-in-f14.1e100.net [216.58.198.174]

Trace complete.

Your address:
Tracing route to lhr35s04-in-f14.1e100.net [216.58.201.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1]
  2     1 ms     1 ms     1 ms  home.gateway.pace.net [192.168.1.1]
  3     *        *        *     Request timed out.
  4    29 ms    22 ms    22 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  5    25 ms    23 ms    24 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  6    25 ms    22 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  7    24 ms    23 ms    23 ms  41.164.52.40
  8    45 ms    44 ms    44 ms  172.18.1.162
  9    46 ms    45 ms    44 ms  72.14.194.206
 10   205 ms   203 ms   202 ms  72.14.234.161
 11   203 ms   201 ms   201 ms  216.239.54.130
 12   205 ms   203 ms   203 ms  216.239.54.239
 13   203 ms   203 ms   202 ms  72.14.234.133
 14   208 ms   204 ms   203 ms  lhr35s04-in-f14.1e100.net [216.58.201.46]

Trace complete.
I'm using Google DNS and my latency to the exchange is ~7ms more than yours.
 
Seems like there's a lot of latency at the moment, 2.39am. Very weird.

Will do some tests in the morning and see if there's still an issue, will report back.
 
YouTube was pretty bad for earlier and it does seem to be related to the routing. I was buffering like crazy.
It changed earlier today and changed back after 1am

12pm yesterday
Code: 
Tracing route to youtube-ui.l.google.com [169.1.2.92]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    21 ms    21 ms    20 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    20 ms    20 ms    24 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    23 ms    21 ms    22 ms  169-1-21-9.ip.afrihost.co.za [169.1.21.9] 
  6    21 ms    27 ms    21 ms  169-1-2-92.ip.afrihost.co.za [169.1.2.92] 

Trace complete.

3pm yesterday
Code: 
Tracing route to youtube-ui.l.google.com [216.58.201.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    23 ms    22 ms    22 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    34 ms    22 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    34 ms    26 ms    22 ms  41.164.52.40 
  6    43 ms    42 ms    45 ms  172.18.1.162 
  7    43 ms    47 ms    49 ms  72.14.194.206 
  8   204 ms   204 ms   209 ms  66.249.95.8 
  9   204 ms   206 ms   204 ms  209.85.252.62 
 10   206 ms   205 ms   216 ms  216.58.215.67 
 11   217 ms   205 ms   205 ms  72.14.234.117 
 12   207 ms   206 ms   206 ms  lhr35s03-in-f14.1e100.net [216.58.201.14] 

Trace complete.

After 3pm the latency stayed at just over 200ms until 1am this morning.

1am today
Code: 
Tracing route to youtube-ui.l.google.com [169.1.2.90]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    24 ms    21 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4     *       21 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    24 ms    23 ms    23 ms  169.1.21.9 
  6    21 ms    22 ms    21 ms  169.1.2.90 

Trace complete.

Also interesting is how the destination IP changed
Code: 
StartOn			IpAddress	Max Latency
2016-09-14 12:26:38 PM 	169.1.2.92	23
2016-09-14 03:22:42 PM 	216.58.201.14	209
2016-09-14 03:52:53 PM 	216.58.214.14	212
2016-09-14 04:27:04 PM 	216.58.201.14	209
2016-09-14 05:02:55 PM 	216.58.212.78	207
2016-09-14 05:22:28 PM 	216.58.201.46	203
2016-09-14 05:42:11 PM 	216.58.214.14	220
2016-09-14 06:12:11 PM 	172.217.23.46	204
2016-09-14 06:41:55 PM 	216.58.201.46	204
2016-09-14 07:12:13 PM 	216.58.213.110	212
2016-09-14 07:42:10 PM 	216.58.213.110	214
2016-09-14 08:12:28 PM 	172.217.23.46	209
2016-09-14 08:37:05 PM 	216.58.201.46	239
2016-09-14 08:57:10 PM 	216.58.198.174	281
2016-09-14 09:26:59 PM 	216.58.212.78	279
2016-09-14 10:27:36 PM 	172.217.23.14	214
2016-09-14 10:56:49 PM 	216.58.201.14	239
2016-09-14 11:26:48 PM 	172.217.23.46	206
2016-09-14 11:53:11 PM 	216.58.201.14	206
2016-09-15 12:26:49 AM 	216.58.198.174	205
2016-09-15 12:55:47 AM 	169.1.2.90	23
2016-09-15 01:30:38 AM 	169.1.2.93	23
2016-09-15 01:53:19 AM 	169.1.2.91	26
2016-09-15 02:06:09 AM 	169.1.2.89	22
2016-09-15 02:25:23 AM 	169.1.2.86	23
2016-09-15 02:55:04 AM 	169.1.2.89	23
 
Overall the browsing experience was not very good either. It seems the latency issues/routing issues we assumed were fixed are back.

Play Store 12pm
Code: 
Tracing route to play.l.google.com [169.1.2.80]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    23 ms    22 ms    25 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    23 ms    20 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    21 ms    21 ms  169-1-21-9.ip.afrihost.co.za [169.1.21.9] 
  6    20 ms    21 ms    21 ms  169-1-2-80.ip.afrihost.co.za [169.1.2.80] 

Trace complete.

Play Store 3pm
Code: 
Tracing route to play.l.google.com [172.217.23.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    29 ms    22 ms    31 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    48 ms    25 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    21 ms    22 ms  41.164.52.40 
  6    42 ms    49 ms    43 ms  172.18.1.162 
  7    45 ms    45 ms    45 ms  72.14.194.206 
  8   201 ms   214 ms   200 ms  72.14.234.161 
  9   184 ms   183 ms   184 ms  209.85.243.42 
 10   206 ms   205 ms   204 ms  216.239.56.195 
 11   202 ms   201 ms   201 ms  108.170.235.107 
 12   201 ms   200 ms   219 ms  lhr35s02-in-f46.1e100.net [172.217.23.46] 

Trace complete.

Play Store 1am
Code: 
Tracing route to play.l.google.com [169.1.2.92]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    23 ms    21 ms    22 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    22 ms    21 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    25 ms    22 ms    23 ms  169.1.21.9 
  6    24 ms    21 ms    20 ms  169.1.2.92 

Trace complete.

Latency for news24.com
Code: 
StartOn			Target		MaxLatency
2016-09-14 19:31:48.277	www.news24.com	38
2016-09-14 20:01:48.783	www.news24.com	38
2016-09-14 20:31:50.28	www.news24.com	25
2016-09-14 20:46:47.787	www.news24.com	90
2016-09-14 21:16:51.367	www.news24.com	82
2016-09-14 21:46:52.623	www.news24.com	52
2016-09-14 22:46:50.26	www.news24.com	51
2016-09-14 23:16:48.29	www.news24.com	62
2016-09-15 00:16:52.237	www.news24.com	25
2016-09-15 01:17:17.237	www.news24.com	24
2016-09-15 02:16:50.717	www.news24.com	28
2016-09-15 03:16:52.217	www.news24.com	23

Latency for telkom.co.za
Code: 
StartOn			Target			MaxLatency
2016-09-14 19:03:40.88	www.telkom.co.za	47
2016-09-14 19:33:37.02	www.telkom.co.za	91
2016-09-14 20:03:44.41	www.telkom.co.za	46
2016-09-14 20:33:38.463	www.telkom.co.za	129
2016-09-14 20:48:37.917	www.telkom.co.za	85
2016-09-14 21:18:41.377	www.telkom.co.za	102
2016-09-14 21:48:41.64	www.telkom.co.za	60
2016-09-14 21:57:36.903	www.telkom.co.za	81
2016-09-14 22:19:01.36	www.telkom.co.za	100
2016-09-14 22:48:34.93	www.telkom.co.za	46
2016-09-14 23:18:33.09	www.telkom.co.za	55
2016-09-14 23:44:59.983	www.telkom.co.za	48
2016-09-15 00:18:36.453	www.telkom.co.za	96
2016-09-15 00:47:36.853	www.telkom.co.za	46
2016-09-15 01:20:29.893	www.telkom.co.za	46

Latency for afrihost.com
Code: 
StartOn			Target			MaxLatency
2016-09-14 18:33:01.437	www.afrihost.com	45
2016-09-14 19:03:02.543	www.afrihost.com	45
2016-09-14 19:32:58.527	www.afrihost.com	101
2016-09-14 20:03:06.037	www.afrihost.com	52
2016-09-14 20:32:59.953	www.afrihost.com	45
2016-09-14 20:47:59.107	www.afrihost.com	114
2016-09-14 21:18:02.523	www.afrihost.com	114
2016-09-14 21:48:03.257	www.afrihost.com	82
2016-09-14 22:18:02.33	www.afrihost.com	1001
2016-09-14 22:47:56.56	www.afrihost.com	59
2016-09-14 23:17:54.6	www.afrihost.com	60
2016-09-14 23:44:21.46	www.afrihost.com	44

Latency for mweb.co.za
Code: 
StartOn			Target		MaxLatency
2016-09-14 18:27:13.65	www.mweb.co.za	27
2016-09-14 18:57:09.55	www.mweb.co.za	24
2016-09-14 19:27:09.723	www.mweb.co.za	40
2016-09-14 19:57:10.127	www.mweb.co.za	98
2016-09-14 20:27:12.167	www.mweb.co.za	33
2016-09-14 20:42:09.553	www.mweb.co.za	85
2016-09-14 21:12:12.563	www.mweb.co.za	110
2016-09-14 21:42:09.773	www.mweb.co.za	80
2016-09-14 22:12:05.507	www.mweb.co.za	69
2016-09-14 22:42:12.1	www.mweb.co.za	35
2016-09-14 23:12:10.273	www.mweb.co.za	35
2016-09-14 23:42:09.757	www.mweb.co.za	34
 
Youtube was just not working last night. I gave up and switched back to another ISP.

Websites also took forever to load.
Speed test showed that it was going fine, but it seems that web pages just took forever to start loading, but once it started it load it was fast.

If afrihost says that there is no load issues due to the R1, and that this is how their network is normally - then I'm going to have to back to my old ISP - the quality isn't great.
 
Maybe Afriguy would like to explain why their state of the art network crashed last night. Also why it is not indicated on your network status page.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X