Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
Please introduce me to these people. I think it would be great to have access to this kind of info for clients experiencing congestion. Though, I'm curious when the capacity of the exchange does not match the physical infrastructure/backhaul capacity (in terms of DP's, etc). What device is being measured here? From the BNG in the description, I'm guessing this is a new Broadband Network Gateway (upgraded BRAS) and not the DSLAM or MSAN itself, which explains why the capacity shows as high, when my experience is that various Bellvile exchanges are notorious for being congested.

Would love to know more about what we're actually looking at here :)

It's a contact at telkom. Im sure as an ISP if you guys request the info from specific exchanges they will ablige? Otherwise there is something very wrong within the contract between ISP and Telkom
 
It's a contact at telkom. Im sure as an ISP if you guys request the info from specific exchanges they will ablige? Otherwise there is something very wrong within the contract between ISP and Telkom

I've used the tool previously, it is quite locked down though :)
 
I've used the tool previously, it is quite locked down though :)

Well can you imagine if every support request to any ISP start with the support team running such a query on every exchange? :P
 
Well can you imagine if every support request to any ISP start with the support team running such a query on every exchange? :P

The world has moved on, looking at info like that is really easy these days - and you can do it without paying a cent for it, like a simple elastic/kibana/logstash stack.

Like I've said many times before, SA is really far behind what the rest of the world considers norm.
 
The site itself loads up OK for me, are you having issues streaming content?

Gets to landing page and half the content doesn't even load. Clicking on the links opens another tab and then that's all, page eventually times out. Switch to different ISP and loads in seconds with no hassles.
 
Gets to landing page and half the content doesn't even load. Clicking on the links opens another tab and then that's all, page eventually times out. Switch to different ISP and loads in seconds with no hassles.

That's very strange. Do you have some links for me to test? I've been browsing around http://www.skysports.com/ which loads up nearly instantly for me.
 
