Afrihost New Network Feedback - Part 3

Status
Not open for further replies.
AfriMan said:
It looks like one test is going local and the other is international. I think the labelling of the routers may be confusing, but when you jump from 20ms to 130ms, you've left the country (if everything is working as it should).
Click to expand...

130ms international is not possible.
 
Last night... Up and down.
I at least could stream. Games were very very unstable
 
AfriMan said:
I'm seeing consistent destination latency at values we'd be pretty happy with. IT's always possible that one hop will respond slower based on how busy that router is - some are obviously going to do more work than others at times.

Did you feel that your experience was poor or are you posting based poorly on the trace results?
Click to expand...

A bit of both, definitely some improvement in certain regards but still experiencing certain issues such as jitter making certain games extremely difficult to play... yet again finding myself having to connect to another ISP account to play CSGO.

I don't necessarily buy 'certain hops will respond slower than others depending on how busy that router is', this clearly shows traffic congestion of some sort at specific points, which will definitely cause issues, 300ms is not normal for an EU hop.

Nor is 170ms fine for local traffic. This does not happen on other ISP's routes because it is not normal.

Please forward my tests to NOC team?
 
Mine was fine last night Ping was even as low as 1ms at one stage with a max of 9ms when I did a speed test. Night before it was in the hundreds.
 
DeatheCore said:
A bit of both, definitely some improvement in certain regards but still experiencing certain issues such as jitter making certain games extremely difficult to play... yet again finding myself having to connect to another ISP account to play CSGO.

I don't necessarily buy 'certain hops will respond slower than others depending on how busy that router is', this clearly shows traffic congestion of some sort at specific points, which will definitely cause issues, 300ms is not normal for an EU hop.

Nor is 170ms fine for local traffic. This does not happen on other ISP's routes because it is not normal.

Please forward my tests to NOC team?
Click to expand...

I definitely don't see anything of concern here, neither do the NOC engineers.

I don't see anything local giving 170ms, except one hop to Mweb, which is within their network, not ours. I think we're very satisfied with the results you've posted, as well as those we've got in our own tests in the South, with other users who test for us.
 
I can confirm that the normal period of latency still existed, but it was much shorter than the norm

Also not sure who's network stops and begins where, but news24 when it's bad
Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    23 ms    19 ms    19 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    19 ms    30 ms    18 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   139 ms   139 ms   151 ms  optinet.ixp.capetown [196.10.140.15] 
  7   157 ms   161 ms   164 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  8    31 ms    36 ms    41 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9    20 ms    20 ms    19 ms  196.28.178.66 
 10   141 ms   131 ms   129 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11    20 ms    31 ms    20 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    21 ms    21 ms    20 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    19 ms    19 ms    19 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Compared to Telkom
Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    19 ms    18 ms    19 ms  105-187-252-54.ti-sen.telkomsa.net [105.187.252.54] 
  5    19 ms    18 ms    18 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  6    19 ms    18 ms    19 ms  blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54] 
  7    19 ms    18 ms    18 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138] 
  8    19 ms    19 ms    22 ms  optinet.ixp.capetown [196.10.140.145] 
  9    22 ms    22 ms    19 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
 10    18 ms    19 ms    19 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
 11    20 ms    20 ms    19 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    19 ms    20 ms    19 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    20 ms    20 ms    20 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 14    52 ms    19 ms    19 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 15    20 ms    20 ms    19 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.
 
standerr said:
I can confirm that the normal period of latency still existed, but it was much shorter than the norm

Also not sure who's network stops and begins where, but news24 when it's bad
Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    23 ms    19 ms    19 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    19 ms    30 ms    18 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6   139 ms   139 ms   151 ms  optinet.ixp.capetown [196.10.140.15] 
  7   157 ms   161 ms   164 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  8    31 ms    36 ms    41 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9    20 ms    20 ms    19 ms  196.28.178.66 
 10   141 ms   131 ms   129 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11    20 ms    31 ms    20 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    21 ms    21 ms    20 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    19 ms    19 ms    19 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Compared to Telkom
Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    19 ms    18 ms    19 ms  105-187-252-54.ti-sen.telkomsa.net [105.187.252.54] 
  5    19 ms    18 ms    18 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  6    19 ms    18 ms    19 ms  blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54] 
  7    19 ms    18 ms    18 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138] 
  8    19 ms    19 ms    22 ms  optinet.ixp.capetown [196.10.140.145] 
  9    22 ms    22 ms    19 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
 10    18 ms    19 ms    19 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
 11    20 ms    20 ms    19 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    19 ms    20 ms    19 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    20 ms    20 ms    20 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 14    52 ms    19 ms    19 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 15    20 ms    20 ms    19 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.
Click to expand...

