Afrihost Uncapped DSL Feedback

I just want to add. There is serious issues between mweb and Afrihost. its as if you are running a 12kbps link between you two. last few nights is very good for me(since IPC upgrade). but the mweb/afrihost is very bad. aka steam/dstv now etc. anything on that?
 
SickTricky said:
I just want to add. There is serious issues between mweb and Afrihost. its as if you are running a 12kbps link between you two. last few nights is very good for me(since IPC upgrade). but the mweb/afrihost is very bad. aka steam/dstv now etc. anything on that?
Click to expand...

:(

I'll ask our Team to look into this. Were you able to run any traceroutes that I can pass onto them?
 
AfriGenie said:
:(

I'll ask our Team to look into this. Were you able to run any traceroutes that I can pass onto them?
Click to expand...

this is on afrihost

bad%20pings%20afrihost_zpseat3hqq5.jpg


This is on telkom

bad%20pings%20telkom_zpsffh0jdrb.jpg


ok when I did the tracert, I believe my dynamic ip changed the pings were good. so after DC and reconnect the pings are better...
 
AfriFella said:
This is great, but it's a ping test. :) Could you perhaps add a traceroute to these results as well and we'll pass it onto our team as a bundle.
Click to expand...

Sorry, :) like I said. all is fine now. traceroutes are clean. after the DC and reconnect everything was fine
 
AfriGenie said:
That would appear to be part of our network infrastructure, yes. :)
Click to expand...

That's nice. You must be so proud.

So, now that I have clarity on whether you deserving kakking out, when are you going to pull your fingers from your sphincters and get it fixed? Routing through that node adds 150ms+ latency to international hosts, no matter what time of day. It's been doing this for over a year.

It would be so nice if others took some pride in their work for a change. But maybe my expectations are unreasonable.

Code: 
tracert www.huffingtonpost.com