Sorry to hear about the issues here :(
I ran a few tests on our news server earlier on and didn't seem to have any issues. Are you not getting any throughput?

Yes. This was between 6 and 7:30am this morning, left for work but I see nntp had died and nothing come through in the early morning. I'll check again once home later.
 
Yes. This was between 6 and 7:30am this morning, left for work but I see nntp had died and nothing come through in the early morning. I'll check again once home later.

Was this using our news server?
Keep me posted when you're home :)
 
Flaky performance in the South again today... packet loss and throughput down on Afrihost accounts.

4377963112.png


Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   22 |    0 |    0 |    0 |    0 |    0 |
|                          41.181.221.253 -    2 |  101 |   99 |   22 |  108 |  826 |   63 |
|                          41.181.221.254 -    2 |  101 |   99 |   21 |   77 |  775 |   24 |
|   tb-dca-2.za--qux-c.za.mtnbusiness.net -    2 |  101 |   99 |   21 |   78 |  774 |   22 |
|                     unc-cpt-1.mtnns.net -    2 |  101 |   99 |   21 |   76 |  826 |   24 |
|        jh-cr-1.za--tb-cr-2.za.mtnns.net -    4 |   97 |   94 |   41 |   69 |  784 |   42 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    1 |  105 |  104 |   40 |  103 |  793 |   41 |
|       18.185.181.41.in-addr.aserv.co.za -    0 |  108 |  108 |   41 |  124 |  833 |   41 |
|________________________________________________|______|______|______|______|______|______|



4377972968.png


Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|       cdsl2-ctn-vl2473-ipc.ip.isnet.net -    0 |  101 |  101 |   23 |   68 |   74 |   38 |
|            vlan2473.cdsl2-ctn.isdsl.net -    0 |  101 |  101 |   22 |   31 |   89 |   42 |
|                          196.35.115.136 -    0 |  101 |  101 |   23 |   33 |  100 |   43 |
|     mi-za-cpt-p8-te0-0-0-0.ip.isnet.net -    0 |  101 |  101 |   21 |   30 |   89 |   26 |
|                           168.209.6.130 -    0 |  101 |  101 |   21 |   30 |   88 |   27 |
|                 41-208-29-210.mtnns.net -    0 |  101 |  101 |   21 |   33 |   88 |   43 |
|       rb-cr-1.za.nl-ha-2.za-a.mtnns.net -    0 |  101 |  101 |   23 |   34 |   85 |   27 |
|      tb-cr-2.za--ct-cr-1.za-a.mtnns.net -    0 |  101 |  101 |   22 |   32 |   85 |   26 |
|        jh-cr-1.za--tb-cr-2.za.mtnns.net -    0 |  101 |  101 |   42 |   53 |  107 |   47 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    0 |  101 |  101 |   41 |   53 |  136 |   60 |
|       18.185.181.41.in-addr.aserv.co.za -    0 |  101 |  101 |   40 |   50 |  106 |   46 |
|________________________________________________|______|______|______|______|______|______|
 
Flaky performance in the South again today... packet loss and throughput down on Afrihost accounts.

4377963112.png


Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   22 |    0 |    0 |    0 |    0 |    0 |
|                          41.181.221.253 -    2 |  101 |   99 |   22 |  108 |  826 |   63 |
|                          41.181.221.254 -    2 |  101 |   99 |   21 |   77 |  775 |   24 |
|   tb-dca-2.za--qux-c.za.mtnbusiness.net -    2 |  101 |   99 |   21 |   78 |  774 |   22 |
|                     unc-cpt-1.mtnns.net -    2 |  101 |   99 |   21 |   76 |  826 |   24 |
|        jh-cr-1.za--tb-cr-2.za.mtnns.net -    4 |   97 |   94 |   41 |   69 |  784 |   42 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    1 |  105 |  104 |   40 |  103 |  793 |   41 |
|       18.185.181.41.in-addr.aserv.co.za -    0 |  108 |  108 |   41 |  124 |  833 |   41 |
|________________________________________________|______|______|______|______|______|______|



4377972968.png


Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|       cdsl2-ctn-vl2473-ipc.ip.isnet.net -    0 |  101 |  101 |   23 |   68 |   74 |   38 |
|            vlan2473.cdsl2-ctn.isdsl.net -    0 |  101 |  101 |   22 |   31 |   89 |   42 |
|                          196.35.115.136 -    0 |  101 |  101 |   23 |   33 |  100 |   43 |
|     mi-za-cpt-p8-te0-0-0-0.ip.isnet.net -    0 |  101 |  101 |   21 |   30 |   89 |   26 |
|                           168.209.6.130 -    0 |  101 |  101 |   21 |   30 |   88 |   27 |
|                 41-208-29-210.mtnns.net -    0 |  101 |  101 |   21 |   33 |   88 |   43 |
|       rb-cr-1.za.nl-ha-2.za-a.mtnns.net -    0 |  101 |  101 |   23 |   34 |   85 |   27 |
|      tb-cr-2.za--ct-cr-1.za-a.mtnns.net -    0 |  101 |  101 |   22 |   32 |   85 |   26 |
|        jh-cr-1.za--tb-cr-2.za.mtnns.net -    0 |  101 |  101 |   42 |   53 |  107 |   47 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    0 |  101 |  101 |   41 |   53 |  136 |   60 |
|       18.185.181.41.in-addr.aserv.co.za -    0 |  101 |  101 |   40 |   50 |  106 |   46 |
|________________________________________________|______|______|______|______|______|______|

Sorry to hear you're seeing issue here :( The South IPC looks quite good today, shouldn't be any general issues from our end.
Just ran a test from my place, also in Wynberg CPT and seems OK.

4378001997.png


Are these issues replicated when using another network too?
 
Sorry to hear you're seeing issue here :( The South IPC looks quite good today, shouldn't be any general issues from our end.
Just ran a test from my place, also in Wynberg CPT and seems OK.

4378001997.png


Are these issues replicated when using another network too?

Other networks are OK... just AH suffers.
 
Afrihost. Please sort your **** out. Seriously, only you guys can break the most easily accessible service online. Once again, for the 50th time, no Google services are available. This is getting so bad, we have honestly started looking into alternatives for our client base (we spend around 60k a month). Over this rubbish.
 
Afrihost. Please sort your **** out. Seriously, only you guys can break the most easily accessible service online. Once again, for the 50th time, no Google services are available. This is getting so bad, we have honestly started looking into alternatives for our client base (we spend around 60k a month). Over this rubbish.

Sorry to hear about the issues.
Google services should be fine on the network. If however, you're using Chrome - please try and make these changes.

For those of you having trouble with Google services and Chrome:

open a new tab and go to chrome://flags/
Find "Experimental QUIC protocol."
Set it to "Disabled" instead of "Default"

Boom, Google services working again. This was driving me nuts the past few days, and appears to be related to Google switching this protocol on for their services and having it enabled by default in Chrome. Not sure what the benefit is supposed to be, but clearly something's buggy with it right now and disabling it has no negative effects.
 
Sorry to hear about the issues.
Google services should be fine on the network. If however, you're using Chrome - please try and make these changes.

Do you have an explanation as to why your network is breaking this protocol? It only happens on your network. This protocol is meant to add quicker connections and more security, but you guys have something in place that is breaking this protocol. Are you intercepting user packets for monitoring or something?
 
Do you have an explanation as to why your network is breaking this protocol? It only happens on your network. This protocol is meant to add quicker connections and more security, but you guys have something in place that is breaking this protocol. Are you intercepting user packets for monitoring or something?

QUIC is an experimental protocol run by Google, so I'm not sure it'll be working as it should, all the time.
We've run extensive checks on our end - this isn't something that can be fixed on our network.
 
My router gets reset twice in a row while I'm in a rank match, when it finally done, suddenly got 50% packet loss and I just ruined 4 people time in a online match. Really this should have been fixed long time ago.
 
My router gets reset twice in a row while I'm in a rank match, when it finally done, suddenly got 50% packet loss and I just ruined 4 people time in a online match. Really this should have been fixed long time ago.

:(

Are you able to check if the ADSL line dropped the connection, or your ADSL account itself dropped the connection?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X