:(

That looks like the latency starts when it hits the Mweb portion of the network, I'll check with our Team what's going on there. Have you noticed this with any other sites or services?
 
I needs some help ... some technical explanation please.

I have a 4 meg line that used to give me around 3,7megs.
I understand there is some overhead loss so a small difference.
Cool.

The SnR on the line dropped to around 5 and I picked up all sorts of issues. It hovers between 6 and 8 db.
When it was at 9 and above all was good.

Since then the speed as been in the 2.5meg range at best.

I have put in a number of support tickets and have been told my line is fine and all is well.

Result of all is well

Download Speed: 2637 kbps (329.6 KB/sec transfer rate)
Upload Speed: 301 kbps (37.6 KB/sec transfer rate)
Latency: 30 ms
Jitter: 53 ms
2017/01/27, 6:20:42 AM

For the sake of history leading up

Last Result:
Download Speed: 3085 kbps (385.6 KB/sec transfer rate)
Upload Speed: 400 kbps (50 KB/sec transfer rate)
Latency: 30 ms
Jitter: 2 ms
2017/01/26, 12:55:51 AM

Last Result:
Download Speed: 1616 kbps (202 KB/sec transfer rate)
Upload Speed: 394 kbps (49.3 KB/sec transfer rate)
Latency: 30 ms
Jitter: 129 ms

Last Result:
Download Speed: 1930 kbps (241.3 KB/sec transfer rate)
Upload Speed: 278 kbps (34.8 KB/sec transfer rate)
Latency: 169 ms
Jitter: 359 ms
2017/01/23, 11:19:44 PM

Last Result:
Download Speed: 2225 kbps (278.1 KB/sec transfer rate)
Upload Speed: 340 kbps (42.5 KB/sec transfer rate)
Latency: 32 ms
Jitter: 44 ms
2017/01/20, 5:49:23 PM

Of course I have continued to put in support tickets because I want to go back to where I was.

Every now and again I get this response.

Hope you are well.
I checked your line and it is synced at 3.7Mbps by Telkom to stabilize it.
Once the sync stats have a improved, the line speed will be re-synced back to 4Mbps
Should you need anything else, please do contact us.
Click to expand...

Of course ... the line never gets back to 3.7megs ..... and a new support ticket is raised and so we go on.

How do I set about getting to back to where I was?

Edit ... been chatting with AH since 15th October about this .... so not long only about 3 and half months.
Dont you have a critical care section?
 
Last edited:
Traceroute from the East:

Through VOX:

traceroute to news24.com (41.86.110.143), 30 hops max, 40 byte packets
1 * * *
2 41.193.73.214 (41.193.73.214) 36.348 ms 14.057 ms 14.445 ms
3 41.193.73.220 (41.193.73.220) 15.686 ms 15.456 ms 15.573 ms
4 mweb.dinx.net.za (196.223.30.32) 15.409 ms 15.97 ms 15.96 ms
5 197-82-7-1.dbn.mweb.co.za (197.82.7.1) 48.317 ms 197-82-7-2.dbn.mweb.co.za (197.82.7.2) 46.499 ms 197-82-7-1.dbn.mweb.co.za (197.82.7.1) 44.899 ms
6 te0-0-0-0.vic-p-1.optinet.net (197.84.4.38) 47.123 ms te0-7-0-1.vic-p-2.optinet.net (197.84.4.44) 49.808 ms 45.605 ms
7 te0-0-0-0.cpt-p-2.optinet.net (197.84.4.46) 46.919 ms te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 49.949 ms te0-0-0-0.cpt-p-2.optinet.net (197.84.4.46) 47.115 ms
8 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 67.346 ms 46.449 ms 44.965 ms
9 196.28.178.66 (196.28.178.66) 47.331 ms 47.62 ms 44.778 ms
10 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 46.592 ms 46.316 ms 47.647 ms
11 OPTI-CPT-N1-Hosting.optinet.net (197.84.196.6) 45.701 ms 48.522 ms 45.426 ms
12 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 45.312 ms 48.144 ms 47.336 ms
13 41-86-110-143.mweb.co.za (41.86.110.143) 52.107 ms 46.011 ms 47.951 ms

Through Afrihost:

traceroute to news24.com (41.86.110.143), 30 hops max, 40 byte packets
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.174) 18.544 ms 14.477 ms 14.628 ms
3 dbn-in1.ip.adsl.co.za (169.1.5.204) 18.315 ms 15.646 ms 16.403 ms
4 optinet.ixp.durban (196.10.141.75) 15.872 ms 16.543 ms 25.544 ms
5 197-82-7-2.dbn.mweb.co.za (197.82.7.2) 45.594 ms 197-82-7-1.dbn.mweb.co.za (197.82.7.1) 47.714 ms 197-82-7-2.dbn.mweb.co.za (197.82.7.2) 67.545 ms
6 te0-7-0-1.vic-p-2.optinet.net (197.84.4.44) 50.357 ms te0-0-0-0.vic-p-1.optinet.net (197.84.4.38) 47.002 ms 46.183 ms
7 te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 51.602 ms 197-84-4-101.cpt.mweb.co.za (197.84.4.101) 47.683 ms te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 49.278 ms
8 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 48.385 ms te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 48.034 ms vl11.cpt-hscore-1.optinet.net (197.84.5.238) 46.909 ms
9 196.28.178.66 (196.28.178.66) 47.789 ms te0-7-0-0.cpt-p-2.optinet.net (197.84.4.32) 50.9 ms 196.28.178.66 (196.28.178.66) 48.698 ms
10 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 44.364 ms 45.153 ms 62.735 ms
11 OPTI-CPT-N1-Hosting.optinet.net (197.84.196.6) 49.733 ms 196.28.178.66 (196.28.178.66) 45.916 ms 46.115 ms
12 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 51.635 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 52.019 ms 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 49.113 ms
13 41-86-110-143.mweb.co.za (41.86.110.143) 51.066 ms OPTI-CPT-N1-Hosting.optinet.net (197.84.196.6) 46.112 ms 41-86-110-143.mweb.co.za (41.86.110.143) 49.057 ms
 
