Afrihost Capped DSL Feedback

[JohnJuniorV3]

Thanks!

Our Network Team is looking into this now. I'll let you guys know the moment I have an update.

Thank you very much!

 

[nerf]

Crystal Web

C:\Users\Oliver>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.246.79]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms csp3.zte.com.cn [192.168.1.1]
2 * * * Request timed out.
3 81 ms 19 ms 19 ms cdsl2-rba-vl2563-ipc.ip.isnet.net [196.38.73.214]
4 97 ms 19 ms 18 ms cdsl2-rba-vl2563.ip.isnet.net [196.38.73.213]
5 20 ms 20 ms 19 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 91 ms 21 ms 22 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 193 ms 184 ms 183 ms 168.209.201.93
8 185 ms 180 ms 187 ms bbc-linx.pr01.rbsov.bbc.co.uk [195.66.236.103]
9 * * * Request timed out.
10 247 ms 183 ms 182 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
11 210 ms 207 ms 204 ms 132.185.255.165
12 182 ms 182 ms 185 ms 212.58.246.79

Trace complete.

Afrihost
C:\Users\Oliver>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.246.79]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms csp3.zte.com.cn [192.168.1.1]
2 * * * Request timed out.
3 * 122 ms 122 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 118 ms 120 ms 117 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 120 ms 107 ms 96 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 141 ms 141 ms 137 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 108 ms 105 ms 102 ms 41.169.57.216
8 122 ms 122 ms 122 ms if-ae-7-0.tcore2.JSO-Johannesburg.as6453.net [41.206.179.13]
9 299 ms * 302 ms if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net [216.6.55.85]
10 187 ms 187 ms 187 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
11 273 ms 273 ms 256 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.57]
12 * 288 ms * if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
13 296 ms 296 ms 301 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
14 301 ms 300 ms 298 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
15 * 188 ms * if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
16 285 ms 286 ms 285 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 291 ms 295 ms 286 ms NIU-SOLUTIO.ear1.London15.Level3.net [212.187.173.210]
21 * * * Request timed out.
22 * * * Request timed out.
23 * 310 ms 307 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
24 250 ms 240 ms 231 ms 132.185.255.165
25 290 ms 292 ms 292 ms 212.58.246.79

Trace complete.

@Afrihost, getting the same - 100mbps Fiber on Openserve

Trace from Afrihost account

4 * * * Request timed out.
5 * 88 ms 70 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
6 116 ms 113 ms 112 ms jhb-in2.ip.adsl.co.za [169.1.5.30]
7 210 ms 116 ms 112 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
8 * 119 ms 122 ms cloudflare.ixp.joburg [196.60.8.198]
9 121 ms 127 ms 122 ms 104.20.10.169

Trace from Web Africa accounts

5 22 ms 8 ms 9 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134]
6 18 ms 15 ms 7 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
7 13 ms 8 ms 7 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
8 14 ms 10 ms 14 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

 

[steel_dog]

We're definitely up to date with all of your test results. You are still working with our Critical Care Team if I'm not mistaken?

Yep you and AfriFella are certainly up to date. My feedback wasn't directed to either of you .
Someone in CC has been assigned to drive this with the NOC team. I've been providing input since Saturday. Not a peep from NOC though. I was told that some upgrade was done in CPT a week and a bit ago. Hasn't changed the experience. Both AH SAIX Test accounts and my new CW capped account works peachy.

More woe from today - Downloads from my US based VPS - AH 96KB/s; CW 1.5MB/s.

 

[VindicatoR]

Been experiencing similar issues to EU on my Afrihost Unshaped Capped account.

Playing WoW or Diablo 3 on this is just horrible intermittent spikes.

Traceroute:

C:\>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.93]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 14 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 5 ms 7 ms 7 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 7 ms 7 ms 6 ms 41.164.52.40
6 6 ms 11 ms 11 ms ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
7 172 ms 162 ms 162 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
8 160 ms 158 ms 159 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.101]
9 287 ms 291 ms 287 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 162 ms 163 ms 163 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 292 ms 291 ms 293 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
12 166 ms 167 ms 167 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
13 300 ms 295 ms 278 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
14 167 ms 162 ms 162 ms 195.219.83.102
15 * * * Request timed out.
16 * * * Request timed out.
17 289 ms 282 ms 319 ms NIU-SOLUTIO.ear1.London15.Level3.net [212.187.173.210]
18 * * * Request timed out.
19 * * * Request timed out.
20 282 ms 291 ms 287 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
21 164 ms 161 ms 156 ms 132.185.255.165
22 166 ms 167 ms 163 ms bbc-vip014.cwwtf.bbc.co.uk [212.58.246.93]