Tracing route to gp1.adn.v2cdn.net [93.184.219.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  FVS318Gv2 [192.168.10.200]
  2     *        *        *     Request timed out.
  3     *       23 ms    23 ms  jhb-up3.ip.adsl.co.za [169.1.5.29]
  4    25 ms    22 ms    23 ms  169-1-5-250.ip.afrihost.co.za [169.1.5.250]
  5   103 ms   105 ms    92 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  6    23 ms    23 ms    24 ms  jhb-ex0.ip.adsl.co.za [169.1.5.61]
  7    22 ms    22 ms    23 ms  aptice.net.afrihost.co.za [169.1.1.44]
  8    24 ms    27 ms    24 ms  jhb-os2.ip.adsl.co.za [169.1.1.49]
  9    81 ms    85 ms   223 ms  jhb-ex1.ip.adsl.co.za [169.1.5.60]
 10    34 ms    32 ms    30 ms  169-1-5-74.ip.afrihost.co.za [169.1.5.74]
 11    23 ms    23 ms    23 ms  41.169.57.216
 12    24 ms    23 ms    24 ms  ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
 13   225 ms     *      212 ms  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 14   284 ms   298 ms   279 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
 15   230 ms   228 ms   275 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 16   197 ms   210 ms   208 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 17   190 ms   190 ms   190 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 18     *      196 ms   197 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 19   202 ms   202 ms   202 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 20   192 ms   193 ms   192 ms  80.231.60.123
 21   200 ms   200 ms   199 ms  ae-2.r02.londen03.uk.bb.gin.ntt.net [129.250.4.131]
 22   281 ms   280 ms   275 ms  81.25.207.42
 23   278 ms   281 ms   282 ms  93.184.219.20

Trace complete.
 
Whoah... this is so... unexpected. 180ms added latency while routing through Slaapstad.

The datagrams must really enjoy taking in the mountain view. That has to be the explanation. After all, it can't be that a company that purports to offer a quality service is actually skimping on serving the needs of paying customers, can it?

Code: 
tracert www.huffingtonpost.com

Tracing route to gp1.adn.v2cdn.net [93.184.219.20]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  FVS318Gv2 [192.168.10.200]
  2     *        *        *     Request timed out.
  3     *       24 ms    23 ms  jhb-up3.ip.adsl.co.za [169.1.5.29]
  4    25 ms    24 ms    23 ms  169-1-5-250.ip.afrihost.co.za [169.1.5.250]
  5    49 ms    48 ms    47 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  6    85 ms    60 ms     *     jhb-ex0.ip.adsl.co.za [169.1.5.61]
  7    23 ms    23 ms    23 ms  aptice.net.afrihost.co.za [169.1.1.44]
  8    33 ms    35 ms    36 ms  jhb-os2.ip.adsl.co.za [169.1.1.49]
  9    23 ms    23 ms    23 ms  jhb-ex1.ip.adsl.co.za [169.1.5.60]
 10    48 ms    53 ms    57 ms  169-1-5-74.ip.afrihost.co.za [169.1.5.74]
 11    42 ms    48 ms    51 ms  41.169.57.216
 12    23 ms    24 ms    24 ms  ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
 13   188 ms   199 ms   205 ms  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 14   287 ms   217 ms   231 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
 15   202 ms   355 ms   396 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 16   296 ms   460 ms   283 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 17   301 ms   309 ms   309 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 18     *      311 ms   339 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 19   280 ms   308 ms   323 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 20   305 ms   322 ms   320 ms  80.231.60.123
 21   301 ms   270 ms   294 ms  ae-2.r02.londen03.uk.bb.gin.ntt.net [129.250.4.131]
 22   309 ms   345 ms   323 ms  81.25.207.42
 23   262 ms   294 ms   310 ms  93.184.219.20

Trace complete.
 
Abominable Intelligence said:
Whoah... this is so... unexpected. 180ms added latency while routing through Slaapstad.

The datagrams must really enjoy taking in the mountain view. That has to be the explanation. After all, it can't be that a company that purports to offer a quality service is actually skimping on serving the needs of paying customers, can it?

Code: 
tracert www.huffingtonpost.com

Tracing route to gp1.adn.v2cdn.net [93.184.219.20]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  FVS318Gv2 [192.168.10.200]
  2     *        *        *     Request timed out.
  3     *       24 ms    23 ms  jhb-up3.ip.adsl.co.za [169.1.5.29]
  4    25 ms    24 ms    23 ms  169-1-5-250.ip.afrihost.co.za [169.1.5.250]
  5    49 ms    48 ms    47 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  6    85 ms    60 ms     *     jhb-ex0.ip.adsl.co.za [169.1.5.61]
  7    23 ms    23 ms    23 ms  aptice.net.afrihost.co.za [169.1.1.44]
  8    33 ms    35 ms    36 ms  jhb-os2.ip.adsl.co.za [169.1.1.49]
  9    23 ms    23 ms    23 ms  jhb-ex1.ip.adsl.co.za [169.1.5.60]
 10    48 ms    53 ms    57 ms  169-1-5-74.ip.afrihost.co.za [169.1.5.74]
 11    42 ms    48 ms    51 ms  41.169.57.216
 12    23 ms    24 ms    24 ms  ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
 13   188 ms   199 ms   205 ms  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 14   287 ms   217 ms   231 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
 15   202 ms   355 ms   396 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 16   296 ms   460 ms   283 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 17   301 ms   309 ms   309 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 18     *      311 ms   339 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 19   280 ms   308 ms   323 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 20   305 ms   322 ms   320 ms  80.231.60.123
 21   301 ms   270 ms   294 ms  ae-2.r02.londen03.uk.bb.gin.ntt.net [129.250.4.131]
 22   309 ms   345 ms   323 ms  81.25.207.42
 23   262 ms   294 ms   310 ms  93.184.219.20

Trace complete.
Click to expand...

180ms added latency? What international latency do you usually see?

With that being said, I can see that this is higher than normal and I've passed it onto our NOC Team. :)
 
Morning Guys!

There is an issue in the East at the moment. We've seen a drop in the available capacity, our Team is investigating now. We've updated the Network Notice page.
 
Just an update guys, our Team believes that the issue in the East has been resolved, but can you please test from your side and see if there is any change.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X