Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
One of the major technology universities (can't remember which) issued an communique on this. It seems it was related to UDP on an extension and was causing Google services in particular to act weird. Dunno if they fixed it on their side.

Best you find that link.
 
As far as we know it was related to a Chrome plug-in or extension. We didn't make any changes for the issue to be resolved.

No. It was not related to a plugin. If we are talking about the same user.

And the only problem related to UDP that Chrome has had was back in 2010 - which was a security and port problem which was fixed shortly after being reported.

I suggested a browser switch to the user because I had the same problems on your network only - not a perfect solution but then again I could not wait for you guys to fix it. This happens on Chrome on uncapped accounts when shaping is active btw. Does not happen often, but it does happen. I even reported this in a various tickets 2 years ago when Chrome was making the switch to HTML 5. Promises of it being investigated. Seems nothing happened relating to those claims.
 
No. It was not related to a plugin. If we are talking about the same user.

And the only problem related to UDP that Chrome has had was back in 2010 - which was a security and port problem which was fixed shortly after being reported.

I suggested a browser switch to the user because I had the same problems on your network only - not a perfect solution but then again I could not wait for you guys to fix it. This happens on Chrome on uncapped accounts when shaping is active btw. Does not happen often, but it does happen. I even reported this in a various tickets 2 years ago when Chrome was making the switch to HTML 5. Promises of it being investigated. Seems nothing happened relating to those claims.

We saw several reports from clients mostly last week, and they issues went away without us having to make any changes so I can only assume that Chrome pushed out an update (though I don't know of one specifically) or changed something on their side.
 
We saw several reports from clients mostly last week, and they issues went away without us having to make any changes so I can only assume that Chrome pushed out an update (though I don't know of one specifically) or changed something on their side.

Not getting involved in an argument with you.

Those problems are not resolved by the way and they will occur again. That is the nature of an intermittent issue which exists on, you guessed it, your network only.

But of course nothing is wrong on your network. Just like how people cannot play games or stream realtime content the last three and half months and must just wait for these fixes to come - which they still have not. Contention issues? Of course they don't exist. Pfff. Just look at the network status indicator. All green. Good to go. All these complaints must be the user, the browser, the exchange or their imagination right?

Whatever. Glad I moved to a network that works and that I could at least help one user while he still struggles with you.
 
Are you using Chrome by any chance? There have been significant issues with Chrome over the past few days, and Google is busy investigating the cause.

Unless you have contacted Google directly they are not investigating anything related according to the support groups.
The most relevant issues were posted in 2013 and in 2014, both were related to Googles own "pepper flash" plugin.
Disabling "pepper flash" resolved any conflict with Adobe Flash.
That issue has not recurred since mid 2014, and is not the course of current issues on AH, I know, It is the first thing I looked for.
 
Not getting involved in an argument with you.

Those problems are not resolved by the way and they will occur again. That is the nature of an intermittent issue which exists on, you guessed it, your network only.

But of course nothing is wrong on your network. Just like how people cannot play games or stream realtime content the last three and half months and must just wait for these fixes to come - which they still have not. Contention issues? Of course they don't exist. Pfff. Just look at the network status indicator. All green. Good to go. All these complaints must be the user, the browser, the exchange or their imagination right?

Whatever. Glad I moved to a network that works and that I could at least help one user while he still struggles with you.

I can't take ownership of a problem we don't believe it not specific to us. From the reports we saw, it was happening only on Chrome, but to not only to Afrihost users.
 
Unless you have contacted Google directly they are not investigating anything related according to the support groups.
The most relevant issues were posted in 2013 and in 2014, both were related to Googles own "pepper flash" plugin.
Disabling "pepper flash" resolved any conflict with Adobe Flash.
That issue has not recurred since mid 2014, and is not the course of current issues on AH, I know, It is the first thing I looked for.

I'm not sure what the plug-in that was mentioned but we certainly didn't change anything on our side for the problem to go away for all the users that reported the anomaly. If the problem was on our network, every Chrome user would have experienced this. It seemed to relate only to a subset of users with certain extensions active.
 
I can't take ownership of a problem we don't believe it not specific to us. From the reports we saw, it was happening only on Chrome, but to not only to Afrihost users.

We really would appreciate it if you could link to those reports for us.
This morning even trying to type a reply in GMail is slow and Google Docs is very sluggish.
I have been trawling the usual Google Support Forums, both official and user, and have found no current issues.
I expect to start getting calls from my clients soon if it persists and will let you know if it is only the ones on AH complaining or if it is across the board.
 
We really would appreciate it if you could link to those reports for us.
This morning even trying to type a reply in GMail is slow and Google Docs is very sluggish.
I have been trawling the usual Google Support Forums, both official and user, and have found no current issues.
I expect to start getting calls from my clients soon if it persists and will let you know if it is only the ones on AH complaining or if it is across the board.

So does this only happen in Chrome for you, or on all browsers? Just want to make sure we are discussing the same topic here.
 
I only have Chrome installed at the moment, or at least have only tried it with chrome, as it is the best platform for integrating Google docs. I can try later with Firefox but need to get some documentation finished before I have time to start testing again.
I may also switch to a backup account and see if it persists on another ISP, but for now I have to live with it.
 
We really would appreciate it if you could link to those reports for us.
This morning even trying to type a reply in GMail is slow and Google Docs is very sluggish.
I have been trawling the usual Google Support Forums, both official and user, and have found no current issues.
I expect to start getting calls from my clients soon if it persists and will let you know if it is only the ones on AH complaining or if it is across the board.

Can't find any links but here were reports from clients to that effect via various channels:

9YADj4N.png


YVMAWeo.png
 
Thanks, but I don't use AddBlock or AddBlock Plus, the only other extensions I have loaded are my VPN which is disabled when not needed, i.e. most of the time, and the various Google Docs Plugins that I use for work.
Strange that the university is sending out email about the issue but have not posted an issue on the Google support Forums or Issue Logging System. They normally follow procedure if it is identified by the IT department.
 
What are these speeds on a 20Mb/s capped line? My line can never run fully for a full day.
http://speedtest.ookla.com/result/2864365253.png




Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=28 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=70 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=28 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=97 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=110 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=94 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=83 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=47 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=57 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=59 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1.788 ms 5.25 ms 2.259 ms
2 105.236.14.65 16.482 ms 71.159 ms 55.309 ms
3 41.181.178.53 25.807 ms 64.809 ms 71.198 ms
4 196.44.0.146 24.523 ms 72.311 ms 67.007 ms
5 196.44.0.42 33.039 ms 94.186 ms
196.44.31.95 64.521 ms
6 41.181.165.115 34.41 ms 22.117 ms 74.135 ms
7 196.44.31.99 18.022 ms 21.693 ms 40.139 ms
8 196.31.220.8 21.406 ms 17.246 ms 31.323 ms
9 196.31.220.27 26.523 ms
196.31.220.23 20.747 ms 46.822 ms
10 196.31.63.206 18.198 ms 39.326 ms
196.31.63.202 25.317 ms
11 196.30.42.133 13.041 ms 21.481 ms 64.526 ms
12 197.242.144.102 37.238 ms 21.638 ms 104.208 ms


traceroute -n 8.8.8.8

1 192.168.1.1 1.693 ms 2.802 ms 4.529 ms
2 105.236.14.65 75.942 ms 35.11 ms 42.792 ms
3 41.181.178.53 66.159 ms 31.257 ms 42.948 ms
4 196.44.31.120 50.602 ms 33.596 ms
196.44.0.146 43.081 ms
5 196.44.31.171 29.172 ms
196.44.0.42 33.658 ms 53.231 ms
6 41.181.165.115 43.177 ms 83.504 ms 53.711 ms
7 196.44.0.43 32.855 ms 110.524 ms 55.468 ms
8 41.181.139.99 112.622 ms 108.291 ms 52.372 ms
9 72.14.194.74 91.42 ms 82.813 ms 62.537 ms
10 72.14.239.117 84.299 ms
72.14.239.35 43.183 ms
72.14.239.33 56.054 ms
11 8.8.8.8 72.383 ms 48.915 ms 48.419 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 41.76.227.137


nslookup www.google.com

Name: www.google.com
Address: 216.58.223.36


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
What are these speeds on a 20Mb/s capped line? My line can never run fully for a full day.
http://speedtest.ookla.com/result/2864365253.png




Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=28 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=70 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=28 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=97 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=110 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=94 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=83 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=47 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=57 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=59 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1.788 ms 5.25 ms 2.259 ms
2 105.236.14.65 16.482 ms 71.159 ms 55.309 ms
3 41.181.178.53 25.807 ms 64.809 ms 71.198 ms
4 196.44.0.146 24.523 ms 72.311 ms 67.007 ms
5 196.44.0.42 33.039 ms 94.186 ms
196.44.31.95 64.521 ms
6 41.181.165.115 34.41 ms 22.117 ms 74.135 ms
7 196.44.31.99 18.022 ms 21.693 ms 40.139 ms
8 196.31.220.8 21.406 ms 17.246 ms 31.323 ms
9 196.31.220.27 26.523 ms
196.31.220.23 20.747 ms 46.822 ms
10 196.31.63.206 18.198 ms 39.326 ms
196.31.63.202 25.317 ms
11 196.30.42.133 13.041 ms 21.481 ms 64.526 ms
12 197.242.144.102 37.238 ms 21.638 ms 104.208 ms


traceroute -n 8.8.8.8

1 192.168.1.1 1.693 ms 2.802 ms 4.529 ms
2 105.236.14.65 75.942 ms 35.11 ms 42.792 ms
3 41.181.178.53 66.159 ms 31.257 ms 42.948 ms
4 196.44.31.120 50.602 ms 33.596 ms
196.44.0.146 43.081 ms
5 196.44.31.171 29.172 ms
196.44.0.42 33.658 ms 53.231 ms
6 41.181.165.115 43.177 ms 83.504 ms 53.711 ms
7 196.44.0.43 32.855 ms 110.524 ms 55.468 ms
8 41.181.139.99 112.622 ms 108.291 ms 52.372 ms
9 72.14.194.74 91.42 ms 82.813 ms 62.537 ms
10 72.14.239.117 84.299 ms
72.14.239.35 43.183 ms
72.14.239.33 56.054 ms
11 8.8.8.8 72.383 ms 48.915 ms 48.419 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 41.76.227.137


nslookup www.google.com

Name: www.google.com
Address: 216.58.223.36


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

There's definitely something wrong here :(
Results like this usually indicate a line issue, drop me a PM with the number and I can take a closer look at this for you.
 
All these complaints coming through with similar issues are you 100% sure IPC is not an issue? Sure looks like it.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X