Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
Please assist....

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=2096ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1535ms TTL=51
Reply from 197.242.89.170: bytes=32 time=695ms TTL=51
Request timed out.

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=31ms TTL=50
Reply from 197.242.89.170: bytes=32 time=36ms TTL=50
Reply from 197.242.89.170: bytes=32 time=31ms TTL=50
Reply from 197.242.89.170: bytes=32 time=40ms TTL=50

AH Trace
Code:
Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3   176 ms   192 ms   195 ms  41.181.53.213
  4   240 ms   101 ms    99 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
  5    61 ms    42 ms   104 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
  6   162 ms   181 ms   299 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   155 ms   142 ms   139 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

  8   210 ms   175 ms   169 ms  196.44.0.74
  9     *      124 ms   120 ms  africainx.cinx.net.za [196.223.22.47]
10   296 ms   397 ms     *     CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
11     *      297 ms   229 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12   219 ms   252 ms   253 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13   368 ms   217 ms    87 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14   248 ms   326 ms   342 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    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3    58 ms   136 ms   132 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
  4    48 ms    12 ms    11 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    38 ms    12 ms    11 ms  196.35.115.136
  6    13 ms    12 ms    12 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.1
3]
  7    12 ms    13 ms    13 ms  css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
  8    12 ms    11 ms    11 ms  196.36.84.154
  9    29 ms    30 ms    31 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
10    46 ms    31 ms    30 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11    30 ms    32 ms    42 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12    39 ms    32 ms    33 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13    30 ms    30 ms    29 ms  197.242.89.170

Trace complete.

Please don't tell me that you are seeing latency across both accounts, it's very clear that one is outperforming the other..
 
Please assist....

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=2096ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1535ms TTL=51
Reply from 197.242.89.170: bytes=32 time=695ms TTL=51
Request timed out.

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=31ms TTL=50
Reply from 197.242.89.170: bytes=32 time=36ms TTL=50
Reply from 197.242.89.170: bytes=32 time=31ms TTL=50
Reply from 197.242.89.170: bytes=32 time=40ms TTL=50

AH Trace
Code:
Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3   176 ms   192 ms   195 ms  41.181.53.213
  4   240 ms   101 ms    99 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
  5    61 ms    42 ms   104 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
  6   162 ms   181 ms   299 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   155 ms   142 ms   139 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

  8   210 ms   175 ms   169 ms  196.44.0.74
  9     *      124 ms   120 ms  africainx.cinx.net.za [196.223.22.47]
10   296 ms   397 ms     *     CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
11     *      297 ms   229 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12   219 ms   252 ms   253 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13   368 ms   217 ms    87 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14   248 ms   326 ms   342 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    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3  [B]  58 ms   136 ms   132 ms [/B] cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
  4    [B]48 ms[/B]    12 ms    11 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    [B]38 ms [/B]   12 ms    11 ms  196.35.115.136
  6    13 ms    12 ms    12 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.1
3]
  7    12 ms    13 ms    13 ms  css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
  8    12 ms    11 ms    11 ms  196.36.84.154
  9    29 ms    30 ms    31 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
10    46 ms    31 ms    30 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11    30 ms    32 ms    42 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12    39 ms    32 ms    33 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13    30 ms    30 ms    29 ms  197.242.89.170

Trace complete.

Please don't tell me that you are seeing latency across both accounts, it's very clear that one is outperforming the other..

There is certainly latency across both accounts here, I can't not point that out. And it's more than negligible, there is a demonstrable pattern here that definitely indiciates something on the line. Granted, its much worse on our account, but also testing at 8am when traffic spikes as business go online is never a great indicator, unless you are specifically testing for that. You will generally see a period of 5-10 minutes when demand increases rapidly and our network recovers. It may even be the case with the other ISP network you are testing with.
 
There is certainly latency across both accounts here, I can't not point that out. And it's more than negligible, there is a demonstrable pattern here that definitely indiciates something on the line. Granted, its much worse on our account, but also testing at 8am when traffic spikes as business go online is never a great indicator, unless you are specifically testing for that. You will generally see a period of 5-10 minutes when demand increases rapidly and our network recovers. It may even be the case with the other ISP network you are testing with.

I did this test at 7pm yesterday evening.
So what's next?
Do we get Telkom involved again or do we wait until the AH account returns results similar to my WA account? As far as I can see, there are definitely issues on the AH account.
 
I did this test at 7pm yesterday evening.
So what's next?
Do we get Telkom involved again or do we wait until the AH account returns results similar to my WA account? As far as I can see, there are definitely issues on the AH account.

