Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
AH manages my dsl line. Can someone tell me how to move my dsl line away from AH so that I am not strapped down?

EDIT: Another question: If I don't want the isp managing the line - what do I do?

You can always unbundle your line from data and move it back into the Holding Pool by cancelling that product. From the Holding pool you can move it back to any ISP (which includes Telkom)
 
Afriman - I have a capped bundle account with you guys and if I pause it, will the dsl line portion of it remain active? Or will that be paused too?

The line part can't be paused unfortunately, but all new data will be paused (though you should still be able to access any valid rollover data and topups)
 
You can always unbundle your line from data and move it back into the Holding Pool by cancelling that product. From the Holding pool you can move it back to any ISP (which includes Telkom)
Please can you assist me in unbundling it and pausing ONLY the data account. The dsl line must remain active please.
 
Agreed.
View attachment 406510

So according to you, capped packages are currently unshaped, correct?
Then why bother paying the premium for the "priority" unshaped capped accounts if I can't even get a stable 200ms ping in the evening that I'm supposed to have and my 8.6/0.72Mbps throughput that I am supposed to have on my 10 Mbps line.

"Unshaped", but if the network's broken, then what's the point as you stated. It's artificial shaping if you know that your network doesn't deliver and yet you still claim it's "unshaped".

Code:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62

Ping statistics for 155.239.255.250:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 22ms, Average = 21ms

EDIT:
Code:
Tracing route to frankfurt.de [62.96.236.95]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1]
  2    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.1]
  3     *        *        *     Request timed out.
  4    24 ms    23 ms    22 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  5    24 ms    23 ms    24 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  6    23 ms    24 ms    24 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  7    23 ms    24 ms    23 ms  41.164.52.40
  8    25 ms    24 ms    24 ms  ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
  [color=red]9   234 ms   215 ms   228 ms  if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253][/color]
 10   147 ms   147 ms   146 ms  if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
 11   171 ms   171 ms   170 ms  if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 12   171 ms   169 ms   170 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 13   176 ms   176 ms   177 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 14   175 ms   175 ms   175 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 15   179 ms   176 ms   177 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 16   217 ms   211 ms   213 ms  linx-ge7-0-oscar.lon.router.colt.net [195.66.224.49]
 17   188 ms   188 ms   189 ms  gi0-2-sar2.JPU.router.colt.net [212.74.84.39]
 18   263 ms   266 ms   249 ms  cpede_fra000990.ia.colt.net [62.96.176.218]
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

https://db-ip.com/41.206.164.253
That 230ms ping trip is still within the city.

Remember that shaping only affects throughout (download speed) on specific services, which would be non-realtime. So even though we're not shaping Capped, if that were the case your latency and ping would be preserved. The results you're showing are showing the kind of latency that points to other issues. Not sure why Germany is the new testing standard on this thread these days, but it looks like latency is mostly increased once we enter the host network for the site you are pinging :(
 
so...to bras is fine but hop 3 and 4 is still terrible:

Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 110 ms 107 ms 107 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 75 ms 75 ms 78 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 121 ms 89 ms 85 ms 41.164.52.40
6 60 ms 57 ms 54 ms 172.18.1.164
7 57 ms 61 ms 63 ms cloudflare.ixp.joburg [196.46.25.198]
8 85 ms 82 ms 87 ms 104.20.30.244

Trace complete.


Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 26ms, Average = 22ms

Definitely not ideal here, though our team have not been reporting any general latency.

We like to see BRAS ping below 10ms or thereabouts, but 20 is not so bad. Can you test again this morning and tell me what you're seeing?
 
Please can you assist me in unbundling it and pausing ONLY the data account. The dsl line must remain active please.

they should not affect each other, but drop me a PM and I'll check the changes you make from my side and advise from there :)
 
Definitely not ideal here, though our team have not been reporting any general latency.

We like to see BRAS ping below 10ms or thereabouts, but 20 is not so bad. Can you test again this morning and tell me what you're seeing?
Already left for work. Pings to bras as far as I recall, over the past few weeks, has always been in +-20s.
So... Now what?
 
they should not affect each other, but drop me a PM and I'll check the changes you make from my side and advise from there :)
Sent 2 pm's. Please check the one about AH+ before looking at the one about pausing.
 
so...to bras is fine but hop 3 and 4 is still terrible:

Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 110 ms 107 ms 107 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 75 ms 75 ms 78 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 121 ms 89 ms 85 ms 41.164.52.40
6 60 ms 57 ms 54 ms 172.18.1.164
7 57 ms 61 ms 63 ms cloudflare.ixp.joburg [196.46.25.198]
8 85 ms 82 ms 87 ms 104.20.30.244

Trace complete.


Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 26ms, Average = 22ms
I've been bitching about this since they went to their "new" network: it manifested exactly like this for the first ~3-4 months of it, and the last 2~3 months its been back. Always high latency appearing either on cpt-rx2.ip.adsl.co.za or on cpt-net1.ip.adsl.co.za with brass always being latency free.

Anyway I canceled earlier this month cause I am tired of their failure/service, and seeing their shaping now I am doubly pleased to leave them.
 
I've been bitching about this since they went to their "new" network: it manifested exactly like this for the first ~3-4 months of it, and the last 2~3 months its been back. Always high latency appearing either on cpt-rx2.ip.adsl.co.za or on cpt-net1.ip.adsl.co.za with brass always being latency free.

Anyway I canceled earlier this month cause I am tired of their failure/service, and seeing their shaping now I am doubly pleased to leave them.

Sorry you feel this way. We've been seeing generally positive feedback on the network since we launched last year, but our engineers have been particularly focussed on the South where we see very specific demand patterns and we want to ensure the best experience.
 
AM so in a nutshell, im not going to do the priority account. I dont torrent much, mostly stream and emails and browsing. Freetime is more important to me because we consume alot of data streaming. What package is R299? 150GB or 300 gigs?
 
I've been bitching about this since they went to their "new" network: it manifested exactly like this for the first ~3-4 months of it, and the last 2~3 months its been back. Always high latency appearing either on cpt-rx2.ip.adsl.co.za or on cpt-net1.ip.adsl.co.za with brass always being latency free.

Anyway I canceled earlier this month cause I am tired of their failure/service, and seeing their shaping now I am doubly pleased to leave them.

Well I"ve been at it for the last 2 or 3 months. Getting nowhere with it at AF, except for 'run more traceroutes, run more traceroutes' Also getting rather fedup with this crap.
 
AM so in a nutshell, im not going to do the priority account. I dont torrent much, mostly stream and emails and browsing. Freetime is more important to me because we consume alot of data streaming. What package is R299? 150GB or 300 gigs?

R299 150GB Priority-Boosted
R299 300GB Shaped Capped

Hope that makes sense?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X