TEXTILE GUY said:
I needs some help ... some technical explanation please.

I have a 4 meg line that used to give me around 3,7megs.
I understand there is some overhead loss so a small difference.
Cool.

The SnR on the line dropped to around 5 and I picked up all sorts of issues. It hovers between 6 and 8 db.
When it was at 9 and above all was good.

Since then the speed as been in the 2.5meg range at best.

I have put in a number of support tickets and have been told my line is fine and all is well.

Result of all is well

Download Speed: 2637 kbps (329.6 KB/sec transfer rate)
Upload Speed: 301 kbps (37.6 KB/sec transfer rate)
Latency: 30 ms
Jitter: 53 ms
2017/01/27, 6:20:42 AM

For the sake of history leading up

Last Result:
Download Speed: 3085 kbps (385.6 KB/sec transfer rate)
Upload Speed: 400 kbps (50 KB/sec transfer rate)
Latency: 30 ms
Jitter: 2 ms
2017/01/26, 12:55:51 AM

Last Result:
Download Speed: 1616 kbps (202 KB/sec transfer rate)
Upload Speed: 394 kbps (49.3 KB/sec transfer rate)
Latency: 30 ms
Jitter: 129 ms

Last Result:
Download Speed: 1930 kbps (241.3 KB/sec transfer rate)
Upload Speed: 278 kbps (34.8 KB/sec transfer rate)
Latency: 169 ms
Jitter: 359 ms
2017/01/23, 11:19:44 PM

Last Result:
Download Speed: 2225 kbps (278.1 KB/sec transfer rate)
Upload Speed: 340 kbps (42.5 KB/sec transfer rate)
Latency: 32 ms
Jitter: 44 ms
2017/01/20, 5:49:23 PM

Of course I have continued to put in support tickets because I want to go back to where I was.

Every now and again I get this response.



Of course ... the line never gets back to 3.7megs ..... and a new support ticket is raised and so we go on.

How do I set about getting to back to where I was?

Edit ... been chatting with AH since 15th October about this .... so not long only about 3 and half months.
Dont you have a critical care section?
Click to expand...

:(

I just checked on your DSL Line sync, and it looks like the actual line sync is still 3,7Mbps.

The SNR is on 7.8dB and the Attentuation is 48.6dB, so that shouldn't prevent you from getting the full 4Mbps sync.

I see that there was an open fault that was closed on the 17th of January. Did you receive any sort of feedback from Telkom?
 
AfriMan said:
I definitely don't see anything of concern here, neither do the NOC engineers.

I don't see anything local giving 170ms, except one hop to Mweb, which is within their network, not ours. I think we're very satisfied with the results you've posted, as well as those we've got in our own tests in the South, with other users who test for us.
Click to expand...

You don't see anything local besides one hop giving 170ms? That fact alone is that there seems to be an issue at play here. I even gave a comparison of that same trace from another ISP to show you that the high latency only exists when tracing from Afrihost.

See @standerr's results above, that's exactly what I'm seeing, and it definitely impacts gaming performance (jitter or spikes).

And yes, it applies to any site or service that involves the MWEB network.
 
Last edited:
Eish this shaping on capped sucks. Luckily month end, changed it to 1/2 cap, no shaping from Feb. What was said before the shaping started, and what realized when the shaping started, are very different. Like day and night, and the shaping is the dark cold night.

I was always happy with AH and 99.999% a positive AH customer, even during their bad times, but this time... I feel cheated and lied to. Not cool AH, not cool.

If next month the 1/2 cap and no shaping prove to be a anything less than a 9/10 experience, I am dropping AH. Grrrr....
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X