I get similar results between 16:00 - 18:00 in the afternoon, business must also go online then and spike the line :wtf:
 
I get similar results between 16:00 - 18:00 in the afternoon, business must also go online then and spike the line :wtf:

I see this type of results almost every time I run a test.
I don't know what I need to do to convince AH that there is a clear problem on their line, they seem to latch onto the fact that there is also a bit of latency on the other account but it's clear as day that there are issues on the AH line which they need to sort out. The WA account is miles ahead of the AH account.
 
I see this type of results almost every time I run a test.
I don't know what I need to do to convince AH that there is a clear problem on their line, they seem to latch onto the fact that there is also a bit of latency on the other account but it's clear as day that there are issues on the AH line which they need to sort out. The WA account is miles ahead of the AH account.

Both accounts show significantly high latency on the 2nd hop though, would be a different story if our account showed high latency and the other was a stable 30ms across the board. I'm afraid it's not, which to me, indicates issues on the exchange :(
 
Both accounts show significantly high latency on the 2nd hop though, would be a different story if our account showed high latency and the other was a stable 30ms across the board. I'm afraid it's not, which to me, indicates issues on the exchange :(

So, you're saying that the AH line is performing as it should, seriously???
What about after the 2nd hop??
Are you telling me that there is no way that the WA account is outperforming the AH account?
Look at the rest of the trace, after the 2nd hop.
I'm sorry but the fact that you can't see that there are problems on the AH account shows me that you guys are deliberately being obtuse.
 
So, you're saying that the AH line is performing as it should, seriously???
What about after the 2nd hop??
Are you telling me that there is no way that the WA account is outperforming the AH account?
Look at the rest of the trace, after the 2nd hop.
I'm sorry but the fact that you can't see that there are problems on the AH account shows me that you guys are deliberately being obtuse.

Both accounts are probably performing as they should, any latency on the 2nd hop will worsen the experience and slow down the rest of the hops.
If you'd like, drop me a PM with your DSL username and I'll run some tests on my home line which will show the account is performing as it should.

Maybe run each account for a few days, without restarting, to get an overall feel for the accounts and line. But again, I need to stress that the results you're posting indicate issues on the exchange.
 
Both accounts are probably performing as they should, any latency on the 2nd hop will worsen the experience and slow down the rest of the hops.
If you'd like, drop me a PM with your DSL username and I'll run some tests on my home line which will show the account is performing as it should.

Maybe run each account for a few days, without restarting, to get an overall feel for the accounts and line. But again, I need to stress that the results you're posting indicate issues on the exchange.

AfriGuy, I don't dispute that there are probably issues on the exchange.
The point I am trying to make is that there is no way that you can tell me that.........

THIS
Code:
  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3   176 ms   192 ms   195 ms  41.181.53.213
  4   240 ms   101 ms    99 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
  5    61 ms    42 ms   104 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
  6   162 ms   181 ms   299 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   155 ms   142 ms   139 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

  8   210 ms   175 ms   169 ms  196.44.0.74
  9     *      124 ms   120 ms  africainx.cinx.net.za [196.223.22.47]
10   296 ms   397 ms     *     CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
11     *      297 ms   229 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12   219 ms   252 ms   253 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13   368 ms   217 ms    87 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14   248 ms   326 ms   342 ms  197.242.89.170

IS THE SAME AS
Code:
  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3    58 ms   136 ms   132 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
  4    48 ms    12 ms    11 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    38 ms    12 ms    11 ms  196.35.115.136
  6    13 ms    12 ms    12 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.1
3]
  7    12 ms    13 ms    13 ms  css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
  8    12 ms    11 ms    11 ms  196.36.84.154
  9    29 ms    30 ms    31 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
10    46 ms    31 ms    30 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11    30 ms    32 ms    42 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12    39 ms    32 ms    33 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13    30 ms    30 ms    29 ms  197.242.89.170

Both accounts are probably performing as they should, any latency on the 2nd hop will worsen the experience and slow down the rest of the hops.
Tell me, why is it not slowing down the rest of the hops on the WA test??

Both accounts are probably performing as they should
How can this be when the one is clearly outperforming the other?
 
Last edited:
AfriGuy, I don't dispute that there are probably issues on the exchange.
The point I am trying to make is that there is no way that you can tell me that.........

THIS
Code:
  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3   176 ms   192 ms   195 ms  41.181.53.213
  4   240 ms   101 ms    99 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
  5    61 ms    42 ms   104 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
  6   162 ms   181 ms   299 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  7   155 ms   142 ms   139 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

  8   210 ms   175 ms   169 ms  196.44.0.74
  9     *      124 ms   120 ms  africainx.cinx.net.za [196.223.22.47]
10   296 ms   397 ms     *     CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
11     *      297 ms   229 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
12   219 ms   252 ms   253 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13   368 ms   217 ms    87 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
14   248 ms   326 ms   342 ms  197.242.89.170

IS THE SAME AS
Code:
  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3    58 ms   136 ms   132 ms  cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
  4    48 ms    12 ms    11 ms  vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
  5    38 ms    12 ms    11 ms  196.35.115.136
  6    13 ms    12 ms    12 ms  mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.1
3]
  7    12 ms    13 ms    13 ms  css1-ctn-gi0-2.ip.isnet.net [168.209.6.10]
  8    12 ms    11 ms    11 ms  196.36.84.154
  9    29 ms    30 ms    31 ms  CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