Trace complete.

I'm constantly running a ping to check my connection and on the Afrihost account I get random packet loss for no apparent reason.

Swapped to my WA account as I couldn't take it anymore.

 

[ToyToyZA]

Experience similar issues with latency on local csgo servers, no matchmaking tonight

Tracing route to www.bbc.net.uk [212.58.246.55]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms [192.168.0.1]
2 * * * Request timed out.
3 10 ms 9 ms 10 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 115 ms 96 ms 93 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 201 ms 98 ms 98 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 9 ms 10 ms 9 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 * 103 ms 102 ms 41.169.57.216
8 15 ms 10 ms 9 ms ix-ae-7-0.tcore1.jso-johannesburg.as6453.net [41.206.178.29]
9 225 ms 227 ms 228 ms if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
10 187 ms 181 ms 182 ms if-ae-5-2.tcore2.pv9-lisbon.as6453.net [80.231.159.85]
11 185 ms 183 ms 183 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
12 188 ms 185 ms 184 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
13 179 ms 179 ms 189 ms if-ae-2-2.tcore2.sv8-highbridge.as6453.net [80.231.139.1]
14 188 ms * * if-ae-11-2.tcore1.l78-london.as6453.net [80.231.139.42]
15 181 ms 180 ms 189 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 247 ms 260 ms 266 ms niu-solutio.ear1.london15.level3.net [212.187.173.210]
20 * * * Request timed out.
21 * * * Request timed out.
22 190 ms 188 ms 189 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
23 271 ms 262 ms 264 ms 132.185.255.165
24 258 ms 252 ms 246 ms bbc-vip046.cwwtf.bbc.co.uk [212.58.246.55]

Trace complete.

I'm also experiencing up to 7% packet loss.

Seems the problem is not restricted to Cape Town.

 

[electrofreeze]

shaping on the Shaped Capped accounts shouldn't be happening too often.

Really? so http downloads are getting shaped heavily otherwise people wont be able to browse on your network even at 1 am in the morning every day and night

 

[Hummercellc]

Is anyone else seeing Packet Loss to the Mweb Network?


Tracing route to talk.mweb.net [197.80.140.140]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 20 ms 25 ms 25 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 20 ms 21 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 30 ms 30 ms 28 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 26 ms 27 ms 28 ms optinet.ixp.durban [196.10.141.75]
7 37 ms 34 ms * 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
8 41 ms * 36 ms te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
9 41 ms 47 ms * 197-80-7-78.jhb.mweb.co.za [197.80.7.78]
10 39 ms * 32 ms 197-80-132-82.jhb.mweb.co.za [197.80.132.82]
11 * * 33 ms talk.mweb.net [197.80.140.140]

 

[AfriFella]

Really? so http downloads are getting shaped heavily otherwise people wont be able to browse on your network even at 1 am in the morning every day and night

Have you compared your experience to an Unshaped Capped account?

 

[AfriFella]

Morning Everyone. Our NOC Team confirmed at around 11:30PM last night that the latency issue was resolved. It appears that a physical cable error affected throughput at an upstream point in our network, but was quickly resolved. Thanks to everyone for testing - please report back if you're still experiencing issues.

 

[electrofreeze]

Have you compared your experience to an Unshaped Capped account?

do you have a test account we can try

 

[VindicatoR]

Morning Everyone. Our NOC Team confirmed at around 11:30PM last night that the latency issue was resolved. It appears that a physical cable error affected throughput at an upstream point in our network, but was quickly resolved. Thanks to everyone for testing - please report back if you're still experiencing issues.

Hey AfriFella, I'm still experiencing packet loss this morning on pings, I've yet to test it in anything else, but will do so once I get home from work.

 

[AfriFella]

Hey AfriFella, I'm still experiencing packet loss this morning on pings, I've yet to test it in anything else, but will do so once I get home from work.

What address are you testing? Could you run an MTR and post the results for me, please?

 

[electrofreeze]

speeds are getting real crappy again and moving up and down a lot

 

[VindicatoR]

What address are you testing? Could you run an MTR and post the results for me, please?

Using bbc.co.uk, since I think it's the most accurate for testing EU latency.

I hope I'm assuming correct here in 'an MTR' you mean a traceroute.

Traceroute:

C:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.244.22]
over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    11 ms    11 ms    10 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  4     4 ms     7 ms     7 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  5     4 ms    11 ms    11 ms  41.164.52.40
  6     9 ms    10 ms    11 ms  ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
  7   156 ms   156 ms   158 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.93]
  8   163 ms   163 ms   163 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
  9   160 ms   154 ms   155 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 10   160 ms   156 ms   157 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 11     *      158 ms   157 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 12   160 ms   163 ms   167 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 13   156 ms   155 ms   155 ms  195.219.83.102
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16   156 ms   155 ms   157 ms  NIU-SOLUTIO.ear1.London15.Level3.net [212.187.173.210]
 17     *        *        *     Request timed out.
 18   153 ms   157 ms   160 ms  ae0.er02.telhc.bbc.co.uk [132.185.254.105]
 19   156 ms   166 ms   158 ms  132.185.255.148
 20   163 ms   163 ms   167 ms  212.58.244.22

Trace complete.

Got the below running almost all the time while gaming to monitor server/internet issues.

Ping:

C:\>ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.246.78] with 32 bytes of data:
Reply from 212.58.246.78: bytes=32 time=164ms TTL=44
Reply from 212.58.246.78: bytes=32 time=163ms TTL=44
Request timed out.
Reply from 212.58.246.78: bytes=32 time=164ms TTL=44
Reply from 212.58.246.78: bytes=32 time=162ms TTL=44
Reply from 212.58.246.78: bytes=32 time=164ms TTL=44

But getting those drops randomly, its looking a lot better now, but it was worse the last couple of weeks(7-12 days).

 

[AfriGenie]

Using bbc.co.uk, since I think it's the most accurate for testing EU latency.

I hope I'm assuming correct here in 'an MTR' you mean a traceroute.

C:\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.244.22]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 11 ms 10 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 4 ms 7 ms 7 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 4 ms 11 ms 11 ms 41.164.52.40
6 9 ms 10 ms 11 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 156 ms 156 ms 158 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.93]
8 163 ms 163 ms 163 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
9 160 ms 154 ms 155 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 160 ms 156 ms 157 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
11 * 158 ms 157 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
12 160 ms 163 ms 167 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 156 ms 155 ms 155 ms 195.219.83.102
14 * * * Request timed out.
15 * * * Request timed out.
16 156 ms 155 ms 157 ms NIU-SOLUTIO.ear1.London15.Level3.net [212.187.173.210]
17 * * * Request timed out.
18 153 ms 157 ms 160 ms ae0.er02.telhc.bbc.co.uk [132.185.254.105]
19 156 ms 166 ms 158 ms 132.185.255.148
20 163 ms 163 ms 167 ms 212.58.244.22

Trace complete.

Got the below running almost all the time while gaming to monitor server/internet issues.

C:\>ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.246.78] with 32 bytes of data:
Reply from 212.58.246.78: bytes=32 time=164ms TTL=44
Reply from 212.58.246.78: bytes=32 time=163ms TTL=44
Request timed out.
Reply from 212.58.246.78: bytes=32 time=164ms TTL=44
Reply from 212.58.246.78: bytes=32 time=162ms TTL=44
Reply from 212.58.246.78: bytes=32 time=164ms TTL=44

But getting those drops randomly, its looking a lot better now, but it was worse the last couple of weeks(7-12 days).

Thanks for sharing! I'm passing these results onto our Team.

 

[Wetstuff]

Hi All

Can someone please explain the following statement to me:

"The fact that the uploads are not done at the time of your downloads does not mean they won't affect your overall speed."

This is in relation to the same high latency / streaming problems many here are having in Cape Town.

Thanks in advance

 

[GreatD7007]

If you're using the same account, it sounds like it could be an issue with either the line or the exchange in the second location. Can you drop me a PM with the line number?

Will send you the number now....

 

[AfriMan]

Hi All

Can someone please explain the following statement to me:

"The fact that the uploads are not done at the time of your downloads does not mean they won't affect your overall speed."

This is in relation to the same high latency / streaming problems many here are having in Cape Town.

Thanks in advance

It could be a reference to asynchronous digital transfer, which I also had some confusion around. While it is theoretically possible to upload and download at the same time, if your line is saturated with a download (or an upload), it can affect your overall experience.

Context could help me explain in more detail

 

[AfriMan]

Will send you the number now....

Awesome - thanks

 

[steel_dog]

Hi All

Can someone please explain the following statement to me:

"The fact that the uploads are not done at the time of your downloads does not mean they won't affect your overall speed."

This is in relation to the same high latency / streaming problems many here are having in Cape Town.

Thanks in advance

Hmmm... so paraphrasing the statement above - If you don't have any uploads running it doesn't mean that uploads won't affect your overall speed. Err... that statement does not make any sense.

Basically if you have either uploads or downloads running it will affect ping results.
Uploads will affect download experience IF you saturate the upstream connection.
From my experience, modems are fairly good at throttling the downstream connection to allow saturation on the upstream. I've not seen the converse. Would be difficult on DSL given the ratio of upstream to downstream.