Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Did something change on the network last night around 23:30 to be exact? My smokeping graphs all of a sudden show the 90%+ packet drops stopped, and now its down to 0% packet loss. Initially latency was high, but it gradually came down to a perfect number. Definitely looks like something was fixed somewhere.
 
Kosmik said:
No. I logged a ticket and a tech reset the account. The server immediately connected and started processing. Considering that I could game, browse and stream and ONLY the 119 was blocked BEFORE the reset, points at a direct traffic issue on your network.
Click to expand...

The account reset simply refreshed the radius server, it doesn't affect any policies or anything like that. If he disconnected your session before doing that (which is usually the process) then the session would just have been re-established at the exchange and then our network
 
rhodad said:
After an up and down conversation with AfriGuy, trying to convince him that something is wrong with my line on AH side, he asks me for results from a vendor neutral site - Well, here they are.
This is becoming ridiculous now......

AH Ping
Code: 
Pinging www.mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=67ms TTL=51
Reply from 197.242.89.170: bytes=32 time=128ms TTL=51
Reply from 197.242.89.170: bytes=32 time=89ms TTL=51
Reply from 197.242.89.170: bytes=32 time=93ms TTL=51
Ping statistics for 197.242.89.170:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 67ms, Maximum = 128ms, Average = 94ms

Web Africa Ping
Code: 
Pinging www.mybroadband.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=39ms TTL=50
Reply from 197.242.89.170: bytes=32 time=40ms TTL=50
Reply from 197.242.89.170: bytes=32 time=44ms TTL=50
Reply from 197.242.89.170: bytes=32 time=41ms TTL=50
Ping statistics for 197.242.89.170:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 44ms, Average = 41ms

AH Trace
Code: 
Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:
  1     4 ms     1 ms     1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3   107 ms   109 ms    83 ms  41.181.221.253
  4   123 ms   113 ms   117 ms  41.181.221.254
  5    77 ms   145 ms    98 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
  6    80 ms    87 ms    56 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   106 ms    64 ms    45 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
  8    54 ms    98 ms    48 ms  196.44.0.74
  9   104 ms   100 ms    86 ms  africainx.cinx.net.za [196.223.22.47]
 10    56 ms    86 ms    53 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
 11   145 ms   100 ms   106 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
 12    96 ms   131 ms   121 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
 13    64 ms   111 ms    86 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
 14    72 ms   104 ms    71 ms  197.242.89.170
Trace complete.

Web Africa Trace
Code: 
Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:
  1     1 ms     2 ms     1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3    21 ms    83 ms    13 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
  4    12 ms    13 ms    13 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    13 ms    12 ms    13 ms  196.35.115.136
  6    13 ms    13 ms    16 ms  mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1
3]
  7    13 ms    13 ms    12 ms  css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
  8    12 ms    12 ms    33 ms  196.36.84.154
  9    50 ms    40 ms    38 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
 10    53 ms    50 ms    45 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
 11    51 ms    44 ms    40 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
 12    45 ms    42 ms    51 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
 13    40 ms    40 ms    39 ms  www.mybroadband.co.za [197.242.89.170]
Trace complete.

Come now man!
Click to expand...