10    46 ms    31 ms    30 ms  41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11    30 ms    32 ms    42 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12    39 ms    32 ms    33 ms  row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13    30 ms    30 ms    29 ms  197.242.89.170


Tell me, why is it not slowing down the rest of the hops on the WA test??


How can this be when the one is clearly outperforming the other?

Probably due to different IPC layouts. Regardless, the latency is high here.
Drop me a PM with the username and I'll gladly run some tests on your account for you.
 
Seeing improvement in the East. Pings are better and speed is more constant now.

Well done AfriTeam!
 
Probably due to different IPC layouts. Regardless, the latency is high here.
Drop me a PM with the username and I'll gladly run some tests on your account for you.

PM sent
Honestly, I am sick of AH trying to convince me that my AH account is performing as it should when I can see that it isn't.
It's all in the results, forget there might be a problem at my exchange and focus on getting my AH results to replicate my WA results.
Once that's done, we'll tackle Telkom.
 
PM sent
Honestly, I am sick of AH trying to convince me that my AH account is performing as it should when I can see that it isn't.
It's all in the results, forget there might be a problem at my exchange and focus on getting my AH results to replicate my WA results.
Once that's done, we'll tackle Telkom.

Thanks, got your PM :)
Will run some tests and revert with feedback there.
 
Both accounts are probably performing as they should, any latency on the 2nd hop will worsen the experience and slow down the rest of the hops.

So you are saying that an Afrihost account should, by design, have a latency of an order of magnitude higher than a WebAfrica account?

That looks like more of an MTN vs IS backbone issue to me, rather than the accounts performing as they should.
 
So you are saying that an Afrihost account should, by design, have a latency of an order of magnitude higher than a WebAfrica account?

That looks like more of an MTN vs IS backbone issue to me, rather than the accounts performing as they should.

I don't think that's what I said. At least that wasn't the intention :)
 
Just noticed I was charge an admin fee when I was unable to update my credit card details due to an repeatable error on the website....

Very annoying considering how useless the email support is when trying to resolve with them.
1.) They basically ignored my email with details of the problem.
2.) The instructions they replied with were exaxtly the ones I told them wasn't working.

Yesterday I finally received a reply stating that they're closing the ticket because I was finally able to resolve the issue - with absolutely no help from them :mad:

I actually don't know why you guys have support systems like that in place, just about every interaction with them is a serious pain in the arse...days to respond - and usually with something meaningless because they didn't bother reading the initial communication, requiring you to email them again and wait days.
 
Just noticed I was charge an admin fee when I was unable to update my credit card details due to an repeatable error on the website....

Very annoying considering how useless the email support is when trying to resolve with them.
1.) They basically ignored my email with details of the problem.
2.) The instructions they replied with were exaxtly the ones I told them wasn't working.

Yesterday I finally received a reply stating that they're closing the ticket because I was finally able to resolve the issue - with absolutely no help from them :mad:

I actually don't know why you guys have support systems like that in place, just about every interaction with them is a serious pain in the arse...days to respond - and usually with something meaningless because they didn't bother reading the initial communication, requiring you to email them again and wait days.

I've replied to your PM :)
 
As far as I can see latency was solid on the general North region network for pretty much all areas. Did you run any tests at the time to compare? I haven't tested Destiny for ages myself. Will see if I can fire it up and give it a bash as well.

Definitely wasn't solid my side. Changed over to web Africa and had no further issues so no tests were run.

I think in the past month I've sent enough tests to your support?
 
Hi All
Quick question...
I have a 150GB capped 4MB account.
There are 2 people including myself that make use of the internet...
How do I track how much bandwidth the other person is using over a given time (day, month, week etc)?
Is this possible?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X