Looking at your tests, I can see that the latency is occuring on all your accounts. This is definitely not ISP specific :(
 
AfriMan said:
The account reset simply refreshed the radius server, it doesn't affect any policies or anything like that. If he disconnected your session before doing that (which is usually the process) then the session would just have been re-established at the exchange and then our network
Click to expand...

But with a different IP. I didn't actually reset my router as I only saw the message later and I was busy in a offline game at the time. I did see a notification from my PC that my public IP had changed and that was when I was able to process 119 traffic again.

This is NOT a local issue to my internal workings as it has been running for years. These issues only started this month when I switched the account.
 
Tinuva said:
Did something change on the network last night around 23:30 to be exact? My smokeping graphs all of a sudden show the 90%+ packet drops stopped, and now its down to 0% packet loss. Initially latency was high, but it gradually came down to a perfect number. Definitely looks like something was fixed somewhere.
Click to expand...

That seems to be when we see demand rapidly drop off in the South. The exact time depends on demand, but it's pretty much what I've seen on our bandwidth reports.
 
Kosmik said:
But with a different IP. I didn't actually reset my router as I only saw the message later and I was busy in a offline game at the time. I did see a notification from my PC that my public IP had changed and that was when I was able to process 119 traffic again.

This is NOT a local issue to my internal workings as it has been running for years. These issues only started this month when I switched the account.
Click to expand...

It could be something to do with the IP range, but that would be at the service provider/server, not something we would enforce. It could be a new range added (we add new IPs regularly) that the NNTP SP doesn't not recognise.
 
AfriMan said:
Looking at your tests, I can see that the latency is occuring on all your accounts. This is definitely not ISP specific :(
Click to expand...

I don't quite understand.
Where is the latency on the WA account?
Also, even if there is latency on both - Why is the WA account outperforming the AH account by so much?
 
Last edited:
rhodad said:
I don't quite understand.
Where is their latency on the WA account?
Also, even if there is latency on both - Why is the WA account outperforming the AH account by so much?
Click to expand...

I think Afriman may have read through your tests too quickly. The latency difference is quite clear.
 
The people have spoken Afrihost! Strange how ISP of the year has dropped so far down! Do you still believe all the issues are "no so bad"?

Screen Shot 2015-04-21 at 10.56.00 AM.jpg

Screen Shot 2015-04-21 at 10.56.17 AM.jpg
 
DrJohnZoidberg said:
I think Afriman may have read through your tests too quickly. The latency difference is quite clear.
Click to expand...

rhodad said:
I don't quite understand.
Where is the latency on the WA account?
Also, even if there is latency on both - Why is the WA account outperforming the AH account by so much?
Click to expand...

This was you posted result for other ISP:

Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 21 ms 83 ms 13 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
4 12 ms 13 ms 13 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 13 ms 12 ms 13 ms 196.35.115.136
6 13 ms 13 ms 16 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1
3]
7 13 ms 13 ms 12 ms css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
8 12 ms 12 ms 33 ms 196.36.84.154
9 50 ms 40 ms 38 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
10 53 ms 50 ms 45 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 51 ms 44 ms 40 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 45 ms 42 ms 51 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 40 ms 40 ms 39 ms www.mybroadband.co.za [197.242.89.170]
Trace complete.

May not be as pronounced but remember that you also resync your account every time you switch ISP accounts (unless you are using PPPoE passthrough which I don't recommend for this type of testing)
 
AfriMan said:
This was you posted result for other ISP:

Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 21 ms 83 ms 13 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
4 12 ms 13 ms 13 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 13 ms 12 ms 13 ms 196.35.115.136
6 13 ms 13 ms 16 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1
3]
7 13 ms 13 ms 12 ms css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
8 12 ms 12 ms 33 ms 196.36.84.154
9 50 ms 40 ms 38 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
10 53 ms 50 ms 45 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 51 ms 44 ms 40 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 45 ms 42 ms 51 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 40 ms 40 ms 39 ms www.mybroadband.co.za [197.242.89.170]
Trace complete.

May not be as pronounced but remember that you also resync your account every time you switch ISP accounts (unless you are using PPPoE passthrough which I don't recommend for this type of testing)
Click to expand...

So that's it? Not an AH problem??
Shocking!
 
Thi is the kind of support i get from Critical care the answer say knothing copy past

Hi Thorsten

Pranav here from Afrihost Critical Care.

I have checked with our technical team and they are still monitoring network,
Changes will be made if they feel its necessary.

I'll keep you posted as I have more information.
 
AfriMan said:
This was you posted result for other ISP:

Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 21 ms 83 ms 13 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
4 12 ms 13 ms 13 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 13 ms 12 ms 13 ms 196.35.115.136
6 13 ms 13 ms 16 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1
3]
7 13 ms 13 ms 12 ms css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
8 12 ms 12 ms 33 ms 196.36.84.154
9 50 ms 40 ms 38 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
10 53 ms 50 ms 45 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 51 ms 44 ms 40 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 45 ms 42 ms 51 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 40 ms 40 ms 39 ms www.mybroadband.co.za [197.242.89.170]
Trace complete.

May not be as pronounced but remember that you also resync your account every time you switch ISP accounts (unless you are using PPPoE passthrough which I don't recommend for this type of testing)
Click to expand...

I'd ask to rerun the test. There is one ping that is higher than the rest there, may just have been an anomaly. On the AH test basically all the pings are high.
 
DrJohnZoidberg said:
I'd ask to rerun the test. There is one ping that is higher than the rest there, may just have been an anomaly. On the AH test basically all the pings are high.
Click to expand...

That's what I noticed as well - Just seems that I'm getting the shrug off here..
Anyway, suppose I'm gonna have to reboot my router, run the test with the AH account, reboot again and run it with the WA account - Can guarantee that the results will reflect the same.
I don't know to what lengths I have to go to get AH to take me seriously - This is really ridiculous.
Seems like they look for any inkling of latency in the competitor account to push the fault away
 
rhodad said:
So that's it? Not an AH problem??
Shocking!
Click to expand...

In all the tests you've posted there had been consistent latency, and that is a massive difference.

You can run the tests again, but you've posted several which shows the same pattern to varying degrees. I honestly do believe this is not ISP specific, and the results do support that. A jump in latency of even 10 or 20ms might be less prominent, but that tells me there is definitely another issue here.
 
DrJohnZoidberg said:
I'd ask to rerun the test. There is one ping that is higher than the rest there, may just have been an anomaly. On the AH test basically all the pings are high.
Click to expand...

Check back to an earlier post where the results we more consistent across both ISP accounts. I think the anomaly, from the results posted, is that the problem seems less severe at times. Just going by the posts I've seen.
 
AfriMan said:
In all the tests you've posted there had been consistent latency, and that is a massive difference.

You can run the tests again, but you've posted several which shows the same pattern to varying degrees. I honestly do believe this is not ISP specific, and the results do support that. A jump in latency of even 10 or 20ms might be less prominent, but that tells me there is definitely another issue here.
Click to expand...

I've posted results twice, including this one.
So the latency is lacking on the 3rd hop across the board (worse on AH) - What about the rest of the hops? It's clear as day that the WA account is performing much better than the AH account

So, if I reboot my router before the AH test and before the WA test and the results are the same - This would mean that the WA account is still by far outperforming the AH account, correct? What then?
Even with my limited knowledge, it's beyond me how you can shrug it off by picking out 1 slightly high latency ping in a series of 42 pings whereas the AH account's latency is through the roof on most of the pings. (Each line in a hop in a trace route represents a ping, right?)
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X